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. anders+MC1[view] [source] 2023-07-22 05:27:16
>>kibwen+nh
> you have to fork the entire web

That's exactly what we need to do. More specifically, we need to decouple the app web from the document web. Most of the value of the web to society lies in text, images, and video, in that order. We need a version of the web refocused around basic content with a spec simple enough for a small team to implement a browser for. A subset of HTML/CSS is probably the only way to succeed, since sites would need to work with current browsers. I think a few HTML tags + flexbox + fonts + colors would get you pretty far.

◧◩◪◨
4. leshen+is3[view] [source] 2023-07-22 22:30:46
>>anders+MC1
honestly, I'd be fine with just markdown with some extensions (e.g. images and footnotes, not sure if they're part of the standard)
[go to top]