With Linux being the standard for server systems there is no way to force locked bootloaders everywhere without making the whole web and a lot of companies collapse. But I expect more limitations regarding desktop systems. It’s hard to tell at this point because it’s a complex issue, not only from an economical but also political point of view (Mass surveillance).
Oh sorry about that, it’s still showing up as a bot for me but it’s fine on your instance. I think the information just hasn’t federated over to lemmy.ca yet
It might, but I think it might be a federation bug between our instances. I haven’t seen one like this before, but I’ll keep an eye out to see if it happens again / there’s a pattern.
You could also try setting yourself as a bot, saving, and then reversing it again. That might prompt your instance to send out the information again.
With Linux being the standard for server systems there is no way to force locked bootloaders everywhere without making the whole web and a lot of companies collapse. But I expect more limitations regarding desktop systems. It’s hard to tell at this point because it’s a complex issue, not only from an economical but also political point of view (Mass surveillance).
Don’t I own this hardware? Can I not do what I want with it?
You own the hardware but not the software.
And that includes the firmware required for you to load your software.
Case in point:
Find a recently-ish manufactured used Chromebook/chromebox, and try to unlock the BIOS so you can slap a different OS on it
Source: it me 🫠
You’ll shoot your eye out, kid.
/s
Your account is marked as a bot by the way, you can fix that in your user settings
I already did, but thanks nonethless.
Oh sorry about that, it’s still showing up as a bot for me but it’s fine on your instance. I think the information just hasn’t federated over to lemmy.ca yet
Interesting. Maybe it helps if I log off?
It might, but I think it might be a federation bug between our instances. I haven’t seen one like this before, but I’ll keep an eye out to see if it happens again / there’s a pattern.
You could also try setting yourself as a bot, saving, and then reversing it again. That might prompt your instance to send out the information again.
Thanks, I will try to switch it on and off again.
Beep-boop!
Companion (2025)