Liberated Systemd

(github.com)

11 points | by gasull 2 hours ago

7 comments

  • wewewedxfgdf 8 minutes ago
  • stabbles 16 minutes ago
    The other day someone commented on this site that in the age of agentic coding "maintaining a fork is really not that serious of and endeavor anymore." and that's probably the case. I'm sure continuously rebasing "revert birthday field" can be fully automated.

    Then the only thing remaining is convincing a critical mass that development now happens over at `Jeffrey-Sardina/systemd` on GitHub.

  • gzread 10 minutes ago
    Why are people worried about age bracket category (optional, defaults to "over 18") but they're not worried about remote attestation (will be mandatory to view any website)?
  • SahAssar 22 minutes ago
    The birthdate doesn't actually get sent anywhere, right?

    Why would adding a field for a birthdate be "mass surveillance" anymore than having fields for email, full name, etc.?

    • gasull 13 minutes ago
      Because it's the first step.

      “Information, once collected, will be misused.”

      ― Richard Stallman, How Much Surveillance Can Democracy Withstand?, 2013

      • gzread 10 minutes ago
        So that's also for email address, username, right?
        • GrayShade 9 minutes ago
          Don't forget location.
    • GrayShade 15 minutes ago
      It doesn't, and it's optional.
  • reconnecting 26 minutes ago
    Perhaps I wasn't paying enough attention to this fork's commits, but what is actually happening with the birth date and where does it go?
    • adrian_b 9 minutes ago
      There is a stupid new California law, which requires that all operating systems must demand the age of any user, and then the OS must implement an API through which any application can ask which is the age of the current user.

      This information is supposed to be passed by browsers to the sites you visit, so that they would implement age verification.

      The systemd maintainers are among the first who have rushed to be compliant with the new law, even if compliance with abusive laws does not seem the right solution.

      The requirements of the law are incredibly stupid and for now they are trivial to circumvent, but the fear is that this is only the beginning. After the legislators see that they can force anyone to work to implement such ridiculous demands, they will demand more, eventually leading to privacy-restricting measures that will no longer be easy to circumvent.

    • dark-star 8 minutes ago
      It goes nowhere of course, but people seem to think that the age verification laws that are currently being drafted everywhere somehow make this the obvious next step.

      They don't understand that it's still all on your computer and you can of course set the birthdate to whatever you want (or not set it at all).

      tl;dr: it's a tinfoil hat fork

  • dark-star 4 minutes ago
    systemd also stores the real name of the user using this computer in the same user record. Why not remove that as well, as it could uniquely identify the user of the computer? Or the uuid field...
  • tux3 28 minutes ago
    This does a terrible job explaining, but it seems to be in protest of age verification laws in operating systems.

    The only commit is removing a user birthday field.

    • gzread 5 minutes ago
      The existence of the user birthday field is mass surveillance, but the GECOS field, which contains your full name and street address, and the username, which often contains parts of your name and is mandatory, somehow are not. Full access to your home directory, which includes all of your passwords and usernames and confidential data, also somehow is not an invasion of privacy.