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.

  • Magiilaro@feddit.org
    link
    fedilink
    arrow-up
    2
    ·
    2 days ago

    In advance of what? The law is already enacted, and the time until it gets active is exactly there for preparation and development.

    It would be in advance if he had done it when the law was still in the plan phase, but that is way done.

    • The D Quuuuuill@slrpnk.net
      link
      fedilink
      English
      arrow-up
      5
      ·
      2 days ago

      the law is not enacted. even in your prior comment you said this was being prepared for when the law is active and binding. no one told SystemD they had to do this. they voluntarily complied with a state law in colorado and two state laws in draft phase in other states

      • Magiilaro@feddit.org
        link
        fedilink
        arrow-up
        3
        ·
        2 days ago

        Governor Gavin Newsom signed the California Digital Age Assurance Act (AB 1043) into law on October 13, 2025.

        It is a valid law, it only has a postponed start date of January 2027 to give everyone time to get their Systems ready.

          • motogo@feddit.dk
            link
            fedilink
            arrow-up
            1
            ·
            1 day ago

            Yes! That’s how compliance works. Otherwise it would be like “Excuse me for speeding officer. I’m going to adhere to the speed limit tomorrow. I promise!” Anyway, what’s your point ?