I've been holding off on writing my own browser, but I suppose it is time.
I mean, why not have 20 different projects in various stages of completion, instead of finishing one at a time?
"They all work together" I say to myself.
# sovereign_browser
A Linux x86 web browser built in C99 on WebKitGTK, designed around **sovereign identity** instead of the traditional web's permissioned infrastructure.
The thesis: the browser's security model (DNS/domains, TLS/CAs, same-origin policy, CORS, cookie sandboxing) is what forces you to rely on permissioned domains, certificate authorities, and centralized account systems. By deprecating that model and replacing it with **Nostr identity** and **FIPS
mesh transport**, you get a browser that's more capable, not less safe — because trust moves to the layer where it belongs: your keys.
I mean, why not have 20 different projects in various stages of completion, instead of finishing one at a time?
"They all work together" I say to myself.
# sovereign_browser
A Linux x86 web browser built in C99 on WebKitGTK, designed around **sovereign identity** instead of the traditional web's permissioned infrastructure.
The thesis: the browser's security model (DNS/domains, TLS/CAs, same-origin policy, CORS, cookie sandboxing) is what forces you to rely on permissioned domains, certificate authorities, and centralized account systems. By deprecating that model and replacing it with **Nostr identity** and **FIPS
mesh transport**, you get a browser that's more capable, not less safe — because trust moves to the layer where it belongs: your keys.
1