Live data from Hacker News

Google is already pushing WEI into Chromium

github.com

621–630 of 876 posts

Re: Google is already pushing WEI into Chromium

#621
post #186

It's small, but here's a real actionable item that you can do to help: Put a gentle "Use Firefox" (or any other non-Chromium-based browser) message on your website. It doesn't have to be in-your-face, just something small. I've taken my own advice and added it to my own website: https://geeklaunch.io/ (It only appears on Chromium-based browsers.) We can slowly turn the tide, little by little.

The issue with that is that most people here will only have their own website or product, which is already aimed at more tech-savvy people, who will already have made a conscious decision to use Firefox, Chrome, or whichever browser they prefer. But we / this site only represents a small percentage. 85% market share means there are hundreds of millions, if not billions of users that would have to switch to make any k…

Most web developers don't use Firefox. Changing that would be a huge step. Many things are developed for Chrome first by inertia at this point.

Re: Google is already pushing WEI into Chromium

#622
post #576

Don't just comment and complain, contact your antitrust authority today: US: - https://www.ftc.gov/enforcement/report-antitrust-violation - antitrust@ftc.gov EU: - https://competition-policy.ec.europa.eu/antitrust/contact_en - comp-greffe-antitrust@ec.europa.eu UK: - https://www.gov.uk/guidance/tell-the-cma-about-a-competition... - general.enquiries@cma.gov.uk India: - https://www.cci.gov.in/antitrust/ - https://www.…

I admire your optimism. Don't know about the others, but I'll be surprised if UK one would lift a finger. They are beyond useless.

Re: Google is already pushing WEI into Chromium

#623

As someone who is a somewhat new to web technologies, can someone really explain why this is bad? I saw the techical discussions in the PRs made to the WEI repo but it was all super technical that I was not able to understand the arguments made for and against it.

WEI turns non-compliant browsers into second-class citizens. You’re perfectly free to use whatever compliant browser engine and OS combo you like today – but in a world with WEI, you’ll have to use Approved Chrome on an Approved OS on Approved Hardware with Approved Signing Keys, or you won’t be able to sign into your bank.

Is there any way around this, like spoofing headers or OS specs?

Re: Google is already pushing WEI into Chromium

#624

I've been holding on to my Firefox installation after switching back around ~2016 or so. I was on the Chrome bandwagon when they were the upstart (still have the comic from the launch!) but it didn't take long to see how dangerous things were getting with monoculture. If you want to help, push back on all the anti-Firefox rhetoric that amplifies every little misstep that they take. Firefox is so much better from a us…

Maybe they shouldn't have added the Pocket links if they didn't want the vitriol. Tracking or not (I'm still not 100% convinced that they're not), it doesn't look good when your browser greets you with that stuff. It's like entering a neighborhood and seeing a "checks cashed" store.

Re: Google is already pushing WEI into Chromium

#625
post #419

Mozilla should call for Google's removal from the W3C over this implementation of Web Environment Integrity. "But Chrome has 65% market share, what good is the W3C without them?” If Google can take unilateral action to fundamentally change the basic principles of the web, then the W3C is already useless. This will give Google a clear choice: if they want to maintain the idea that the W3C matters, they should withdraw…

It didn't happen when Apple did it with Safari (and you all were quiet as a mouse as well, with HN actively defending Apple Safari monopoly with this feature enabled)... so why would NOW be any different?

I think the main difference is that Apple already controlled what operating systems can run Safari via other mediums. Adding this to Safari effectively changes nothing regarding the web ecosystem on Apple devices.

Re: Google is already pushing WEI into Chromium

#626
post #186

It's small, but here's a real actionable item that you can do to help: Put a gentle "Use Firefox" (or any other non-Chromium-based browser) message on your website. It doesn't have to be in-your-face, just something small. I've taken my own advice and added it to my own website: https://geeklaunch.io/ (It only appears on Chromium-based browsers.) We can slowly turn the tide, little by little.

I don't think most people know the difference between Chrome or Firefox and if they can still use websites they use with that change, they just won't bother.

Even if you explain what is the difference, 99% they'll forget the next day.

It's just pointless. With this kind of overreach, only government intervention and regulation can help. Google is not something you can go against with your proverbial wallet - they are too big.

Re: Google is already pushing WEI into Chromium

#627
post #576

Don't just comment and complain, contact your antitrust authority today: US: - https://www.ftc.gov/enforcement/report-antitrust-violation - antitrust@ftc.gov EU: - https://competition-policy.ec.europa.eu/antitrust/contact_en - comp-greffe-antitrust@ec.europa.eu UK: - https://www.gov.uk/guidance/tell-the-cma-about-a-competition... - general.enquiries@cma.gov.uk India: - https://www.cci.gov.in/antitrust/ - https://www.…

A customizable form letter would be nice to have, if anyone wants to jump on that. I'm not a great writer in that respect.

This is what I sent, feel free to use and customize:

    I would like to bring your attention to Google’s recent proposal to add a feature to its Chrome (Chromium family) of browsers called Web Environment Integrity. This provides a mechanism to reinforce Google’s already dominant browser market position by creating a technological control that can be used to nullify a user’s choice of browser, device and operating system. This technology also has the potential for abuse by preventing users from using browser extensions that can enhance security by blocking unwanted and potentially malicious content, as well as browser extensions that help vulnerable users with enhanced accessibility needs, such as color blindness and visual impairment.

    Google’s dominant, near-monopoly position in the browser market already harms me as a consumer by reducing browser choices and preventing a competitive market for developing new browsers. Allowing Google to include this feature will reduce my browser choices and consolidate the browser market even further, and it is incumbent on [INSERT AUTHORITY HERE] to take action against this abusive behavior.

Re: Google is already pushing WEI into Chromium

#628
Is anyone else working on alternatives to this web? We're going to want something working before this one becomes a telescreen.

I'm thinking:

- content addressing, not server addressing (to better distribute the hosting load)

- looser coupling between data itself and apps for viewing data (to prevent aesthetics from being used as a heuristic for trustworthiness)

- a native permissionless annotation protocol (p2p trust governs whether annotations appear: if you see an ad, just revoke trust in its author)

- no code execution needed for browsing, fancy features (i.e. the kind of thing you actually need js for) stay optional

I'm curious what design goals other people think are relevant.

Re: Google is already pushing WEI into Chromium

#629

Not a lawyer but this seems ripe for antitrust action. Microsoft got sued back in the 2000's for simply bundling IE with their operating system. The behavior of Google (and quite frankly Microsoft with Edge) seems way way worse than whatever MS was doing when they got sued.

But MS still bundles IE, and they've gotten more pushy about it lately.

Re: Google is already pushing WEI into Chromium

#630
post #503

Earlier quoted context omitted.

To put it simple, it makes it possible for service provider to reject providing service to clients not running corporate-owned white-listed clients. Thus making it virtually impossible to create independent clients for such services. It will be swiftly adopted by well meaning but clueless bank and government clerks who will accidentally use to lock all open hardware, open operating system, open browser users out and…

Isn't this already the reality in the mobile space? I own a rooted Samsung device and have to jump through 100 hoops to be able to use my banking app or Netflix or some rando game (which I don't actually play). SafetyNet broken, hardware fuse blown, Magisk Hide + some other havks just to still be able to do online banking. I just want to be able to ssh into my own device or install a real ad blocker, like Adaway with…

Yes, exactly correct. WEI is a way to turn this mobile device signing nightmare into a web standard that can be enforced across all devices.
Post reply on HN