https://piefed.zip/u/Sunshine posted on Apr 5, 2026 11:18
You could put it into the
archinstallscript and just never finish the installation if there is no age set. You could also prevent a user from logging into an account that has no age set, this could be achived by modified core packages in thebasepackage.
My (rather limited) understanding is that Arch can be installed both without the archinstall script and without a user. Also, the rest of your comment covers how stupid it is to require a value anyway since people can put whatever they want.
Outside of that, it’s all open source. It’s possible to fork and remove the field entirely from an install script, distro, or even systemd itself.
Nobody can enforce this in the open source world. This is honestly the strongest argument for an open source exemption in these laws. It cannot be enforced on open source OSs.
that Arch can be installed both without the archinstall script
Yes. But it would protect them from legal liability.
If it means nothing, then why adding it?
Because some OS vendors based in the US might have to comply with the law, if you like it or not. System76 or RedHat will not have a choice unless the laws will get repelled.
That’s the way I see it as well. Some distros are going to want to or be forced to comply with the laws, so offering the option seems sensible on systemd’s part.
Nobody is forcing distros that don’t want to comply to use it.
Slippery slope of compliance, magat
Give it a few days, I got a popup saying there was an issue, they’re working on it.
Invidious is certainly worth it, even though you lose live feeds at the moment. You can even remove comments and trending. If you want to subscribe to a channel, you can do it without YouTube.
Yeah might be the IP range of the provide. Also sometimes it stops working till you update. But I expect the hetzner IP range has more than one self hosted instance on it so probably gets tagged for the whole range.
A lot of people simply don’t have time to go the extra steps.
Instead you should be focused on secure by default design. E.g. not setting a static router password to admin admin.
It’s stupid in this day and age to continue to see default logins occur still.
simply don’t have time
Sorry, but that is no reason. That’s a bit akin to having a dog and saying: “Nah I don’t have time to walk the dog now”. Selfhosting something that is publicly available (not as in “everyone can use it” but “everyone can access it”) bears some level of responsibility. You either make the time to properly set up and maintain it, or you shouldn’t selfhost stuff.