As a developer I have reviewed open source code and reported vulnerabilities to maintainers. I think more of the cve issues are reported by university organized and funded security research groups but corps and independent individuals report some too.

The alternative is closed source, proprietary software where security vulnerabilities can be harder to identify by obscurity, but also be exploited for longer because they take longer to identify and report while others may still be using the exploit. This is what people mean when they say security by obscurity isn’t secure, because while it may grant the appearance of security if you prevent security groups from reviewing and examining code it may also prevent them from discovering vulnerabilities that are already being exploited. But measuring these effects sounds like an interesting read.

Square pusher flipping bits, like George Jetson without the sprockets

Build a skunk works, it’s like an IT department’s shadow IT, shave a yak, shed a bike.

Yeah I don’t think anyone was called a remaster, different words even if they share the same root

Also master/slave was used in tech for awhile not just for forked branches, a couple examples are https://docs.oracle.com/cd/E88353_01/html/E37855/scsi-slave-9f.html in SCSI interfaces and replication systems like those used with databases https://jira.mariadb.org/plugins/servlet/mobile#issue/MDEV-18777

Default, primary, contemporary, trunk, toot toot here comes the deploy train

deleted by creator

Glad to see ffmpeg is still going strong, I used it years ago to do some project 1999 EverQuest streaming on twitch running on a Manjaro dist install running EQ in wine.

Jess of the heretical texts