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?



Everything except for client-side scripting and stuff that is only useful with it, automatic loading of pictures or other embedded elements unless hosted on the same server as the page and the expectation that the client faithfully follows the style sheet.

ยท Amaroq ยท 2 ยท 2 ยท 1


The problem with the modern web browser is that it's become a software runtime. This is handy for writing lightweight(ish) clients and games but 95% of the web is just documents.

So every document is potentially a program without looking like one and a huge amount of effort goes into (semi-successfully) trying to keep those secret programs from harming us.

So I say cut the Gordian Knot: use a document reader when reading web pages and the app runner ONLY on websites you trust.

@suetanvil thatโ€™s the idea Iโ€™m considering here, yeah.

Sign in to participate in the conversation
Mastodon for Tech Folks

This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either! We adhere to an adapted version of the TootCat Code of Conduct and follow the Toot Cafรฉ list of blocked instances. Ash is the admin and is supported by Fuzzface, Brian!, and Daniel Glus as moderators. Hosting costs are largely covered by our generous supporters on Patreon โ€“ thanks for all the help!