Ignas Kiela on Nostr: 翠星石 nprofile1q…utslx nprofile1q…xvklh I see zero reasons why locking people ...
翠星石 (nprofile…vqps) nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq0cq07ulfyc7y2l8rczk9s36g8j65tq3m6xk9us8hr3ua4ktfmaqqeutslx (nprofile…tslx) nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqlksxw7gqy3tyvzvzv4wn0he6045z7k68nhnlec9tz4njkk3xdfmqaxvklh (nprofile…vklh) I see zero reasons why locking people with proprietary firmware in is better than at least leaving a possibility of loading free firmware. But that's what RYF does.
It's impossible to make a computer these days that complies with RYF without also making it fully open hardware. Because RYF doesn't just restrict loading of the firmware on each boot, it restricts modification of firmware at all. Pinephone is not RYF compliant not because it needs to load modem firmware each boot, but because it can change the modem firmware. When going with these requirements, you can't even use any remotely modern SSDs or hard drives, because their firmware can be updated.
Building hardware that FSF sees as good is building hardware that restricts your ability to modify it.
It's impossible to make a computer these days that complies with RYF without also making it fully open hardware. Because RYF doesn't just restrict loading of the firmware on each boot, it restricts modification of firmware at all. Pinephone is not RYF compliant not because it needs to load modem firmware each boot, but because it can change the modem firmware. When going with these requirements, you can't even use any remotely modern SSDs or hard drives, because their firmware can be updated.
Building hardware that FSF sees as good is building hardware that restricts your ability to modify it.