Some of you need to watch this video, and hang your head in shame.

Dylan Taylor has been receiving constant harassment, including threats to his life and safety, for actions done collectively by SystemD. The article by Sam Bent was explictly mentioned as part of the harassment campaign, and rightfully so.

I don’t think enough people realize that this is catastrophically bad. It’ll discourage people from becoming open source developers, it’ll discourage people from using Linux, and it’ll discourage legislators from taking the Linux community seriously.

If you ever wished ill upon another human being for complying with a relatively inconsequential law, you are better off never touching a computer again. The Linux community has collectively gone so far beyond what is acceptable here.

  • lightnsfw@reddthat.com
    4·
    12 hours ago

    Its not leaving a lot of choice if it’s part of systemd and I’d wager far more people do not want this than were asking for it. There’s no benefit to it except for the government and corporations that want your data.

    • FauxLiving@lemmy.world
      11·
      12 hours ago

      The field doesn’t do anything by itself. There is zero harm inflicted on people using systemd. There are probably lots of features of systemd that you don’t want or use and the entire negative effect that you suffer is a few megabytes less free storage space.

      The only way the field would be used is if a person decided to use a different piece of software that wants a birthdate. If they don’t choose to install such a program then the field is no more a danger than the realName or location fields. They have scary sounding labels but do absolutely nothing unless the user chooses to use them.

      • lightnsfw@reddthat.com
        1·
        2 hours ago

        The only way the field would be used is if a person decided to use a different piece of software that wants a birthdate.

        It leave the door open for this to happen. A malicious software may not advertise that it is harvesting your demographic information. Now that this is in place it’s one more thing we have to worry about when evaluating software. There is absolutely no reason to be storing PII in a centralized spot where anything and everything can request it. If I want an app to have any of that shit I’ll enter it on a case by case basis.

        You can say “well don’t put it in there” but what happens when big monopolistic corporations start requiring it to use some service of theirs that you don’t have an alternative for? Now I have to maintain a separate PC for that shit? Fuck that.

        • FauxLiving@lemmy.world
          1·
          2 hours ago

          You can say “well don’t put it in there” but what happens when big monopolistic corporations start requiring it to use some service of theirs that you don’t have an alternative for? Now I have to maintain a separate PC for that shit? Fuck that.

          If you choose to use a service that requires age verification then that service will store your age verification information on your computer somewhere. If it is stored in systemd, malicious programs will be able to access it. If it is not stored in systemd, malicious programs will still be able to access it.

          If you choose to not use a service that requires age verification, then you will not store any age verification information on your computer to be stolen by malicious software. Even if systemd has a birthDate field you will not store any age verification information.

          The difference in these two scenarios is your choice to use age verification or not. The location where the data is stored doesn’t change the scenario.