You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The best and up-to-date source of truth about IPFS addressing right now is inADDRESSING.md memo.
As more and more people add IPFS support to their software, especially on the web,
we should decrease noise and increase signal around addressing by adding proper technical spec doc to the ipfs/specs repo, as suggested in #138.
Timeline
2022:
WIP gateway specs, compliance and consolidation work
2021: 💚 Brave supports ipfs:// an ipns:// out of the box (details)
Retrieval would be processed as "DNS look up domain.name IN TXT, resolve resulting IPFS/IPNS identifier, retrieve object".
I was reading this, hoping to find just that. IPFS wants to get away from hosting locations for reasons of persistency, but IPNS is different. I love the idea of using DNS (and DNSSEC) and getting very powerful bookmarks:
Stored domain name, for human reference where it once originated from
Stored IPNS key, so we can lookup the names from anyone who pins them, along with new versions from the same origin
Stored IPFS hash, so we can retrieve the version that we bookmarked for as long as it is pinned
I will add the spec to my reading list, it's useful stuff!
2022-03-01 discussion: we may add an issue for separating out the gateway tests that are in go-ipfs so have a "poor-mans" compliance test suite for gateway implementations.
The best and up-to-date source of truth about IPFS addressing right now is in ADDRESSING.md memo.
As more and more people add IPFS support to their software, especially on the web,
we should decrease noise and increase signal around addressing by adding proper technical spec doc to the ipfs/specs repo, as suggested in #138.
Timeline
ipfs://
anipns://
out of the box (details)ipfs://
andipns://
URIs being registered at IANA (details)TODO
ipfs/specs
(consolidate technical content from Prior Art)(https://github.com/ipfs/specs/blob/master/DWEB_ADDRESSING.md, reuse Background on Address Scheme discussions (dweb, ipfs:// and more) #152)
ipfs:
andipns:
URI schemes #138/ipns/
as well (IPNS: should work with case-insensitive identifiers (Base32) kubo#5287, IPFS Addressing in Web Browsers, ipns://, and DNSLink in-web-browsers#118)ADDRESSING.md
to point at the doc in ipfs/specsipfs:
andipns:
URI schemes #138cc ipfs/in-web-browsers#118 ipfs/in-web-browsers#3 ipfs/ipfs#227 ipfs/in-web-browsers#4 ipfs/in-web-browsers#28 #139 @autonome
The text was updated successfully, but these errors were encountered: