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):

Hopefully the energy of this reaction won't be scattered among too many alternatives, although some amount of scattering is always good.

you are viewing a single comment's thread
view the rest of the comments
[–] 37 points 7 months ago* (last edited 7 months ago) (14 children)

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.

  • source
  • hideshow 14 child comments
  • [–] 18 points 7 months ago (11 children)

    I wonder how many people freaking out over this field have even looked at what other fields are on that user record. The realName field could be used to dox you! ICE and the CIA are interested in your location! Those fields have about the same level of enforcement as the new one, i.e. you can just lie.

  • source
  • parent
  • hideshow 11 child comments
  • [–] 2 points 7 months ago (10 children)

    Good examples of things that shouldn’t be there.

  • source
  • parent
  • hideshow 10 child comments
  • [–] 1 point 7 months ago (9 children)

    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

  • source
  • parent
  • hideshow 9 child comments
  • [–] 1 point 7 months ago (8 children)

    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.

  • source
  • parent
  • hideshow 8 child comments
  • [–] 2 points 7 months ago (7 children)

    then perhaps you should have made the PR rather than completely overreacting about someone else’s implementation of an entirely optional, unverified text field

  • source
  • parent
  • hideshow 7 child comments
  • [–] 1 point 7 months ago (6 children)

    I don’t see you getting involved.

  • source
  • parent
  • hideshow 6 child comments
  • [–] 1 point 7 months ago (5 children)

    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

  • source
  • parent
  • hideshow 5 child comments
  • [–] 1 point 7 months ago (4 children)
  • [–] 1 point 7 months ago (3 children)

    like i have nothing to prove to you and keep this identity separate to work adjacent activities so im not listing them :)

  • source
  • parent
  • hideshow 3 child comments