• InFerNo@lemmy.ml
        link
        fedilink
        arrow-up
        0
        arrow-down
        1
        ·
        1 year ago

        A fork like Vivaldi, Brave or Opera could opt not to implement these changes, but then some websites could become incompatible to them.

        • 133arc585@lemmy.ml
          link
          fedilink
          arrow-up
          1
          arrow-down
          1
          ·
          edit-2
          1 year ago

          A fork like Vivaldi, Brave or Opera could opt not to implement these changes

          It doesn’t quite work like that. They wouldn’t choose to not implement the change, because the change comes from upstream via Chromium. They would have to choose to remove the feature which, depending on how it’s integrated, could be just as much work as implementing it (or more, if Google wants to be difficult on purpose). Not implementing the change is zero effort; removing the upstream code is a lot of effort.

      • 133arc585@lemmy.ml
        link
        fedilink
        arrow-up
        0
        arrow-down
        1
        ·
        1 year ago

        It depends on how Google wants to play this. If they require website operators to use WEI in order to serve ads from Google’s ad network (a real possibility), then suddenly 98.8% of websites that have advertising, and 49.5% of all websites would be unusable unless you’re using Chrome. It’s probably safe to assume they’d also apply this to their own products, which means YouTube, Gmail, Drive/Docs, all of which have large userbases. The spec allows denying attestation if they don’t like your browser, but also if they don’t like your OS. They could effectively disallow LineageOS and all Android derivatives, not just browser alternatives.