@bytebro

It's very unlikely that anything of the sort will occur. There is simply a complete disconnect between Microsoft/Google/Apple user accounts anything that firmware can record in persistent storage before an operating system has even started up.

I predicted, as you probably saw, the form that the compliance measures would take for #Unix and Unix-like operating systems on 2026-03-01, and both 11 hours and about 4 days later they took that form from two different people. One with pull requests on GitHub, one in the very FediVerse thread that I began.

It is operating systems that will see (and indeed have seen) the updates bringing this. Not firmwares.

#AgeVerification #systemd #FreeBSD #NetBSD #OpenBSD #MidnightBSD

@raymierussell

You are.

I've been following this since #MidnightBSD drew it to everyone's attention, and have directly read the bills in the 4 state legislatures that I know of, done my own analyses and compared with the analyses of others.

The problem is that legislators use fairly uncontroversial definitions that won't surprise software people of 'operating system', 'application', and 'developer'; define a really broad concept of a 'covered application store'; and place onuses on operating system makers and application developers, the latter being required to have their apps ask about age, and the former being required to have their operating system provide an API for answering the questions.

https://mastodonapp.uk/@JdeBP/116268403720368221

[Continued…]
@morgant @ShadowInTheVoid

#USLaw #AgeVerification #ZXSpectrum #retrocomputing