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?

Follow

@ajroach42 I'd build a web without imperative clientside code.

Everything would be declarative!

And everything that sent an HTTP request to a non-origin location would be behind a permission dialog:
* Always allow [domain]
* Always allow [domain] from [origin]
* Allow [domain] from [origin] this session
(+ disallow variants of the above options)

@zatnosk @ajroach42 I think dialogs as a whole fail to prevent sites from doing bad things. I've seen too many sites that say We are unable to show you our content because you have #JavaScript turned off and users then allow whatever the site and its third party partners want to do.
.
I'd make the client default to being unable to perform most tasks involving 3rd parties.
Sign in to participate in the conversation
Manowar.social

Private mastodon server run by Zatnosk