Skip to content

feat: support ipns/<name> & dnsLink resolution #400

Description

@SgtPooki

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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1High: Likely tackled by core team if no one steps upeffort/daysEstimated to take multiple days, but less than a weekexp/intermediatePrior experience is likely helpfulgood first issueGood issue for new contributorshelp wantedSeeking public contribution on this issuekind/enhancementA net-new feature or improvement to an existing featurestatus/readyReady to be workedtopic/interopInteroperability

    Type

    No type

    Projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions