patrick.net

Patrick, I assume one must know the ip of the server to ssh/scp to? Basically that's probably distributed with the user's public key? Why scp instead of ssh tunnels?

Have you considered using regular https in browsers, but just use self signed certs? Putting the user's cert in your local trust store basically makes it a root cert. Since a self signed cert has no upstream certs, there's no one to revoke it.

A benefit of this way would be better/easier compatibility. Adding a base dir to urls like
http://localhost/(hash of content author public key)/
likely requires complicated proxy code that scans html, js, cookies, headers etc... to rewrite paths. It can be done, and I know existing proxy server projects do it, but the js part is the place where I imagine they never quite get perfect compatibility. Same goes for changing the domain and/or port by using localhost, you'll need to rewrite content. Well, unless the site author does a perfect job of using relative paths.

I guess a drawback is that when using certs, angry npcs at google could possibly alter chrome to block certain certs "known for disseminating hate speech", whereas your method would require they modify scp to block a public key. Because with your method, the browser is just connecting to a local webserver, w/ no easy way for them to id the source of the content.

Maybe instead of using a base url, make domains via the host file, which all just point to 127.0.0.1. By having a dedicated domain that points to the local web server (like http://correct.horse.battery.stapler ), the browser cross domain security model will remain in tact, whereas using a base url, you will have issues with websites reading each others data, because you cannot guarantee isolation.

AmericanKulak says

White people have cut soda consumption 20% in the past two decades, but minorities have not. Therefore, all commercials for soda feature Twerking.

https://twitter.com/crazyclipsonly/status/1722826385691975947

A female gorilla trying to seduce her mate