• atyaz@reddthat.com
    link
    fedilink
    arrow-up
    18
    arrow-down
    3
    ·
    1 year ago

    That’s fine but the point of the post is that you have to use a non chromium browser to avoid wei. Once it’s implemented it’s likely that edge and others will have to implement it too.

    • Draces@lemm.ee
      link
      fedilink
      arrow-up
      3
      arrow-down
      6
      ·
      1 year ago

      No you don’t. Chrome might implement wei but chromium is open source. There’s literally no way they could force every chromium browser to use it and the threat of drm web isn’t affected by using a non wei chromium browser or Firefox.

      • atyaz@reddthat.com
        link
        fedilink
        arrow-up
        12
        ·
        1 year ago

        It would be a monumental effort for smaller browsers to keep chromium extensions working, while the rest of the ecosystem moves to the new APIs. The only way that could work is if they all fork chromium and base their browsers on this new fork, and even then it’s not guaranteed to develop a real ecosystem of plugins since chrome has more users than all of those other chromium browsers combined.

        So yeah you have to use Firefox if you want to avoid that, at least for now.

        • Draces@lemm.ee
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          What does the implementation with extensions look like? It’s a required module that every extension needs to handle?

      • WhyJiffie@sh.itjust.works
        link
        fedilink
        arrow-up
        7
        ·
        1 year ago

        How is there no way? Yes, there is. Google implements it in the original, websites start requiring it, all of those browsers that didn’t implement it will be denied from access to websites. The end.