Federated Republic of Sean is a user on retro.social. You can follow them or interact with them if you have an account anywhere in the fediverse.

So web browsers are bad, right?

And web browsers being bad is making the internet bad, right?

Or maybe the internet being bad is making web browser bad.

Doesn't matter.

The upshot is that we should stop using bad web browsers recreationally, and stop using services that can only be accessed from bad web browsers.

And when that isn't possible, build alternatives that work from not bad browsers.

That's why I'm so happy that Brutaldon exists.

So, what are the core features a good web browser should have?

What shouldn't it have?

If you were redesigning the web, today, knowing what you know about popups, cookies, malicious javascript, etc. What would you design?

@ajroach42 I guess the question is, how would you *split up* the web, so that applications that really do need the abused functionality went off into their own space (perhaps with its own protocol), while the pieces we like would stay in their own space in which annoyances are relatively difficult to implement.

Federated Republic of Sean @freakazoid

@ajroach42 No JS. No transclusion of third-party content. Cookies, but no third-party cookies (which are meaningless without third-party content anyway). Little to no control over layout by the author, with all formatting being based on semantics. Images can be embedded, but they need to be literally embedded in the document.

· Web · 5 · 1



I agree with all of that aside from the formatting. Users should have a *choice* to override formatting but I don't think it should be removed completely.

Support should exist for viewing all content in a variety of ways, but don't throw out the baby with the bathwater.