Comment

Comment by cookiengineer

My side project kind of escalated quickly into a main project. I've been working on my own browser for the last couple months, and decided that I can improve a lot when it comes to using the web for automating and acquiring knowledge (i.e. the semantic aspect of it).

Currently on the verge of founding a (possibly viable) startup with it, but the browser itself is totally alpha for now.

Been working on parsers and protocols for a while now, and had to switch to TDD to keep my sanity together. Needed to write my own test runner that can simulate network behaviours (2G slow fragmentation is real) and peer to peer scenarios. Most servers out there don't comply with specifications, so making my own client- or peer-side implementations work was a hard task.

Currently writing my own SGML parser and optimizer, so that the browser receives only "linted and upgraded" html that is free of malicious parts, whilst embracing the idea of disallowing everything that could be potentially misused, including CDNs that do cache busting all the time.

The idea behind the browser concept is that trust is not established by default, and users should decide what website to trust, and match that with what kind of content they'd expect the website to deliver.

[1] https://github.com/cookiengineer/stealth

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton