3 ms·
Here's a thread by Google's head of security that notes the ways they've contributed to FFmpeg over the years: https://x.com/argvee/status/1986194852669964528
by skybrian 1y ago
Here's a thread by Google's head of security that notes the ways they've contributed to FFmpeg over the years:
https://x.com/argvee/status/1986194852669964528 https://x.com/argvee/status/1986194852669964528
- FridgeSeal 1y agoUnfortunately, nobody not on Twitter can see anything except the first message, which just appears to be some corporate-deflection-speak. It’s a trillion dollar company. I’m sure they could find rifle through their couch cushions and find more than enough money and under-utilised devs to contribute finance or patches.
- tom_ 1y agoTry xcancel instead: https://xcancel.com/argvee/status/1986194852669964528 https://xcancel.com/argvee/status/1986194852669964528
- deleted 1y ago[deleted]
- izacus 1y agoGoogle is one of the largest contributors to OSS in the world, so they're already throwing literal millions at OSS?
- Jyaif 1y agoThey have thousands of highly paid employees working on open source; they are spending at least 1 billion per year.
- FridgeSeal 1y agoI’m sure they can take a moment of their _busy schedules_ to send a patch then. Especially if they’ve just spent all this cash on some ai tool.
- izacus 1y agoI'm sure you can as well. I had no issues contributing to ffmpeg under my company payroll before, why not you?
- strictnein 1y agoNice to see coming from Google. Some other current and form Google employees were unfortunately not as professional in their interactions on Twitter in regards to this issue.
- lofaszvanitt 1y agoIf you rely on it, pay for it. So easy. Especially if you are a BIIG company. Money gives the maintainers joy, free time and appreciation for their work. Wakey wakey people, FOSS is here to F you. It can be free, while those, who rely on it and using it, also pay for it.
- mellosouls 1y agoTo help those without access to X, the PR thread linked appears to give 2014 as the last time they reported solid contributions to helping fix security issues in ffmpeg. https://security.googleblog.com/2014/01/ffmpeg-and-thousand-fixes.html https://security.googleblog.com/2014/01/ffmpeg-and-thousand-...
- skybrian 1y agoWhile technically accurate, this is selective quoting, leaving out other contributions. Here's an archive link: https://xcancel.com/argvee/status/1986194852669964528 https://xcancel.com/argvee/status/1986194852669964528