Call me when the FSF isn't actively hurting the cause for hardware freedon by having bass-ackwards certification rules that result in designs where non-free parts are made invisible and untouchable and unfreeable.
-
-
This Tweet is unavailable.
-
They have a "secondary processor exception" that requires nonfree firmware to be hidden and immutable, leading to nonsense like this:https://puri.sm/posts/librem5-solving-the-first-fsf-ryf-hurdle/ …
3 replies 1 retweet 4 likes -
This Tweet is unavailable.
-
Ah, so proprietary firmware is fine as long as you can't see it, change it, audit it, improve it (patching), or replace it with free firmware. Gotcha. Sorry, but I'm not interested in your image of "freedom" then. That's not freedom, it's bullshit.
1 reply 0 retweets 4 likes -
Replying to @marcan42
Freedom is having all proprietary firmware that you can't escape or get rid of live in /lib/firmware, so at *least* you can inspect it, decide if you want to trust it, know exactly what version is used, and perhaps one day decide to write a free version.
0 replies 0 retweets 2 likes -
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.
1 reply 0 retweets 1 like -
Replying to @marcan42
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!
1 reply 0 retweets 0 likes -
Replying to @marcan42
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.
1 reply 0 retweets 3 likes
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.
-
-
This Tweet is unavailable.
-
Yes, but because it's also applied to devices that do, it's meaningless as a certification, because it doesn't certify anything practical.
0 replies 0 retweets 0 likes
End of conversation
-
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.