ipfs
feat: support ipns/<name> & dnsLink resolution
We should enable users to explore paths like:
-
/ipns/docs.ipfs.tech -
/ipns/k51... -
foobar.host.com- with DNSLink TXT entry
When typing things like /ipns/k51..., /ipns/ipfs.io into the browse/inspect bar if you hit inspect it'll take you to the explore page and will error.
There are a variety of errors depending on the mutable identifier type:
-
/ipns/k51...-> Error: No resolver found for codec "libp2p-key" -
/ipns/12D3...-> HTTPError: invalid path "12D3K...": selected encoding not supported -
/ipns/Qm...-> Seems to hang/break things (but could be mistaken) -
/ipns/ipfs.io-> Error: invalid character '.' in 'ipfs.io'
Related
- https://github.com/ipfs/ipfs-webui/issues/1884
- https://github.com/ipfs/ipfs-webui/issues/1076
- https://github.com/ipfs/ipfs-desktop/issues/2649
After https://github.com/ipfs/ipld-explorer-components/pull/406, this work becomes trivial: just use https://github.com/ipfs/helia-ipns
After #406, this work becomes trivial: just use https://github.com/ipfs/helia-ipns
I've needed to install helia for a while anyway, some back reference for you, in case it's relevent:
I've reproduced this error after a "doh" deploy, just trying to see if something would work here. I was deploying a page that exist on https that contains encoded background icons. Luckily it initially got flagged as malicious because I should of been including a third party that handles password management there. :-D
There's a translation that needs to occur on the client side in the page to process a handshake. And in my case the third party offers this as a service, but I'm working on developing it. You never know when spare info will come in handy, figured I'd drop this in this grave over here. lol.
