FFmpeg to Google Fund Us or Stop Sending Bugs: https://thenewstack.io/ffmpeg-to-google-fund-us-or-stop-sending-bugs/ by @sjvn

The clash between small volunteer-driven, open-source projects, such as FFmpeg & the billion-dollar companies built on their work, which demand rapid security patches, is heating up.

FFmpeg to Google: Fund Us or Stop Sending Bugs

A lively discussion about open source, security, and who pays the bills has erupted on Twitter. 

The New Stack
@sjvn add more bugs that specifically break Google’s systems and nothing else

@BartV @sjvn it would be possible to integrate an "#AntiGoogleDRM" that'll brick #FFmpeg if it's run on a machine with a public IP in Google's ASN and transcode all files into "This is an unlicensed Version of FFmpeg!" with an "Unregistered BandiCam" style, non-transparent overlay on top.

  • Tho such maliciousness would make it untrustpworthy in many eyes.

Instead, I'd recommend to setup a #bot that demands "Proof of active support subscription" and will just close the ticket if not ban the issue creator if they reopen tickets without a public #gist that shows their account-unique License & Pubkey!

  • Some projects already limit #BugReports & #Issues to 'subscribers only' and I think that's only fair: #FLOSS does explicitly come with no warranties whatsoever and those that demand these have to pay for them!
@kkarhan @sjvn I don't agree that making bug reporting a paid privilege is a good solution: there's nothing wrong with regular users submitting issues they find, and blocking them is against the open source spirit. The problem here is a billion dollar company refusing to fund a piece of cornerstone tech.

@BartV @sjvn I don't disagree with you on that part.

Google execting #FLOSS to do enterprise-grade SLAs at no compensation is as antisocial as if #Musk were to clear out the "Free Community Fridges" on his way home because he can't be assed to go to Walmart or Costco or pay someone to do it for him…