there’s also a push for making opensource exempt from it Let’s hope it succeeds. Actually, let’s hope the law is overturned entirely. And while we’re at it, let’s hope Meta fails, crashes, burns and takes all its bullshit down with it, but that’s only tangentially related. It depends, if the purpose is age verification then yes I will oppose it. Then I’ll not tell you what I intend to use that encrypted hash I’m writing to my app’s data storage for. Any data storage can be abused. This one is transparent about its content, but I don’t see anything implying that you have to enter anything, let alone have to enter your actual birthdate. It can be used for parental controls, it can be used for age restrictions, but if I implement age verification, where I store that data on your machine is the least of your worries. Where I store your ID on my machine, on the other hand, should be more concerning, and even more so the fact that I need your ID at all. We can argue whether this is necessary, whether it can serve reasonable use cases (such as voluntary parental controls), but at the end of the day, it’s such a small and exchangeable part of the system that it’s not worth the shit people give systemd over it. I think controlled, transparent storage is better than intransparent, and any storage is only as evil as the things using it. Target those things instead.