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/ …
-
This Tweet is unavailable.
-
-
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 -
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?
1 reply 0 retweets 0 likes
*I* can audit some bizarro proprietary firmware better than whatever the FSF can do themselves, and *I* want the freedom to do so.
-
-
Replying to @marcan42
Also, making firmware immutable for this reason is ridiculous. If they want to provide a "we audited this version and it's okay" stamp, just publish the SHA256 of the binary! Making it immutable and uncheckable is nonsense!
0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.