• FishFace@piefed.social
    link
    fedilink
    English
    arrow-up
    3
    ·
    7 hours ago

    Cool.

    And what, exactly, is the path from “pushing back on zsh” to “embedded device manufacturers can no longer lock down their devices?”

    • Shrubbery@piefed.social
      link
      fedilink
      English
      arrow-up
      3
      ·
      6 hours ago

      A plausible path is precedent and normalization, not zsh specifically.

      If a widely used copyleft component (like a shell) starts being accepted as “OK to lock down” in consumer or embedded devices, manufacturers and courts get comfortable with the idea that user-modifiable software is optional rather than a right tied to distribution. Over time, that erodes enforcement of anti-tivoization principles and weakens the practical force of copyleft licenses across the stack.

      Once that norm shifts, vendors can apply the same logic to kernels, drivers, bootloaders, and userland as a whole—at which point locked-down embedded devices stop being the exception and become the default, even when the software is nominally open source.

      • FishFace@piefed.social
        link
        fedilink
        English
        arrow-up
        1
        ·
        4 hours ago

        I don’t understand. It’s already ok to “lock down” devices, from the point of view of most consumers and the courts, regardless of the software license. Phones make it hard for you to flash new firmware onto them. That is still true with android and the open source components in its stack.

        Using bsd licensed software in every day life cannot accelerate that because it has already happened, and I don’t see how it would be otherwise, because software licensing doesn’t protect against the kind of locking down you’re talking about.