I'm not against the idea. I don't want HP-ificiation or Samsung-ification or FAANG-ificiation or any other form of enshittification. Just require _everything_ t

I'm not against the idea. I don't want HP-ificiation or Samsung-ification or FAANG-ificiation or any other form of enshittification. Just require _everything_ to be open source to be fully certified. Without open source hardware and software, you're just buying future e-waste. I don't want some workaround like "oh yeah the certificate is for the initial release but you need to update for security and oh by the way the update is not certified". Otherwise, imagine this scenario: Company release a product and pushes out the version for the certification. Updates require new versions to be signed with a particular key. A couple months later, the key is leaked! Okay, so keys are rotated and a new update is pushed and the old key is blocked. What happens to the certification? What use is the certified key? What use is the certified source code? The certification should mandate a user-activatable factory-reset to the certified keys and code, which can't be tampered with by firmware to block or modify a different firmware from being installed.