The sad part is that it took RMS making excuses for sex trafficking for him to get kicked out. He's been a hindrance to the free software movement for many years now, in technical/licensing/endorsement/general image matters.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
What are you going on about? The whole point I'm making is that the FSF RYF stuff doesn't encourage hardware that is "almost free except for a tiny compromise", it encourages hardware that is *way less free* and opaque and unfreeable.
Tell me a *single* way in which it is better to have some proprietary firmware hidden in some inaccessible Flash memory instead of having that same exact firmware in /lib/firmware. Both included proprietary firmware, but the former deprives me of many more freedoms!
-
-
I want the freedom to *reverse engineer* the proprietary firmware, to *audit* the proprietary firmware, to *patch* the proprietary firmware, and ultimately to *replace* the proprietary firmware. The FSF *requires* depriving me of those freedoms to gain certification.
-
It also means RYF devices are untrustworthy by default, because their proprietary firmware is unauditable, and therefore its privacy implications cannot be understood. It could have one or multiple backdoors.
- Show replies
New conversation -
-
-
This Tweet is unavailable.
-
LOL no they don't. They don't audit squat. Where did you get that idea from? How are they going to audit ROM code or encrypted microcode or code for a proprietary DRAM controller sequencer architecture?
- Show replies
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.