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

IPFS Addressing in Web Browsers, ipns://, and DNSLink #118

Open
Tracked by #248
da2x opened this issue Oct 1, 2018 · 1 comment
Open
Tracked by #248

IPFS Addressing in Web Browsers, ipns://, and DNSLink #118

da2x opened this issue Oct 1, 2018 · 1 comment
Labels
status/ready Ready to be worked topic/origin Issues related to Origin-based security

Comments

@da2x
Copy link

da2x commented Oct 1, 2018

ADDRESSING.md doesn’t address the use of DNSLink in URIs. E.g. ipns://<domain>/ or dweb://ipns/<domain>/.
@lidel lidel added the status/ready Ready to be worked label Oct 3, 2018
@lidel
Copy link
Member

lidel commented Oct 18, 2018 •
edited
Loading

Yes, it was on purpose.

IPNS identifier in authority component was omitted mostly due to ipfs/kubo#5287
We want to close that first and then provide coherent addressing guidelines for entire IPNS.

@lidel lidel added the topic/origin Issues related to Origin-based security label Nov 15, 2018
@lidel lidel mentioned this issue Apr 1, 2020
Open
14 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
status/ready Ready to be worked topic/origin Issues related to Origin-based security
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lidel @da2x