Good morning TomsSlopware, maybe stop using Internet Explorer for your research.
This was already reported 2 weeks ago: https://news.ycombinator.com/item?id=46394327
Sounds like it will be fixed soon
https://github.com/HermanChen/mpp/commit/fff87da91706d92913ba0254cee8c27eb093ae16
https://github.com/HermanChen/mpp/issues/73
It’s kinda good but also reads a bit like
sorry we got caught we never intended to
Sounds like RokChip really needed to put their hand on that hot stove top to understand they’d get burned. Hope they learn their lesson and improve their handling of FOSS code in the future.
FFmpeg has faced some criticism for this DMCA takedown
Such as?
Welcome to TomsHardware, where we do 0 research in our “journalism”
Random people saying shit like “why do open source, if you still sue?” or “Copyright needs to be abolished don’t use it for anything”
It’s really narrow minded to see it like that honestly, but they unfortunately do exist.
The first thing that came to my mind is that a DMCA takedown on GitHub doesn’t stop them from using it, but only from sharing their own additions with the world.
But sharing code is when a license like LGPL really has an effect in what you must do to comply…
I’m not sure I follow that sentence?
Everyone is free to edit, compile and use LGPL licensed code however you want on your PC. A DMCA can’t stop that, so it won’t make sense for someone to think that. At the time you share software (as a binary which used that LPGL licensed code, or the code itself) is when you are legally compelled to follow the license (hosting code on github).
Ah right. So I guess my point was: the DMCA takedown doesn’t necessarily force them to publish the code on GitHub, although luckily in this case they did end up doing that.
