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.
The reaction by definition is unproductive. I think Brodie Robertson did a good job covering this the other day.
It’s literally an addition of an optional text field in a collection of already optional and often unfilled text fields. In a small part of the systemD suite. UserD, with no checking or enforcement. Which has value in business and corporate environments. In the form of a pull request from an external, unaffiliated coder.
Regardless of where you stand on metas push for age-gating everything so they don’t have to. Which if you aren’t against it, you’re a fool. This is all way more reactionary and less substantive than the valid sysV vs systemD debate.
I wonder how many people freaking out over this field have even looked at what other fields are on that user record. The
realNamefield could be used to dox you! ICE and the CIA are interested in yourlocation! Those fields have about the same level of enforcement as the new one, i.e. you can just lie.Good examples of things that shouldn’t be there.
why not? in multi user environments the user could be in any number of office locations… tracking that information is useful
just because it’s not useful for you doesn’t mean it’s not useful to anyone
Race, gender, sexual preference, these are all useful to someone and yet should not be data collected. Name, sure. Birth date, no. I’m fine with an Adult Boolean.
then perhaps you should have made the PR rather than completely overreacting about someone else’s implementation of an entirely optional, unverified text field
I don’t see you getting involved.
i’m fine with the change. why would i get involved when im involved with other FOSS efforts and much prefer systemd to every other option
Like what?
While we’re at it, we could add a race and sexual orientation field, this could have value for business in some countries!
A JewONo field might be useful in some counties too
Value for business ≠ Mandated by law