But the blobs are there anyway in much more places, even in the SD card or touchscreen controller - I doubt I have to explain that to *you* :P
-
-
What's important to me is whether I have to reach for non-free blobs when I build software to run on the user-oriented execution unit, and whether those blobs run on that unit itself. Getting rid of blobs contained in the hardware is also important, but it's a next, distinct step
1 reply 0 retweets 0 likes -
Replying to @dos1
Why? Why is that important to you? Do you get digital cooties if you touch a blob? Not running blobs on the main CPU has practical advantages. Not *touching* blobs with the main CPU serves no purpose. That's just FSF religious nonsense.
1 reply 0 retweets 0 likes -
Replying to @marcan42
It's about clear boundaries. 100% of PureOS is free software, with all the user freedom benefits it brings. If it had non-free repos with blobs, it wouldn't be true anymore. And introducing blobs into OS for devices that could very well embed it themselves is not worth it.
1 reply 0 retweets 0 likes -
Sure, the blob is still there. But so are the blobs in all the other microcontrollers there that were already self-contained. Why make the OS "99% free plus some blobs" when you control the hardware it runs on and can maintain that boundary?
1 reply 0 retweets 0 likes -
Replying to @dos1
Because the boundary isn't doing anything for the user. It's religious. What blobs you run has practical consequences. What blobs you touch with the CPU doesn't. The FSF has built a narrative that touching blobs is bad, and the tradeoffs to implement it hurt users.
2 replies 1 retweet 3 likes -
"100% of PureOS is free software (required blobs not considered part of PureOS)" "100% of this burger is gluten-free (burger definition excludes the buns)" "100% of this car is electric (combustion engine required to drive hybrid powertrain is a separate purchase)"
2 replies 0 retweets 0 likes -
Replying to @marcan42
"100% of PureOS is free software (required blobs not considered part of PureOS)" It's not "considered", it's a very clear and tangible boundary! Better analogy would be "this tofuburger is vegan, but the french fries next to it were fried on animal fats".
2 replies 0 retweets 1 like -
And it absolutely does make a difference for the user, because the user is expected to be able to replace that whole distro with whatever they like to run instead - it's their general purpose computer after all. External blobs aren't part of that, they're external.
1 reply 0 retweets 0 likes -
Now - do I want those external blobs to be freed as well? Of course I do! Is this a part of long-term Purism strategy? Sure it is! But this is a separate goal - and one that isn't in any way incompatible with measures taken for RYF certification.
1 reply 0 retweets 0 likes
At the very minimum, the RYF measures waste time better spent freeing blobs. At worst, the program encourages (and certifies) things like devices with firmware in ROM, which are not freeable, auditable, nor verifiable compared to devices with host-loaded FW.
-
-
I already explained how I strongly disagree with the idea that flashed firmware is good for users in any way vs having blobs in the filesystem /distributed as part of the OS, and you haven't rebuked my technical arguments (like signing/verification), so... I'm done.
0 replies 0 retweets 0 likesThanks. 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.