4 ms·
> And it would be news to me, that it is now completely free of binary blobs and their claims always felt a little bit dishonest to me. It's the only phone run
by fsflover 5y ago
> And it would be news to me, that it is now completely free of binary blobs and their claims always felt a little bit dishonest to me.
It's the only phone running FSF-endorsed OS without binary blobs, PureOS. It's recommended by the FSF [0]. More details here [1].
[0] https://www.fsf.org/givingguide/v11/ https://www.fsf.org/givingguide/v11/
[1] https://source.puri.sm/Librem5/community-wiki/-/wikis/Frequently-Asked-Questions#15-how-innovative-is-the-librem-5 https://source.puri.sm/Librem5/community-wiki/-/wikis/Freque...
- detaro 5y agoNote that the FSF takes the position that binary blobs that are in non-writable memory and executed by secondary processors are part of the hardware and thus not relevant for judging the openness under RYF criteria. Which is how the Librem5 achieves that status, by deliberately picking components that do not use firmware upload from the host CPU but rather ship with the firmware in non-writable memory, and by adding read-only memory that is only used in the pre-boot environment. The OS is blob-free because the thing is engineered to make the blobs inaccessible to the OS. Which is a valid choice, since entirely blob-free would be impossible to make and ship, but I also see why people disagree that "blob-free" is a good description for the device.
- deleted 5y ago[deleted]