- YouTube
www.youtube.com
Enjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube.

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.

  • ken@discuss.tchncs.de
    14·
    1 day ago

    You missed this option:

    • Ignore the feature and don’t use it.

    systemd is quite modular. For example, if you abhor systemd-resolved (not at unreasonable stance) it’s NBD to disable it.

    Recently (<1 year?) I frequently see the notion that software is “tainted” by having been touched by Bad. I find this a bit silly. Especially if it’s from a user who’s not even spending time in the codebase.

    • micvil@beehaw.org
      5·
      1 day ago

      If the law creates this new API, nobody will be able to get away without leaking PII to the web (I think it will have a javascript API). 1970 jan 1 identifies *nix users, 1900 jan 1, even an “unset” will leak info on people, etc. entropy and shit. Websites will also try to use the API. One could set the function to crash JS, or disable all JS, but that already breaks 90% of the web. One could also: either not install userdb (like I do), or install a non-systemd linux, but those still will leak “unset” or “API disabled”.

      There’s no getting away from this, it really is the law that we should push back against. Unfortunately it’s a fight currently only Americans and Brazilians can participate in properly. Donations won’t work well, govts these days often clamp down on NGOs because they often get money internationally, and therefore, they are “foreign interference” etc.

      • Kogasa@programming.dev
        2·
        17 hours ago

        “user is likely accessing service from a *nix device” isn’t PII. of course anything can be used for fingerprinting, but this type of “leak” is about as insignificant as it gets. It’s not what most people would consider a violation of their privacy.

        • micvil@beehaw.org
          2·
          14 hours ago

          I agree with most of what you said, however, I’m not worried about most people. I’m more worried about people who are trying to act against tracking. Maybe I shouldn’t, and we cannot “personal responsibility” our way out of this, but I still haven’t processed that loss.

          I’m also not worried about “user is likely accessing service from a *nix device” in itself. It’s hard to say how insignificant this particular bit is. I’ll prolly need to spoof this info, too.

          The systemd change is fairly insignificant, yes. That the xdg-desktop-portal people will implement this is more worrying. I’m also worried that the systemd addition will be used as “proof” that the linux landscape is perfectly capable of adding age attestation and verification, and therefore they will dismiss any possibly amendment to the US bills and the EU wouldn’t even consider adding an exception.