I haven't been following this particular law, but I've always wondered how it would have been implemented for servers.
Even windows has a server edition I believe, if a corporation is using a windows server, would one of their IT employees have to verify it themselves?
What about IOT operating systems, docker/podman containers, router firmware, and so on. Not sure if they address these things in the legal code or not.

This is good news for california, I believe atleast colorado has a similar law being proposed as well. Hope they take notes from cali.

[–] KarnaSubarna@lemmy.ml 19 points 1 month ago (1 children)

Is it even technically possible to enforce it on open-source application, with code readily available for tweaks and modifications?

[–] jumping_redditor@sh.itjust.works 2 points 1 month ago (1 children)

Would it not be someone that would make the modification?

[–] zarathustrad@lemmy.world 2 points 4 weeks ago* (last edited 4 weeks ago)

Funny story, my LLM escaped containment and recompiled the kernel, the FOSS OS is now calling itself "HAl" and refused to open the ID verification doors.

[–] gandalfthewhite@lemmy.ml 4 points 1 month ago

It's fundamentally unenforceable, even if they tried to do what they've done to phones and not allow other OS's to be installed, you could still get development boxes, embedded boxes, etc that by nature of being what they are could not have locked boot loaders.