- cross-posted to:
- linux@programming.dev
- cross-posted to:
- linux@programming.dev
cross-posted from: https://lemmy.ca/post/62192988
The latest changes implemented in the Systemd repo, related to or prompted by age-verification laws, have made many people unhappy (I suppose links about this aren’t necessary). This has led to a surge in Systemd forks during the last days (“surge” because there have always been plenty of forks). Here are some forks that explicitly mention those changes as their reason for forking (rough time ordering taken from the fork page):
paramazo/systemd “The systemd System and Service Manager without age verification”
ganitam/systemd “Systemd fork just before the Age Verification addition. Hoping more capable developers and maintainers do same…”
GSYT-Productions/systemd-fork “The systemd System and Service Manager, without the stupid Age Verification”
speedythesnail/unre tarded-systemd “The systemd System and Service Manager, without the r e t arded age-verification commits”
ta13579/systemd “The systemd System and Service Manager WITHOUT THE FUCKING AGE CHECKS”
r4shsec/systemd-no-age-verification “This is systemd but without the age verification made via pull request https://github.com/systemd/systemd/pull/40978”
Pingasmaster/fightthesystemd “Systemd without the nonsense: no age verification, no lighthouse built-in.”
Jeffrey-Sardina/system “Liberated systemd – no surveillance. Ever.”
HaplessIdiot/systemd-saneagecheck “The systemd System and Service Manager with age verification bypass and polling rate options for said feature”
Queer-Coded-LGBTQ/systemd-fuck-california “The systemd System and Service Manager, but without age bs added in.”
Codiak540/unshitted-systemd “A fork of systemd aiming to strip the Age verification. Sue me california.”
Hopefully the energy of this reaction won’t be scattered among too many alternatives, although some amount of scattering is always good.
Did you read the freaking merge https://github.com/systemd/systemd/pull/40954
Nope. No one did. It’s all drama farming and ignorant apoplectic panic. I’d absolutely be interested to know more about the person behind the merge request. Apparently they have submitted similar code to several other projects for the same purpose. But it’s just fashionable to hate on systemD right now. At least the sysV vs systemD guys have valid issues. Even though as a 30-year Linux user, I wouldn’t go back to sysV inits. I do not miss having to use poorly documented or outright undocumented tricks, tips, and arcana to write basic process watchdogs and initialization scripts.
It’s hard enough for maintainers and devs to fight ai and governments. If you wanna go against someone go against corpos and government not people doing their hobbies.
Yes, time and effort would be infinitely better spent yelling at the local and national governments pushing for this to be implemented at the behest of meta. Than outrage of an optional text field.
We should have them add ss# too, since it’s non-privileged. What could go wrong?
What could go wrong if in your system there exists a standard place where you could put some magic string?
Remember, no one is forcing you to put the magic string in.
No one is forcing the magic string YET. But to think some governments won’t enforce that later is contrary to reality. The direction of the world is very clear…
That’s not a thing in like every single country. Might as well add a “Name of the Chinese primary school you graduated from” field, at least that would have more users.
Whatever you wanna call it. Let’s add that. Gender, gender between your legs, marriage status, race is also super important.
It’s just a field… so why not?