| ▲ | rvnx 7 hours ago |
| [flagged] |
|
| ▲ | akerl_ 7 hours ago | parent | next [-] |
| The amount of armchair quarterbacking here is wild. |
| |
| ▲ | rvnx 7 hours ago | parent [-] | | Then waiting to see how they addressed these points and what were the approaches taken and why ? 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. | | |
| ▲ | kelnos 6 hours ago | parent [-] | | Then why didn't Rockchip solve it in 10 minutes? | | |
| ▲ | rvnx 6 hours ago | parent [-] | | Bad decision and risk/reward calculation for sure. If it's code that is core to your stuff, and it is GPL'd, it's (technically) very tricky to solve. 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. |
|
|
|
|
| ▲ | Blackthorn 7 hours ago | parent | prev | next [-] |
| Deadline and reminders? They aren't teachers and Rockchip isn't a student, they are the victims here and Rockchip is the one at fault. Let's stop literally victim blaming them for how they responded. |
| |
| ▲ | rvnx 6 hours ago | parent [-] | | To be clear: Rockchip is at fault, 100%. I would sue (and obv DMCA) any company who takes my code and refuses to attribute it. 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. | | |
| ▲ | akerl_ 6 hours ago | parent | next [-] | | Maybe spend less time policing how other people are allowed to act, especially when you’re speculating wildly about the presence or content of communications | | |
| ▲ | rvnx 6 hours ago | parent [-] | | It's a call to push the devs to freely say what happened in the background, there are many hints at that "I wonder if...?" "What could have happened that it escalated?" "Why there were no public reminders, what happened in the back", etc, etc, nothing much, these questions are deliberately open. | | |
| ▲ | akerl_ 6 hours ago | parent [-] | | Oh. Being rude and suggesting the devs made (in your opinion) a mistake based on your guess at their actions is not going to be an effective way to get them to elaborate on their legal strategy. Also it’s rude, which is reason enough not to do it. |
|
| |
| ▲ | michaelmrose 6 hours ago | parent | prev [-] | | In the adult world you don't get any warnings when you break the law. |
|
|
|
| ▲ | kelnos 6 hours ago | parent | prev [-] |
| That's bullshit. The FFmpeg devs were well within their rights to even send a DMCA takedown notice, immediately, without asking nicely first. 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. |
| |
| ▲ | 6 hours ago | parent | next [-] | | [deleted] | |
| ▲ | Fnoord 5 hours ago | parent | prev [-] | | Yeah. This is like waiting 90 days before releasing a full disclosure on a vulnerability, and then complaining you could have contacted us and given us time, we only had 90 days now. Gaslighting 101. Those 90 days gives all those with a lot if resources and sitting on zero days (such as Cellebrite) time to play for free. |
|
