Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open
SgtPooki opened this issue Oct 11, 2023 · 1 comment
Open

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

SgtPooki opened this issue Oct 11, 2023 · 1 comment
Labels
effort/days Estimated to take multiple days, but less than a week exp/intermediate Prior experience is likely helpful good first issue Good issue for new contributors help wanted Seeking public contribution on this issue kind/enhancement A net-new feature or improvement to an existing feature P1 High: Likely tackled by core team if no one steps up status/ready Ready to be worked topic/interop Interoperability

Comments

@SgtPooki
Copy link
Member

SgtPooki commented Oct 11, 2023 •
edited
Loading

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
@SgtPooki SgtPooki added the need/triage Needs initial labeling and prioritization label Oct 11, 2023
This was referenced Oct 11, 2023
Closed
Closed
Closed
@SgtPooki SgtPooki added kind/enhancement A net-new feature or improvement to an existing feature help wanted Seeking public contribution on this issue good first issue Good issue for new contributors exp/intermediate Prior experience is likely helpful P1 High: Likely tackled by core team if no one steps up effort/days Estimated to take multiple days, but less than a week status/ready Ready to be worked topic/interop Interoperability and removed need/triage Needs initial labeling and prioritization labels Oct 11, 2023
@github-project-automation github-project-automation bot moved this to Needs Grooming in IPFS-GUI (PL EngRes) Oct 11, 2023
@SgtPooki SgtPooki moved this from Needs Grooming to Planned / Backlog in IPFS-GUI (PL EngRes) Oct 11, 2023
@SgtPooki
Copy link
Member Author

After #406, this work becomes trivial: just use https://github.com/ipfs/helia-ipns

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
effort/days Estimated to take multiple days, but less than a week exp/intermediate Prior experience is likely helpful good first issue Good issue for new contributors help wanted Seeking public contribution on this issue kind/enhancement A net-new feature or improvement to an existing feature P1 High: Likely tackled by core team if no one steps up status/ready Ready to be worked topic/interop Interoperability
Projects
No open projects
IPFS-GUI (PL EngRes)
Status: Planned / Backlog
Milestone
No milestone
Development

No branches or pull requests
1 participant
@SgtPooki