[wei] Ensure Origin Trial enables full feature · chromium/chromium@6f47a22
github.com
This CL moves the base::Feature from content_features.h to a generated feature from runtime_enabled_features.json5. This means that the base::Feature can be default-enabled while the web API is co...
  • Gibberish9031@lemmy.ml
    1·
    1 year ago

    Time to De-Google I guess. I will keep using Firefox and if or when I come across any website pulling this crap I won’t hesitate to blast them to eternity. I suggest everyone else do the same please.

        • 133arc585@lemmy.ml
          0·
          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.

        • InFerNo@lemmy.ml
          0·
          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
            0·
            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.

          • Litany@kbin.social
            0·
            1 year ago

            Digital Rights Management. Usually DRM agreements are imbedded in the terms and conditions no one reads when they install software. It usually gives the software vendor the right to monitor your use of the software in real time via the internet.

            Within the context of Chrome and other Chromium based web browsers, this means that Google will be able to monitor your web browsing in a new way any time you’re using a browser based on Chrome/Chromium.

            • 133arc585@lemmy.ml
              0·
              1 year ago

              Within the context of Chrome and other Chromium based web browsers, this means that Google will be able to monitor your web browsing in a new way any time you’re using a browser based on Chrome/Chromium.

              With only slight hyperbole, we can say that Google can do this monitoring already.

              What’s worse, is now they can:

              • Refuse you access to information by refusing to attest your environment.
              • Restrict your browser, extensions, and operating system setup by refusing attestation.
              • Potentially bring litigation against you for attempting to circumvent DRM (in the USA it’s illegal to bypass DRM).
              • Leverage their ad network to require web site operators to use attestation if they wish to serve ads via Google. AKA force you to use Chrome to use big websites.
              • Derank search results for sites that are not using attestation.

              In my opinion, the least harmful part of this is the ability to monitor page access, because they can more or less do this for Chrome users anyway. What’s really harmful here is the potential to restrict access to and destroy practically the entirety of the internet.