• Cethin@lemmy.zip
    link
    fedilink
    English
    arrow-up
    6
    ·
    edit-2
    1 hour ago

    The issue isn’t resolved because this doesn’t actually do anything. It’s an issue because it’s a ratchet. If we let it proceed, there’s almost no way for us to go back.

    • Luminous5481 "Enemy of the State"@anarchist.nexus
      link
      fedilink
      English
      arrow-up
      3
      ·
      14 hours ago

      It’s open source software with a full commit history, you can literally always go back and it’s impossible to prevent you from having that ability. The whole point of Linux is it can be whatever you want, there’s literally zero way that any government could realistically control Linux, nor any way to implement a practical system to enforce age verification when anybody can bypass it in their install at any time.

      Nobody can convince me that in a world were governments can’t even stop non-anonymous piracy that they’re going to be in any way effective at controlling an operating system primarily used by technically savvy people, which is primarily distributed by P2P software most used for piracy.

      • Cethin@lemmy.zip
        link
        fedilink
        English
        arrow-up
        0
        ·
        12 hours ago

        That’s not what I meant. I meant, once it becomes normal for projects to accept this as standard, more will use/require it. Maybe not the systemd version specifically, but the general concept. Sure, you can always fork it and create a version free from it, but eventually it’ll be too much for any individual to want to deal with and the standards will shift. There will probably always be a distro that doesn’t have any of it, but it’ll become increasingly isolated and incompatible.