zlacker

[return to "Web Environment Integrity API Proposal"]
1. caesil+29[view] [source] 2023-07-21 18:49:55
>>reacto+(OP)
Whether you like it or not (and I certainly don't), you've gotta sort of admire the sheer vision of a fifteen-year project to build a browser so good it comes to monopolize the industry, all because you've had the foresight to realize that monopoly will be crucial to securing your position as the adtech hegemon. An underrated masterpiece of evil genius.
◧◩
2. kibwen+nh[view] [source] 2023-07-21 19:28:26
>>caesil+29
And tech people fell for it hook, line, and sinker.

It's completely and utterly irrelevant that Chromium is open source, because the web is a protocol, and having the source for an implementation of the protocol doesn't matter in the least when you don't control the protocol. You can't just fork Chromium and remove a feature, because websites expect the feature, and your browser won't work on them. You can't just fork Chromium and add a feature, because websites don't care about your tiny fork and won't use your feature. You can't fork Chromium, you have to fork the entire web.

◧◩◪
3. chrisc+6X[view] [source] 2023-07-21 22:44:48
>>kibwen+nh
> You can't just fork Chromium and add a feature

Of course you can. Microsoft's Edge and Brave already add proprietary features like AI and reader mode, tab groups, video calling, crypto wallet etc.

Brave could add a custom CSS or HTML feature. Hell that was the status quo we came from ten years ago when each vendor had their own feature flags and implementation for WebRTC and proprietary video codecs, etc.

Brave already explicitly removes ads and blocks all kinds of things websites expect to work on Chrome.

[go to top]