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/unret arded-systemd "The systemd System and Service Manager, without the ret 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.
It doesn't work quite that way. Typically you have a sequence of very small changes, all "innocuous", that lock you more and more into the previous ones. When you suddenly realize that the cumulative change is bad, you also find it's very difficult to "move away from it". This is why it's important not to give away a single inch, from the very start.
Except that this change doesn't lock us into age verification at all. On its own it's harmless. There are still steps ahead before it's actually difficult to evade. And sure, we are heading that way and it only makes sense to be prepared for the steps towards the next steps of age verification laws. It really isn't magic to comply with these small steps, as long as they themselves don't present a treat, be aware of the bigger picture and still do the work to prevent the actual OS-level age verification.
That's simply not true in this case.
With age verification, there's a very clear cut-off point that you can see and act upon:
Age verification is when you're required to verify your age.
Not just enter a number.
And the way to fight against this law isn't to "boycott" systemd.
Literally no one will notice. It's free, so using it doesn't support it.
And no one even knows whether you use it or not.
That's why I think the law is bad, but it doesn't really apply to open source software. You see the actual limit crossed, you can still fork the version from before that.
Even the law itself, as it stands, is pretty alright. It's effectively just a parental control system, the OS needs to provide the user age to applications, but that age is just whatever you type at install, without any verification. In general, if enough applications implement it, that's not a bad system to help protect kids without invading anyones privacy. Of course, it can be circumvented by the kid installing the OS themselves, but that possibility is a feature, not a bug.
The problem there is the slippery slope though.