FFmpeg has issued a DMCA takedown on GitHub
twitter.comThe repo in question incorporated FFmpeg code while claiming their code is Apache 2.0-licensed over 1.5 years ago[1]
This is not allowed under the LGPL, which mandates dynamic linking against the library. They copy-pasted FFmpeg code into their repo instead.
That's not it. The LGPL doesn't require dynamic linking, just that any distributed artifacts be able to be used with derived versions of the LGPL code. Distributing buildable source under Apache 2.0 would surely qualify too.
The problem here isn't a technical violation of the LGPL, it's that Rockchip doesn't own the copyright to FFMPEG and simply doesn't have the legal authority to release it under any license other than the LGPL. What they should have done is put their modified FFMPEG code into a forked project, clearly label it with an LGPL LICENSE file, and link against that.
How does
"Distributing buildable source under Apache 2.0 would surely qualify too"
reconcile with
"doesn't own the copyright to FFMPEG and simply doesn't have the legal authority to release it under any license other than the LGPL"
You can distribute your own code under Apache along with FFMpeg under LGPL in one download
if they licenced their own code under apache 2.0 as buildable with the lgpl ffmeg code, without relicensing ffmeg as apache itself
"In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License."
They should be covered as an aggregation, provided the LGPL was intact.
The contention is that the ffmpeg code was "cut and pasted" without attribution and without preserving the license (e.g. the LGPLv2 LICENSE file). Obviously I can't check this because I don't have a clone and the repository is now blocked behind the DMCA enforcement. But at least Github/Microsoft seem to agree that there was a violation.
Microsoft/Github have no say in enforcement of a DMCA claim.
Uh... the repo has literally been taken down by GitHub: https://github.com/rockchip-linux/mpp
Not sure what you're trying to say here. DMCA takedown enforcement is 100% the responsibility of the Online Service Providers per statute. It's the mechanism by which they receive safe harbor from liability for hosting infringing content.
Yes, but Microsoft/Github do not make any determination about the validity of the claim.
Once a valid (from a process perspective) claim is submitted, the provider is required to take the claimed content down for 10 days. From there the counter claim and court processes can go back and forth.
Could there have been other / better moves with sending a reminder.
I think the devs of that Chinese company seemed to immediately acknowledge the attribution.
Now the OSS community loses the OSS code of IloveRockchip, and FFmpeg wins practically nothing, except recognition on a single file (that devs from Rockchip actually publicly acknowledged, though in a clumsy way) but loses in reputation and loses a commercial fork (and potential partner).
How do you partner with someone who has so much contempt for you they ignore the license you've given them and, when called on it, simply ignore you?
They had ample warning and ignored the license. what you're even on about?
Your original comment had this at the end...
> - Rockchip's code is gone > - FFmpeg gets nothing back > - Community loses whatever improvements existed > - Rockchip becomes an adversary, not a partner
This is all conjecture which is probably why you deleted it.
Their code isn't gone (unless they're managing their code in all the wrong ways), FFmpeg sends a message to a for-profit violation of their code, the community gets to see the ignorance Rockchip puts into the open source partnership landscape and finally... If Rockchip becomes an adversary of one of the most popular and notable OSS that they take advantage of, again, for profit then fuck Rockchip. They're not anything here other than a violator of a license and they've had plenty of warning and time to fix.
The OP deleted that sentence and I don't think it should have be flagged and unseen by others so I have vouched for it. I understand a lot of people disagree with it, and may downvote it but that is different to flagging. ( I have upvoted in just in case )
He offer perspective from a Chinese POV, so I think it is worth people reading it. ( Not that I agree with it in any shape or form )
The sentence is actually just in the comment below: https://news.ycombinator.com/item?id=46396107
You are right, and the FFmpeg devs are also 100% right and I perfectly understand that.
In fact I like the idea to push the big corps and strongly enforce devs' rights.
I think earlier enforcement would have been beneficial here, just that dropping a bomb after 1 year of silence and no reminder (and we still don't know if that was the case), is a bit unpredictable, so I wanted to raise that question
There hasn't been a year of silence. Multiple people from the community have continued bugging Rockchip to address the matter in a public issue on the now-gone Github repo. The idea of a potential DMCA claim was also brought.
All they could say was "we are too busy with the other 1000s chips we have, we will delay this indefinitely".
Ridiculous.
We are not going to loose anything. If it’s got a strong enough community then someone will publish a fork with the problem fixed
If you have to hound them to stop breaking the law they were already an adversary and the easiest way to comply would be to simply follow the license in which case everyone wins
Copy pasting code is allowed under LGPL, but doing so while removing license headers and attribution of code snippets would not be.
Only if the code you copy pasted the LGPL part into is licenced under a compatible license, and Apache is not.
The simplest way to comply while keeping your incompatible license is to isolate the LGPL part into a dynamic library, there are other ways, but it is by far the most common.
copy/pasting, or using some other mechanism to do digital duplication is irrelevant - the removal of the existing license and essentially _re-license_ without authority is the problem, no matter what the mechanism of including the code is.
this is accurate and how i should have phrased it. i should not have mentioned dynamic linking; you're right it's not relevant
thank you!
LGPL does not mandate dynamic linking, it mandates the ability to re-assemble a new version of the library. This might mean distributing object files in the case of a statically-linked application, but it is still allowed by the license.
this is accurate - thank you for the correction
this is fundamentally false. The LGPL was created because of static linking where GPLd code would be in the distributed binary.
It's an open question (the FSF has their opinion, but it has never been adjudicated) if the GPL impacts dynamic linking.
One could argue that if one ships GPL dynamic libraries together with one's non GPLd code, one is shipping an aggregate and hence the GPL infects the whole, but its more complicated to say if one ships a non GPLd binary that runs on Debian, Redhat et al and uses GPLd libraries that they ship.
they waited for more than 1.5 years and they did not forgot
They were given 1.5 YEARS of lead time. And FLOSS should treat commercial entities the same way they treat us.
Seriously, if we copied in violation their code, how many hours would pass before a DMCA violation?
FLOSS should be dictatorial in application of the license. After all, its basically free to use and remix as long as you follow the easy rules. I'm also on the same boat that Android phone creators should also be providing source fully, and should be confiscated on import for failure of copyright violations.
But ive seen FLOSS devs be like "let's be nice". Tit for tat is the best game theory so far. Time to use it.
My understanding is that the GPL doesn't have fucktons of precedent behind it in court. You bet the house on a big case and lose, the precedent will stick with GPL and may even weaken all copyleft licenses.
Also, it's better to gently apply pressure and set a track record of violators taking corrective measures so when you end up in court one day you've got a list of people and corporate entities which do comply because they believed that the terms were clear enough, which would lend weight to your argument.
Saying this as a GPL hardliner myself.
It definitely does have precedent in multiple jurisdictions. Heck, SFC just won against Vizio enforcing the GPL's terms in the US, and there have been previous wins in France and Germany.
Most licenses, EULAs, contracts and so on don't have much precedent in court. There's no reason to believe that GPL would fold once subjected to sufficiently crafty lawyers.
AFAIK it has enough precedent (also depending a bit on jurisdiction, but you only need one) but the interpretations of what that/the license should cover differ. Like f e if you wanted to argue driver devs would have to open-source their firmware blobs or their proprietary driver loaded by a kernel shim you will have a tough time and prob lose
What happens when you want to mix two libraries with different licences?
If you own one of them, mix in LGPL code, and publish it, the result is entirely LGPL.
If you don’t own it and cannot legally relicense part as LGPL, you’re not allowed to publish it.
Just because you can merge someone else’s code does not mean you’re legally allowed to do so.
This is not correct; you're simply required to follow all applicable licenses at the same time. This may or may not be possible, but is in practice quite commonly done.
> Just because you can merge someone else’s code does not mean you’re legally allowed to do so.
> This may or may not be possible
I am not sure what you are saying, that is different from the comment you replied to.
Completely depends on how much you've "mixed in", and facts specific to that individual work.
Fair use doesn't get thrown out the window because GPL authors have a certain worldview.
Second, there are a lot of non-copyrightable components to source code - if you can't copyright it - you certainly can't GPL it. These can be copied freely by anyone at any time.
You determine if the licenses are compatible first. If they are, you're fine, as long as you fulfill the terms of both licenses.
If they aren't compatible, then you can't use them together, so you have to find something else, or build the functionality yourself.
Some licenses, like LGPL, have provisions for this, some just forbid it.
In the specific ffmpeg case, you are allowed to dynamically link against it from a project with an incompatible license.
You should keep them in different directories and have the appropriate license for each directory. You can have a top-level LICENSE file explaining the situation.
This depends on the licenses.
Copyleft licenses are designed to prevent you mixing code as the licenses are generally incompatible with mixing.
More permissive license will generally allow you to mix licenses. This is why you can ship permissive code in a proprietary code base.
As for linking, “weak copyleft” license allow you to link but not to “mix” code. This is essentially the point of the LGPL.
You dynamicly link against it
I like FFmpeg, I hate doing the whole whataboutism thing, especially because FFmpeg is plainly in the right here, but... listen, FFmpeg as a product is a bunch of license violations too. Something something patents, something something, "doctrine of unclean hands." I worry that HN downvotes people who are trying to address the bigger picture here, because the net result of a lack of nuance always winds up being, "Okay, the real winners are Google and Apple."
With the exception of the Apache license, most major licenses don't cover patents. I have no idea about proprietary licenses if that's what you're talking about here, but it's a bit unclear, so it might help to go into more details than "something something" if you're intending to make a compelling case.
The GNU v3 licenses all cover software patents too, and parts of FFmpeg are under those licenses too (though I guess not the code copied and subject to this takedown, which is LGPLv2.1+).
Independent implementations of an algorithm are a different dimension from software licensing. So the “unclean hands” argument doesn’t hold water here.
Patents != copyright
What licenses are they violating?
The ones that Microsoft Apple and Google pay for, the codec licenses. FFmpeg believes that only end users need licenses for codecs, which is not only their belief, but it’s not a belief of Microsoft, Apple and Google, and it is true the sense of the status quo, but also, LGPL violations are a status quo. So you can see how it’s a bad idea for FFmpeg to make a stink about licenses.
They don't violate licenses otherwise they would have been blown out of existence a long time ago, drown lawsuit after lawsuit.
> I hate doing the whole whataboutism thing [...], but...
... yet, you did it anyway, without going into detail or providing any clue where these violations (as you claim) are.
If there's any substance to what you say, provide some details and proof, so it can be a constructive discussion, rather than just noise.
Incorporating compatible code, under different license is perfectly OK and each work can have different license, while the whole combined work is under the terms of another.
I'm honestly quite confused what FFmpeg is objecting to here, if ILoveRockchip wrote code, under a compatible license (which Apache 2.0 is wrt. LGPLv2+ which FFmpeg is licensed under) -- then that seems perfectly fine.
The repository in question is of course gone. Is it that ILoveRockchip claims that they wrote code that was written FFmpeg? That is bad, and unrelated to any license terms, or license compatibility ... just outright plagiarism.
The DMCA notice is available here: https://github.com/github/dmca/blob/master/2025/12/2025-12-1...
The notice has a list of files and says that they were copied from ffmpeg, removed the original copyright notice, added their own and licensed under the more permissive Apache license.
Thanks for the link; sadly none of the links to the repo can be viewed to see what exactly occurred.
To those downvoting, curious why? Many of the links are not viewable, since GitHub hides them, so any discussion becomes quite tricky.
You can find an archive of the links' targets at https://archive.softwareheritage.org/swh:1:dir:5861f19187336...
Interestingly, the repo has a LICENSES folder that contains the text of the licenses used in the repo:
https://archive.softwareheritage.org/browse/directory/ed4b20...
And yep, they only included the most openly permissive ones there (APL2 and MIT), completely skipping everything else. Ugh.
Maybe because if the ffmpeg people say they have a reason and they've waited 1 year and a half for compliance, we trust them more than whoever relicensed their code without permission.
I didn't downvote. I suspect people did because it sounded like you were defending ILoveRockchip's actions, based on either 1) not understanding what they did, and/or 2) not having access to the facts. People get snippy about abusing Free Software.
Here is the github thread which had some recent discussion before the repo was taken down. Rockchip said something like it would be too much work to fix the licenses for all the new chips they are creating.
https://web.archive.org/web/20251103193914/https://github.co...
The archive isn't very good for the thread. Is that what they said though? From the comments I see they said "we're working on it, but we're busy with XYZ" and then months passed.
Archive won't load the remaining 3 items for me.
Yes it's not loading on the archive but I was following the thread closely, it was said recently within the last few months which prompted further discussion and this action by ffmpeg.
100% my assumptions but:
They were never really working on it, they thought it would just go away. Maybe some junior/senior dev took a shot at it, gave a project plan and it went nowhere.
I wonder how this will work with AI stuff generating code without any source or attribution. It’s not like the LLMs make this stuff up out of thin air it comes from source material.
Best case scenario is it nukes the whole concept of software patents and the whole ugly industry of copyright hoarding. The idea that perpetual rent-seeking is a natural extension and intended outcome of the legal concepts of copyrights and patents is bizarre.
I cannot imagine it somehow impacts parents.
Copyright and patents are completely independent concepts.
The “perpetual” part is the issue but “rent seeking” is the entire reason that copyright and patents exist to begin with.
No — providing funding to promote creation and discovery is why those exist; granting a temporary monopoly is the mechanism meant to accomplish that goal.
This sounds pedantic, but it’s important to not mistake the means for an end:
> To promote the Progress of Science and useful Arts, by securing for limited Times to Authors and Inventors the exclusive Right to their respective Writings and Discoveries;
https://constitution.congress.gov/browse/article-1/section-8...
I wish I could get defensive protection against the millions and millions of bad software parents out there. But there is no such thing.
Did you know that Facebook owns the patent on autocompletes? Yahoo owned it and Facebook bought it from them as kind of a privately owned nuclear weapon to create a doctrine of mutually assured destruction with other companies who own nuclear-weapons-grade patents.
Of course the penalty for violating a patent is much worse if you know you are doing it, so companies are very much not eager to have the additional liability that comes with their employees being aware that every autocomplete is a violation of patent law.
Everything humans make up also comes from source material.
The real (legal) question in either case, is how much is actually copied, and how obvious is it.
I mostly agree with you, but if a human straight up copies work under copyright they’re violating the law. Seems like a LLM should be held to the same standard unless they should be even less beholden to the law than people.
It’s also incredibly hard to tell if a LLM copied something since you can’t ask it in court and it probably can’t even tell you if it did.
From what I have seen, the (US) courts seem to make a distinction between 100% machine-automated output with no manual prompting at all, versus a human giving it specific instructions on what to generate. (And yes I realize everything a computer does requires prior instruction of some kind.)
But the issue with copyright I think comes from the distribution of a (potentially derivative or transformative in the legal sense) work, which I would say is typically done manually by a human to some extent, so I think they would be on the hook for any potential violations in that case, possibly even if they cannot actually produce sources themselves since it was LLM-generated.
But the legal test always seems to come back to what I said before, simply "how much was copied, and how obvious is it?" which is going to be up to the subjective interpretation of each judge of every case.
Not true. That's philosophical skepticism and was roundly refuted long ago.
Source:
I don't think anyone really disputes what should be done when an LLM violates copyright in a way that would be a violation if a human did it.
Questions about LLMs are primarily about whether it's legal for them to do something that would be legal for a human to do and secondarily about the technical feasibility of policing them at all.
Everything is a derivative work.
> I wonder how this will work with AI stuff generating code without any source or attribution.
It's already fixed. Anything you make with AI cannot be protected in any way (UK gives some leeway on certain types of creations).
So if it mimics code from ffmpeg for example, then ffmpeg wins.
Llm's do not verbatim disgorge chunks of the code they were trained on.
I think it's probably less frequent nowadays, but it very much does happen. This still-active lawsuit[0] was made in response to LLMs generating verbatim chunks of code that they were trained on.[1]
[0] https://githubcopilotlitigation.com [1] https://www.theverge.com/2022/11/8/23446821/microsoft-openai...
You can still very trivially get entire chunks of code from Copilot including even literal author names (simply by prodding with a doxygen tag).
They do, and, early on, Microsoft (and perhaps others) put in some checks to try to hide that.
ChatGPT has given me code with comments so specific I found the original 6 year old github.
How long ago was this?
Doesn’t invalidate your story in the slightest - I just know they’ve gotta be chasing this, specifically, like it’s life or death.
Surely they do sometimes?
A 26-sided die reproduces chuncks of source code. What's the dividing line?
This is a multi-terabyte sized dice that is not at all random AND has most definitely copied the source code in question to begin with.
The die is certainly not multi-terabyte. A more realistic number would be 32k-sided to 50k-sided if we want to go with a pretty average token vocabulary size.
Really, it comes down to encoding. Arbitrarily short utf-8 encoded strings can be generated using a coin flip.
The number of sides has nothing to do with the data within. It's not random and sometimes it repeats things in an obviously non-chance way.
Of course, it's random and by chance - tokens are literally sampled from a predicted probability distribution. If you mean chance=uniform probability you have to articulate that.
It's trivially true that arbitrarily short reconstructions can be reproduced by virtually any random process and reconstruction length scales with the similarity in output distribution to that of the target. This really shouldn't be controversial.
My point is that matching sequence length and distributional similarity are both quantifiable. Where do you draw the line?
> Of course, it's random and by chance - tokens are literally sampled from a predicted probability distribution.
Picking randomly out of a non-random distribution doesn't give you a random result.
And you don't have to use randomness to pick tokens.
> If you mean chance=uniform probability you have to articulate that.
Don't be a pain. This isn't about uniform distribution versus other generic distribution. This is about the very elaborate calculations that exist on a per-token basis specifically to make the next token plausible and exclude the vast majority of tokens.
> My point is that matching sequence length and distributional similarity are both quantifiable. Where do you draw the line?
Any reasonable line has examples that cross it from many models. Very long segments that can be reproduced. Because many models were trained in a way that overfits certain pieces of code and basically causes them to be memorized.
> Very long segments that can be reproduced
Right, and very short segments can also be reproduced. Let's say that "//" is an arbitrarily short segment that matches some source code. This is trivially true. I could write "//" on a coin and half the time it's going to land "//". Let's agree that's a lower bound.
I don't even disagree that there is an upper bound. Surely reproducing a repo in its entirety is a match.
So there must exist a line between the two that divides too short and too long.
Again, by what basis do you draw a line between a 1 token reproduction and a 1,000 token reproduction? 5, 10, 20, 50? How is it justified? Purely "reasonableness"?
Why do you want me to pick a number so bad?
There are very very long examples that are clearly memorization.
Like, if a model was trained on all the code in the world except that specific example, the chance of it producing that snippet is less than a billionth of a billionth of a percent. But that snippet got fed in so many times it gets treated like a standard idiom and memorized in full.
Is that a clear enough threshold for you?
I don't know where the exact line is, but I know it's somewhere inside this big ballpark, and there are examples that go past the entire ballpark.
I don't care where specifically the bound is.
IIRC at a point it was 6 line of code
Takedown letter: https://github.com/github/dmca/blob/master/2025/12/2025-12-1...
LGPL allows compiling the whole of ffmpeg into a so or lib and then dynamically linking from there for your closed source code. That's the main difference between LGPL and GPL.
But if you change or add something in building ffmpeg.so that should be GPLed.
Apparently they copied some files from ffmpeg mixed with their propitiatory code and compiled it as a whole. That's the problem here.
Copyright law defines derivative work by substantial similarity and dependence, not by technical mechanisms like linking. Technical measures such as linking is not a copyright concept.
Dynamic linking is a condition for LGPL compliance, but it is not sufficient. Dynamic linking does not automatically prevent a combined work from being a derived work.
> Dynamic linking is a condition for LGPL compliance
No, it isn’t. The condition says to allow your users to make and use their own modifications to the part of the software which falls under the LGPL. Dynamic linking is only a convenient way of allowing this, not a requirement.
The law doesn't seem to work anymore. There are so many cases where someone can do illegal stuff in plain sight and nothing can be done about it. Not everyone has tens of thousands or hundreds of thousands of dollars to spare to get a lawyer. By the time you manage to save up the money, you realize that this system is absolutely crooked and that you don't trust it to obtain justice anyway even with the lawyers and even if you are legally in the right.
The law exists mostly to oppress. It's exactly the argument that gun proponents make "Only the good guys obey gun laws, so only the bad guys have guns."
All the good guys are losing following the law, all the bad guys are winning by violating the law. Frankly, at this stage, they write the laws.
I recently had to deal with a ministry in Canada, where a worker who had been there since 20 years ago failed even a basic test of competence in reading comprehension. Then multiple issues with the OPC (Office of Privacy Commissioner) failing entirely on a basic issue.
Another example exists in Ontario's tenant laws constantly being criticized as enabling bad tenant behavior, but reading the statute full of many month delays for landlords and 2 day notices for tenants paints a more realistic picture.
In fact, one such landlord lied, admitted to lying, and then had their lie influence the decision in their favor, despite it being known to be false, by their own word. The appeal mentioned discretion of the adjudicator.
Not sure how long that can go on before a collapse, but I can't imagine it's very long.
Incompetence is a taboo. It shouldn't be.
I think it should be perfectly OK to make value judgements of other people, and if they are backed by evidence, make them publicly and make them have consequences for that person's position.
A recent review of one of Canada's Federal Institutions showed the correct advice was given 17% of the time[0]. 83% failure rate. Not a soul has been fired unless something changed recently.
I do agree however with your assessment because any (additional) accountability would improve matters.
[0] https://globalnews.ca/news/11487484/cra-tax-service-calls-au...
I can't help but look at it as the sign of an empire in decline. It's only a matter of time before more people realize what you're saying (particularly the last two paragraphs) and the system falls apart.
So here we have the good guys using the law and ... at least temporarily ... winning... so what's your point?
You can see it everywhere. In this case, the fact that it took 2 years. And of course now that FFmpeg is getting more exposure in the media due to their association with AI hype, now they finally get 'fair' legal treatment... I don't call that winning. I see this over and over. Same thing all over the west.
I remember Rowan Atkinson (the UK actor) made a speech about this effect a couple of years ago and never heard about it since but definitely feeling it more and more... No exposure, no money, no legal representation. And at the same time we are being gaslit about our privilege.
> In this case, the fact that it took 2 years. And of course now that FFmpeg is getting more exposure in the media due to their association with AI hype, now they finally get 'fair' legal treatment... I don't call that winning.
It took 2 years because FFmpeg waited 2 years to send a DMCA notice to Github, not because of delays in the legal system. I think you are conflating different unrelated issues here.
Not familiar with Rockchip. Plenty of searches come up with cases of people incorporating ffmpeg into Rockchip projects. I still see the license files and headers. What is different with this DMCA takedown?
The one you reference doesn't look like it misrepresents the licenses, i.e. of you use it to make your own derivative you would expect to have to share modifications you make to the LGPL code.
That's because you can incorporate LGPL code into any project as long as you respect the license.
Rockchip is a hardware platform, what hardware the code runs on isn't relevant here.
Since the link to the actual code is DMCA’d in Rockchip’s repository, anyone have a fork so we can form an opinion independently?
So the comments explaining the situation from the HN community aren’t good enough?
If the repository were still accessible, the only thing I’d be looking for is whether the LGPL portions were modified or statically linked. Absent that, the license-based explanation makes sense.
I guess not?
Would be nice to live in a world where the stupidity of "intellectual property" and "copyright" had already been laughed out of the room. But alas we live in this one, the moral and legal equivalent of walking through a park covered in trash.
You largely have bill gates to thank. Code is math and anyone who insists otherwise is a personof questionable morals, intelligence, or both.
Clash of cultures. https://en.wikipedia.org/wiki/Shanzhai#Regulation vs. the 鬼子 鬼佬 老外
What's the clash? Is the claim that China lacks the notion of copyright, or that they don't care about the rule of law?
No, they have that. It's just not universally applied, or rather with 'some flexibility' instead :-)
It remains to be seen how much 'pull' FFmpeg has against the 'push' of Rockchip.
Not a fan of the CCP, but GH in general has a big problem with users not understanding and respecting licensing and passing off others' code as their own, sometimems unintentionally, often not.
someone post an archive link, I can't read that
Does this work for you? https://xcancel.com/FFmpeg/status/2004599109559496984
Xlssid
Is working around accessing an embargoed site really any better than just accessing it directly? Morally, what's the difference?
If everyone just actively boycotted that site, it would become irrelevant overnight. Anything else is simply condoning it continued existence. Don't kid yourself.
The issue is that you need an account to view the replies, not that there's a moral opposition to visiting the website (though it could be that too).
What's stopping you from making the archive link yourself?
I'd like to learn but I can't find a guide on how to do it. Could you please share one?
Go to https://archive.is and paste the URL into the box.
Chinese is steal of coding, which can pop device company use ffmpeg, 有利有弊
FOSS is and always was a scam, in order to feed tons of code to LLMs and kicking coders in the balls, so they could not monetize their work. And, noone cares about the licenses, everyone steals and robs whatever is at arms length.
So FOSS is bad and commercial software is bad? What's left - going outside and touching some grass?
FOSS has been a thing for decades longer than LLMs have even been a vague notion.
And that doesn't mean it's not 100% bullshit. Also, nation states have 10-20 year plans... yet your mental horizon spans a few days at most.
Time to create a decentralized, blockchain-based GitHub (GitCoin?) and have every commit be a transaction on the chain. Nothing would ever be takedownable.
Git already has a blockchain; what you will need to do next is to make copies of the objects of the repositories on other servers as well. (However, I don't know if the blockchain includes tags on git (it seems to me that it might not but I don't know enough about it), although it does include objects. Fossil includes tags in the blockchain as well as files, commits, etc.)
I mean, torrenting is decentralised and not technically takedownable. But it was entirely possible to make it legally painful for people involved in it, as seen in eg. The Pirate Bay, megaupload or an entire cease-and-desist letter industry around individual torrenting users
Intentional noncompliance with copyright law can get you quite a distance, but there's a lot of money involved, so if you ever catch the wrong kind of attention, usually by being too successful, you tend to get smacked.
> I mean, torrenting is decentralised and not technically takedownable.
It's fairly trivial to block torrent traffic.
The cost would be incredible even for just a pointer to distributed file storage
Github stores about 19 PB. That would cost about $20k a year on Filecoin. Filecoin currently has more supply than demand because it's speculation-driven right now.
There wouldn't be an org maintaining it. You would just buy $100 worth of GitCoin and that would be enough for 10000 commits, or something like that.
Yes, using blockchain to defraud the GPL.
Checks out sufficiently dystopian, yep.
If you could work some gratuitous LLM in there, we could be a little closer to torment-nexus territory. Keep working at it.
Ooh, how about instead of being able to author a commit message, you're forced to let an LLM write it for you based on the diff since last commit. And that the LLM runs distributed on the blockchain, so it's monstrously slow, and has to be paid for with a 'gas' analogue so there's huge transaction fees as well.
That's the most techbro-brained idea I could come up with.
git already uses a blockchain lol