Things a good browser should block:
- scroll-based "signup" dialogs (e.g., for newsletters)
- more than 500KB of JS w/o a user interaction
- any JS served w/o compression or content-length headers
- images that are likely more than 3x the viewport size
- cookie consent dialogs
@slightlyoff Right, but the problem is that 98% of users will then think "this browser broke this web site" instead of "this web site is breaking the web". How do we fix that?
@LouisIngenthron URL-bar UI that indicates the page was interdicted, and that you can tap that button to reload without interventions.
@slightlyoff I'm a NoScript user, so you're preaching to the choir, but I don't think regular users would like that.
They still get pissed off when a browser tries to protect them from a bad SSL cert.
@LouisIngenthron The plural of andecdote is not data. "Broken lock" (and similar) warnings were critical in getting most of the web's traffic encrypted. Turns out that developers respond to incentives.
@slightlyoff @LouisIngenthron Maybe instead of a URL-bar warning, which makes the user think the browser is shit, browsers should just intentionally add 5 seconds of latency to every offending request. That way users will still think it's the site that is shit haha
@Jespertheend @slightlyoff Yesss, I like this. 5 seconds for every MB of text/script content past the first MB. Make oversized images load like a JPEG on dial-up. If a scroll-based signup dialog appears, make scrolling stuttery AF for a few seconds.
