• verdare [he/him]@beehaw.org
    link
    fedilink
    arrow-up
    54
    ·
    1 year ago

    I think signed hardware components are actually a good thing. The problem is that Apple makes it so that unapproved hardware doesn’t work at all. I think the device should warn the user, but allow them to override and continue at their own risk.

    Of course, Apple isn’t going to allow that unless they’re forced to. Glances sideways at the EU.

    • LoamImprovement@beehaw.org
      link
      fedilink
      arrow-up
      9
      ·
      1 year ago

      Makes me wish Google hadn’t canned phonebloks. Can you imagine how much waste we could have cut down on if we decided to standardize every component like the usb-c port?

      • Appoxo@lemmy.dbzer0.com
        link
        fedilink
        arrow-up
        3
        ·
        1 year ago

        I think we would need something like a Framework.
        Project Ara had no future if all modules need a case for protection AND the components.

    • deegeese@sopuli.xyz
      link
      fedilink
      arrow-up
      6
      ·
      1 year ago

      Sounds good, but how do you stop an unscrupulous repair shop from clearing the warning before the end user can see it?

      If it is persistent but buried in settings, most people won’t notice.

      • TheOakTree@beehaw.org
        link
        fedilink
        arrow-up
        3
        ·
        edit-2
        1 year ago

        Maybe the warning could require Apple sign-in to dismiss, but can be hidden at startup? Then make it an industry standard to present the phone when it is powered off.

        EDIT: Yes, I know that this is still shitty for most customers.