this post was submitted on 04 Apr 2026
14 points (100.0% liked)
technology
24317 readers
384 users here now
On the road to fully automated luxury gay space communism.
Spreading Linux propaganda since 2020
- Ways to run Microsoft/Adobe and more on Linux
- The Ultimate FOSS Guide For Android
- Great libre software on Windows
- Hey you, the lib still using Chrome. Read this post!
Rules:
- 1. Obviously abide by the sitewide code of conduct. Bigotry will be met with an immediate ban
- 2. This community is about technology. Offtopic is permitted as long as it is kept in the comment sections
- 3. Although this is not /c/libre, FOSS related posting is tolerated, and even welcome in the case of effort posts
- 4. We believe technology should be liberating. As such, avoid promoting proprietary and/or bourgeois technology
- 5. Explanatory posts to correct the potential mistakes a comrade made in a post of their own are allowed, as long as they remain respectful
- 6. No crypto (Bitcoin, NFT, etc.) speculation, unless it is purely informative and not too cringe
- 7. Absolutely no tech bro shit. If you have a good opinion of Silicon Valley billionaires please manifest yourself so we can ban you.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Avoiding systemd is getting harder and harder though. Some sort of script or plugin would probably be best.
That's exactly why it should be avoided. The vision of the FOSS operating system was that parts were interchangeable, and you aren't locked into any one thing.
People raised the alarm bells on systemd years ago and unfortunately it seems they were correct all along.
Eh. I'm not really on the systemd hate train that a lot of people are. I think having a unified interface is good actually. Plus it's modular enough that you can absolutely add/remove components in your distro.
I also really don't think that this is a sign that they were correct, the whole point of my comment was to point out how ridiculously small this change is and it has no visible path towards becoming anything more.
systemd's whole thing is being the glue, so it makes sense for them to expand their API when changes are being proposed. Doing that ahead of time saves them headache later since people will splinter into other workarounds.
If the "age verification" stuff ends up centralizing on a systemd module, that's good actually since it means you're less likely to see people implementing it themselves in ways that are harder to see or disable.
If all of that flows through systemd, you can just turn it off on the API layer and anyone who uses it (which at this point, will probably be a lot of people since they're ahead of the game) hands off that control to a thing you as a sysadmin have easy control over.