Charlie McHenryFeb 3, 2024
Windows user? Microsoft is sure working hard to keep you from choosing your own browser. By putting MS Edge at the center of their OS, and using other design techniques, #Microsoft makes it hard to use other browsers. #Browsers #BrowserSuppression #AntiCompetitive https://research.mozilla.org/browser-competition/over-the-edge-the-use-of-design-tactics-to-undermine-browser-choice/
Over the Edge: The Use of Design Tactics to Undermine Browser Choice – Mozilla Research

In order to be able to choose their own browser, people must be free to download it, easily set it to default and to continue using it - all without ...

Mozilla Research
katzenbergerNov 5, 2023

The #BrowserSuppression (aka #WEI) "proposal" has been archived on github.

https://github.com/RupertBenWiser/Web-Environment-Integrity

But not in real life. As predicted, the approach is being resurrected. It's being taken to #Android, because … well, because, #Google.

Placation incoming: "narrowly scoped, and only targets WebViews embedded in apps". Diplomacy is the art of being able to say "nice doggie" until you have time to pick up a rock.

https://android-developers.googleblog.com/2023/11/increasing-trust-for-embedded-media.html

GitHub - RupertBenWiser/Web-Environment-Integrity

Contribute to RupertBenWiser/Web-Environment-Integrity development by creating an account on GitHub.

GitHub
katzenbergerOct 25, 2023

After #BrowserSuppression aka #WEI, #Google comes up with the next attack on #privacy, in #Chrome:

Redirect browsing through proxy servers - controlled by Google & friends. In the name of - privacy. Opening the door to man-in-the-middle attacks - by Google & friends.

https://github.com/GoogleChrome/ip-protection/issues/21

Cannot believe the chutzpah · Issue #21 · GoogleChrome/ip-protection

Google owns Chrome. So what's to prevent it from installing its own root certificate and MITMing all of your web browsing? Even if Google is able to restrain itself from acquiring all that juicy da...

GitHub
Show threadkatzenbergerAug 24, 2023

@thetechtutor

As for suggestions: new top-level protocols alone won't cut it. Leaving corporations and governments in control of standards has proven toxic (see recently: #EU attempts at #ChatControl; #Google attempting #BrowserSuppression aka #WEI).

We need a fresh start at decentralization and at putting effective & resilient control into the hands of people (not "users" or "customers"). On that, we can build.

The most promising starting point IMHO seems to be #Veilid.

(2/2)
@dev_m

Show threadkatzenbergerAug 8, 2023

@altpapier

Die drastischen Worte sind in diesem Fall mal angebracht. Wer mit etwas Softwareentwicklungs-Erfahrung sich den "Vorschlag" von Google anschaut (so kompliziert ist er nicht), erkennt sofort, was sich damit anstellen lässt und wie Googles Mär von "Antibetrugsfunktionen" u.ä. diese Funktionalität verschleiert.

Nicht umsonst gaben knapp 550 Entwickler auf einer Entwicklungsplattform ein 👍 für den Kommentar "Don't".

https://github.com/RupertBenWiser/Web-Environment-Integrity/issues/28

#BrowserSuppression #WebDRM

@digitalcourage

Don't. · Issue #28 · RupertBenWiser/Web-Environment-Integrity

Sometimes you have to ask the question whether something should be done at all, and trusted computing is certainly one of those cases where the answer is obviously a big fat NO. So please reconside...

GitHub
katzenbergerJul 27, 2023

Added this to my main website (displayed for visitors using #chromium-derived browsers):

"You are using Chrome, Chromium, or a browser derived from that. These browsers will soon support websites (via #WEI) with suppressing alternative browsers.Please consider switching to a browser that does not support this, e.g. #Firefox"

#BrowserSuppression

katzenbergerJul 26, 2023

As @jan and @ck have rightfully pointed out, implementation of #BrowserSuppression (aka (#WebEnvironmentIntegrity") continues.

If you are a developer and have understood what this is leading to, you may wish to comment on the this commit on github:

https://github.com/chromium/chromium/commit/6f47a22906b2899412e79a2727355efa9cc8f5bd

[wei] Ensure Origin Trial enables full feature · chromium/chromium@6f47a22

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...

GitHub
katzenbergerJul 25, 2023

@mozilla said "No" to #Google's attempt at #BrowserSuppression ("#WebIntegrityEnvironment"):

"#Mozilla opposes this proposal because it contradicts our principles and vision for the Web."

https://github.com/mozilla/standards-positions/issues/852

Quoting their vision:

"Standards themselves aim to avoid assumptions about the underlying hardware or software that might restrict where they can be deployed. This means that no single party decides which form-factors, devices, operating systems, and browsers may access the Web."

Request for Position: Web Environment Integrity API · Issue #852 · mozilla/standards-positions

Request for Mozilla Position on an Emerging Web Specification Specification Title: Web Environment Integrity API Specification or proposal URL (if available): https://rupertbenwiser.github.io/Web-E...

GitHub