Reading up on the @Puri_sm Librem 5. Nice idea, but it's a damn shame they're using the @FSF RYF certification as a goal and to guide the development process. RYF is total nonsense that encourages *decreasing* user freedom.
Show this thread
-
-
A 100% blob-free, Libre world would be nice. Unfortunately, that is not an achievable goal today. The FSF knows this. The solution they came up with? Make sure the user can't *see* any of the proprietary firmware. As long as they don't see it, nobody will complain. Brilliant.
3 replies 1 retweet 23 likesShow this thread -
So RYF has a "secondary processor exception". Which basically means that as long as proprietary firmware is stored separately from the Free™ part, and you can't touch it, and you're firewalled from it, Everything Is Peachy.
3 replies 0 retweets 26 likesShow this thread -
This is, of course, total crap. A device that respects user freedom is a device that *allows* the user to modify proprietary firmware, that *exposes* exactly what proprietary firmware is there, and that *encourages* reverse engineering to produce a Free version.
2 replies 4 retweets 45 likesShow this thread -
What *I* want is hardware with exactly as much proprietary firmware to make it practical (and no more), where all of it is in /lib/firmware (or equivalent). No secret flash memories. I can mess and reverse engineer it all. This is the exact opposite of what the FSF encourages.
1 reply 1 retweet 30 likesShow this thread -
This Tweet is unavailable.
You can write proprietary blobs for RISC-V too.
10:54 PM - 18 Sep 2018
0 replies
0 retweets
0 likes
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.