Any plans for a browser extension? It would be perfect if, e.g. Brave browser, embed this functionality into the browser itself. Brave is pioneering several initiatives like that (decentralized web).
We have great ideas for a browser extension, but we need to finish other work first. Maybe @Alby can cover some things? 😃
Hmmmm 💡 ! @devsou.com how would you see the feature in browser extension? @bitcoinerrorlog wanna drop us some of your ideas?
Not sure what browsers allow, but, for example, you could manage auth/sessions for homeservers, you could offer to server Pubky profile/web pages that render from keys, you could integrate pkdns and serve dns for keys, allow people to render web pages from key domains, parse key domains into nicknames on the page and/or browser bar, etc etc :)
I just wish it were possible to access a website using the public key as the address, serving files directly from your home server.
You could do this by running pkdns locally, then pointing your browser DNS to it.
I think a browser extension could simplify this process. That's the point.
You are the experts, but if Alby can do what brave does for IPFS urls, I.e intercept urls that have Pkarr as TLDs, and route the cleaner endpoint while keeping the address bar showing the original URL, that would defined be fun. we can ship Rust or wasm code that takes pubky or pkarr url and give you back either a normal domain or an ip and port. in fact if you can Rust code in extensions, then we can do TLS too that doesn't depend on CAs. but I don't know enough about extensions limitations.
I think you overestimate what extensions actually can do currently. Seems brave removed IPFS support and now there are some attempts to make such scenarios work through extensions (instead of directly in the browser). Seems like quite some way to go still: https://github.com/ipfs/ipfs-companion/issues/164 WASM should be fine 👌