3 ms·
> “With HTTP, you search for locations. With IPFS, you search for content.” Well, that's the difference between an URL and an URI, right? HTTP seems URL-orient
by enz 5y ago
> “With HTTP, you search for locations. With IPFS, you search for content.”
Well, that's the difference between an URL and an URI, right? HTTP seems URL-oriented while IPFS seems URI-oriented.
- capableweb 5y agoNot quite. A URI is any identifier, a URL is a identifier to a location while a URN is identifier only containing a name. IPFS hashes are URIs/URNs while both URLs and URNs are URIs.
- jrochkind1 5y agoAdditionally, what the "for content" statement is trying to get across is that there is necessarily only one IPFS address possible for a given unique piece of binary content. Which is a quality not universal among URNs either.
- enz 5y agoOh, I see. Thanks for the clarification!
- nivertech 5y agoURL - Uniform Resource Locator URN - Uniform Resource Name URI - Uniform Resource Identifier URI is too generic, "I" in URI means "Identifier", which can be either a semantic/natural or a technical/surrogate key. And in many case it's the same Locator is in URL. IPFS is a CAS (Content Addressable Storage), so an "Identifier" there is a semantic key (i.e. hash of the content).