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.

  • Paulemeister@feddit.org
    link
    fedilink
    arrow-up
    5
    arrow-down
    2
    ·
    5 hours ago

    As long as it’s offline I don’t see a problem of implementing this. It’s a nieche use case, but why not? No program has to use the interface. It does what’s on the can: If I have a kid with a user not in wheel, it can install stuff on user level but might be “safe” from programs it is not supposed to use. Are people saying this is a slippery slope?

    • bearboiblake@pawb.social
      link
      fedilink
      English
      arrow-up
      3
      ·
      2 hours ago

      Yes, thin end of the wedge. Authoritarianism happens little by little, then all at once. It must be furiously resisted by those of us who care about freedom and privacy.

    • RedWedding@lemmygrad.ml
      link
      fedilink
      arrow-up
      3
      ·
      5 hours ago

      It is a slippery slope, because it came as a response to a law. The law itself does not require a real verification for now, but it is clearly a step in this direction. If we look how governments world wide push for laws to undermine privacy for control, these laws are part of this push.

      The birth field itself might even be a “good” tool for parents (I am not a fan of restricting your kids, but I know many are). The problem many people have with the changes by systemd is their anticipatory obedience with these laws.