Here spent time to think and document all the IRC chats, the Twitter thread, the attitude of the SoC manufacturer, etc.
There has to be a backstory to suddenly come after 1.5 years for an issue that could have been solved in 10 minutes.
But here, as FFmpeg is LGPL and we talk about one single file, there is even less work to do in order to fix that.
https://github.com/github/dmca/blob/master/2025/12/2025-12-1...
> ... the offending repository maintainers were informed of the problem almost 2 years ago ([private]), and did nothing to resolve it. Worse, their last comment ([private]) suggests they do not intend to resolve it at all.
Seems like the reporter gave them a lot of time to fix the problem, then when it because obvious (to them) that it was never going to be fixed they took an appropriate next step.
This is what big corporations do to the little guys, so we owe big corporations absolutely nothing more.
They gave Rockchip a year and a half to fix it. It is the responsibility of Rockchip to take care of it once they were originally notified, and the FFmpeg dvelopers have no responsibility to babysit the Rockchip folks while they fulfill their legal obligations.
If you immediately escalate to [DMCA / court] because they refuse to fix, then that's very fair, but suddenly like 2 years after silence (if, and only if that was the case, because maybe they spoke outside of Twitter/X), then it's odd.
Also it’s rude, which is reason enough not to do it.