Part VIII, Annex VI on reparations: Germany was forced to renounce trademark rights on pharmaceutical and chemical products in favor of the Allied powers, so Bayer's Aspirin and Heroin were included.
97 karma · joined May 8, 2022
...had. Nintendo swapped it out in version 1.2 of OoT and all versions afterwards. It is of course relevant that they had it in there in the first place, but AIUI they didn't know it was Islamic chanting then, given they had a strict policy on not including such kinds of references and made the change for that reason.
Honestly, I think you're very much underestimating how much Wikipedia writes about government policy - but perhaps more to the point, it's trivial to find articles about controversies regarding the "other side" that are also quite well furnished, e.g.:
- https://en.wikipedia.org/wiki/Barack_Obama_tan_suit_controve...
- https://en.wikipedia.org/wiki/Let%27s_Go_Brandon
- https://en.wikipedia.org/wiki/I_Did_That!
- https://en.wikipedia.org/wiki/2023_White_House_cocaine_incid...
- https://en.wikipedia.org/wiki/Township_High_School_District_...
- https://en.wikipedia.org/wiki/Code_name_Geronimo_controversy
So I don't think there's much of an argument to say that they're being particularly biased in doing this (you might believe that none, or almost none of these articles at all should exist, but that's a different issue).
I don't know if you'd be satisfied with that, but certainly this would allow them to easily make the blog posts you seem to be complaining about, all while making the load on maintainers rather minimal, at least insofar as blog posts appear to be quite infrequent compared to the total amount of vulnerabilities they report - around 20 vulnerability reports per year certainly seems like a manageable load for the entire FOSS community to bear, especially given almost none of these 20 yearly vulnerability reports would go to ffmpeg (if not literally none, given the Project Zero blog has 0 search results for "ffmpeg" or "libav"), and a significant portion of their blog posts aren't even about FOSS at all but instead about proprietary software like the operating systems Microsoft and Apple make.
I do think such a thing would be bad for everyone, though (including the ffmpeg developers themselves, to be honest) - Project Zero is good for everyone's security, in my opinion, and even if all FOSS developers were to universally decide to reject all Project Zero reports that don't come with a patch, and Google decided to still not make such patches, people being able to know that these vulnerabilities exist is still a good thing nonetheless - certainly much better than more vulnerabilities being left in for malicious actors to discover and use in zero-day attacks.
I, and I think most security researchers do too, believe that it would be incredibly negligent for someone who has discovered a security vulnerability to allow it to go unfixed indefinitely without even disclosing its existence. Certainly, ffmpeg developers do not owe security to their users, but security researchers consider that they have a duty to disclose them, even if they go unfixed (and I think most people would prefer to know an unfixed vulnerability exists than to get hit by a 0-day attack). There's gotta be a point where you disclose a vulnerability, the deadline can never be indefinite, otherwise you're just very likely allowing 0-day attacks to occur (in fact, I would think that if this whole thing never happened and we instead got headlines in a year saying "GOOGLE SAT ON CRITICAL VULNERABILITY INVOLVED IN MASSIVE HACK" people would consider what Google did to be far worse).
To be clear, I do in fact think it would be very much best if Google were to use a few millionths of a percent of their revenue to fund ffmpeg, or at least make patches for vulnerabilities. But regardless of how much you criticize the lack of patches accompanying vulnerability reports, I would find it much worse if Google were to instead not report or disclose the vulnerability at all, even if they did so at the request of developers saying they lacked resources to fix vulnerabilities.
I think the far more likely result of all the complaints is that Google simply completely disengages from ffmpeg and stops doing any security work on it. I think that would be quite bad for the security of the project - if Google can trivially find bugs at a high speed such that it overwhelms the ffmpeg developers, I would imagine bad actors can also search for them and find those same vulnerabilities Google is constantly finding, and if they know that those vulnerabilities very much exist, but that Google has simply stopped searching for them upon demand of the ffmpeg project, this would likely give them extremely high motivation to go looking in a place they can be almost certain they'll find unreported/unknown vulnerabilities in. The result would likely be a lot more 0-day attacks involving ffmpeg, which I do not think anyone regards as a good outcome (I would consider "Google publishes a bunch of vulnerabilities ffmpeg hasn't fixed so that everyone knows about them" to be a much preferable outcome, personally)
Now, you might consider that possibility fine - after all, the ffmpeg developers have no obligation to work on the project, and thus to e.g. fix any vulnerabilities in it. But if that's fine, then simply ignoring the reports Google currently makes is presumably also fine, no ?
Transparency would have been most important before they started randomly cancelling contracts, but it seems they didn't bother.
Additionally, during the 1958 coup itself he did basically give his support for it in the sense that he explicitly said he was "ready to assume the powers of the republic" if asked for (which is what the leaders of the coup demanded be done).
See also https://xkcd.com/2501/