I agree with this post. A $200 million failure clearly refutes the first portion of the sentence: "Concord wasn't a bad game, but it just didn't generate enough interest with enough players". Heck, where I work, a $200 million failure would have someone sent to jail.

Google, Microsoft, Apple, Facebook, Amazon, or another one of the big software development companies could easily fork ffmpeg itself, fix the open CVEs, provide their own (likely incompatible) features, and become the new standard - leaving the original developers out in the cold. Google did this with Blink (forked from WebKit, which itself was forked from KHTML). They took a fork of a KDE backed project, put it into what is now the #1 browser in the world, allowed Microsoft, Opera, and others to then use it in their own browsers — and now Google owns the entire narrative and development direction for the engine (in parallel to, and controlled to a lesser extent by Apple which maintains WebKit). The original KHTML developers really couldn’t keep up, and stopped maintaining KHTML back in 2016 (with full deprecation in 2023).

That is the risk for the original developers here. You’re right in that there isn’t really anything out there that can do what ffmpeg does — but if the developers don’t keep up on CVEs then organizations are going to look for new maintainers — and a year or two from now everyone will be using the Google/Microsoft/Apple/Facebook renamed version of ffmpeg instead.

That’s the shitty truth of how these things work. We’ve seen these same actors do it before.

Yaz

Look — I’m a developer. I get it. I’m personally all for having organizations do more to support the OSS they rely on. But the people in the C-suite are more worried about organizational reputation and losing money to lawsuits. If a piece of software they rely on has a known critical CVE that allows for remote code execution and someone breaks in and steals customer data — that software either needs to be fixed, or it needs to be scrapped. Those are the choices. Our customers in the EU are allowed to request SBOMs of everything we use and pass it through their own security validation software — and if they find sev critical CVEs in software we’re using there is going to be hell to pay. And the people in the C-suite can’t abide that level of risk.

Most software development companies (outside some of the biggest ones) don’t really have the kind of expertise in house to supply patches to something as complex as ffmpeg. But a company like Google has the staff with sufficient experience in this area that they could fork the project, fix the issues, and redistribute it as their own solution to the problem — and now Google is driving ffmpeg development. Organizations that need a security-guaranteed version will simply switch to Google’s version, which will likely slowly become incompatible with the original. They’ve done it before — Chrome was Google’s fork of WebKit, huge swaths of users flocked to Chrome, and now Google has over the years made enough changes that their patches often aren’t compatible with WebKit (and, of course, WebKit itself did similar when they forked KHTML).

Now forking like this is great for the community, but it can be tough on individual developers who see their work co-opted and then sidelined by massive corporations. And that’s really why the ffmpeg developers need to be very careful about ignoring CVEs like this. They do so at their own peril, as anyone can fork their code, fix the issues, and slowly make it incompatible with the original. And a big enough organization can ensure they’re fork becomes the new standard, leaving the original developers out in the cold.

Yaz

That, or your project gets sidelined. Which is where the danger lies.

I work for a big multinational software company that uses a lot of Open Source Software. We have a security office that audits all of our products several times a year. If any piece of our stack shows any open CVEs we have a fixed amount of time to fix the issue, with the amount of time varying from a few days (for CRITICAL severity issues) to roughly half a year for the lowest severity issues. A lack of a fix for a published CVE isn’t an excuse for not fixing the issue on our end — the software still has a security flaw in it, and the organization is so incredible security averse (thanks in part to having contacts in the defence industry) that they don’t want to risk expensive lawsuits and the loss of reputation if a vulnerability is exploited.

A lot of bigger organizations now work this way. We’ve all seen what has happened to organizations that have had significantly security breaches, and it’s not pretty. Our customers are big corporations and government entities — and if they even sniff a risk there are going to be problems. So if there is an unpatched exploit, we’re expected to either switch to something comparable, or DIY a solution (either replacing the library in question, or potentially patching it ourselves).

If ffmpeg allows known and published vulnerabilities to languish, the risk here is that organizations that use their code will simply stop using it and will look for other solutions. That’s a tough pill for an Open Source Software developer to swallow, especially when they make it as big and important as ffmpeg. You might wind up in a situation where an entity like Google forks your code and takes ownership, and eventually gets everyone to migrate to using their version instead (like what they did with WebKit to Chrome), leaving you sidelines. Or maybe someone else jumps in with a compatible solution that works well enough for enough users that they switch to that instead.

Now in an ideal world, the Google’s of this world would not only submit a CVE but would also submit a patch. Having been an OSS developer myself I’ve always encouraged my staff if they find a bug in a piece of software we use to file a bug report and ideally a patch if they know how to patch the issue correctly — but I know that is hardly universal within our organization, and probably even less so elsewhere.

TL;DR: a lot of OSS success relies on having lots of users, or at least some big and important users. But you risk losing those if you leave CVE’s open for too long, as company policies may require scrapping software with unfixed CVEs. That loss of users and reputation is dangerous for an OSS project — it’s how projects get supplanted, either by a fork or by a new (and similar) project.

Yaz

Science? Really? There's a lot of soft-brained, unscientific and technophilic pseudo-religion in the article.

Let's work with the argument's load-bearing phrase, "exploration is an intrinsic part of the human spirit."

There are so many things to criticise in that single statement of bias. Suffice it to say there's a good case to be made that "provincial domesticity and tribalism are prevalent inherited traits in humans", without emotional appeals to a "spirit" not in evidence.

Not according to Kim Kardashian.

Imagine being fined for a political opinion because you don't have a degree political science... how could anyone thing this is good?

The REAL headline and buried lede for the original post should be:

Trump guts nuclear safety regulations

“The president signed a pair of orders on Friday aimed at streamlining the licensing and construction of nuclear power plants — while panning the Nuclear Regulatory Commission for its ‘myopic’ radiation safety standards.”

We now have industry capture of the Nuclear Regulatory Commission.

Who here knows about Admiral Hyman RIckover? All of this is worth reading:

https://en.wikipedia.org/wiki/Hyman_G._Rickover#Safety_record

Are You Scared Yet?

I would be.

The Department of Energy is selling off more than 40,000 pounds of weapons-grade plutonium from the Cold War arsenal to nuclear reactor startups. All of which I’m sure will be thoroughly vetted and monitored, because this is done under the direction of a former board member. Yikes!

https://en.wikipedia.org/wiki/Chris_Wright

Who IS Oklo, Inc. the "private nuclear reactor builder/operator"? Oklo is Sam Altman:

Trump Administration Providing Weapons Grade Plutonium to Sam Altman

We're in territory where weapons-grade plutonium is being given at fire-sale prices to billionaires who's ethical boundaries include creating their own demand for otherwise unnecessary, high-risk energy projects. Guys like Altman, who get their ideas from Wikipedia articles about Ayn Rand — because they are one rung lower than people who actually READ that garbage.

But I'm sure no inventory of hot nuke metal will ever go missing.

Apple had a culture of authenticity. Culture dies pretty hard in most cases. I think we will see the last of that culture dissipate, as it eroded so greatly under Cook and Ive. Then the extractive, enshittifying corruption will spread from Apple, too.

There really was something, that began with Jobs and Woz. It wasn't perfect, and Jobs had a way of twisting ethical stances in ends-justifying-means sophistry. But Steve Jobs would never have prostrated before Trump, proffering a solid gold token.

Oh, you want profit? This is a surveillance spyware wrapper around the entire MacOS user experience - so if you thought Microsoft's Copilot Recall was invasive monitoring, you haven't seen anything yet.

If Apple won't monetize a user panopticon and partner with governments to do it, OpenAI will be right there, to take the cash.

I will argue against strict adherence to this statement. Gnome applications written to the project guidelines have become very fine, since the introduction of GTK-4 and libadwaita. I prefer many of these to their equivalents on MacOS.

It's true that most of these fall into a general category of "utilities", and that Windows enjoys a broader ecosystem driven by commercial incentive. But Windows programs are hardly "better' for this, and the widely varied usability is generally sub-par compared to level that's become norm for Gnome/Adwaita software.

If they are only relaying data I guess it would be an easy fix, just send the data up encrypted and it just passes it along. But if they are actually needing to interact with the data I guess that's a problem.

and it's here today. No homelessness. No medical bankruptcy. No food insecurity. Affordable education. Decent places for everyone to live.