this post was submitted on 18 Aug 2023
-55 points (19.1% liked)
Privacy
31998 readers
959 users here now
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
- Don't promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
Chat rooms
-
[Matrix/Element]Dead
much thanks to @gary_host_laptop for the logo design :)
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The thing that sucks about that is the sheer amount of stuff that a modern web browser is expected to do.
Level 0:
Level 1:
Level 3:
Level 4:
Basically, writing a browser engine from scratch in a way that is in any way competitive is probably on par for scale on writing your own operating system. You might even accomplish the latter faster, depending on where you'd call your OS "complete"
Unfortunately, I can't argue with much of that. In fact, if anything, you're leaving out complexities.
There are a few browsers out there that use WebKit but none of Chromium. (Surf and Uzbl are a couple that I've used in the past.) With a little scripting, you could get them to, for instance, run two different "profiles" with different cookie stores at the same time. But they're far from full-featured.
Maybe what we really need is to scrap the web and start fresh with something better.
Level 5: Handle cookies, a local key value store, and a local database internally in a secure way.
Level 6: If you can't watch Netflix on your browser it's probably a non-starter for some users so better figure out a way to include DRM compatibility. But if you do it, the privacy minded will get really upset, so ideally you'd figure out a way to do it in some way that can be easily turned off or removed.
Level 7: alright, so implementing all of that was hard. But if you don't implement it in such an insanely optimized fashion that you can win arbitrary script tests that are meant to strain modern CPUs, the audience most likely to use your browser (geeks) will immediately move to something else and say your browser sucks. Get optimizing.