3 ms·
This hashlink spec seems to duplicate the existing Named Information (ni:) URI scheme (RFC6920), as well as widely deployed non-standard solutions, namely magne
by zozbot234 4y ago
This hashlink spec seems to duplicate the existing Named Information (ni:) URI scheme (RFC6920), as well as widely deployed non-standard solutions, namely magnet: URI's. These don't seem to currently support the Multihash format that's recommended here, but could easily be extended/amended to that effect. Not seeing the point of this.
- westurner 4y agoNeither RFC6920 nor magnet: URIs appear to support the "just add a url parameter with the hash to the existing URL" use case, FWICS. CAS Content-addressable storage: https://en.wikipedia.org/wiki/Content-addressable_storage#Open-source https://en.wikipedia.org/wiki/Content-addressable_storage#Op... : IPFS <CID>/path RFC6920: https://www.rfc-editor.org/rfc/rfc6920.html https://www.rfc-editor.org/rfc/rfc6920.html Magnet URI scheme: https://en.wikipedia.org/wiki/Magnet_URI_scheme https://en.wikipedia.org/wiki/Magnet_URI_scheme draft-sporny-hashlink-07 2021: https://datatracker.ietf.org/doc/html/draft-sporny-hashlink-07 https://datatracker.ietf.org/doc/html/draft-sporny-hashlink-... : <url>?hl=<resource-hash>
- layer8 4y agoThe URL-parameter method is application-specific though, not sure it’s very useful to have a standard for that. Applications can just use whatever parameter name makes sense for them plus an existing hash/CAS encoding for the value.
- westurner 4y agoHow else can browsers check the hash of a file downloaded over HTTPS?
- layer8 4y agoThe main focus of the draft RFC is to define a new "hl" hashlink URL scheme. This doesn't necessariy target browsers, though they could certainly choose to support that scheme. The URL-parameter encoding, which is not the recommended encoding, is merely for "existing applications utilizing historical URL schemes", which may or may notinclude browsers. The draft explicitly states: "Implementers should take note that the URL parameter-based encoding mechanism is application specific and SHOULD NOT be used unless the URL resolver for the application cannot be upgraded to support the RECOMMENDED encoding."
- westurner 4y agoWhat is the likelihood that all existing resolvers will be updated to support schemes in addition to HTTP:// and HTTPS:// instead of happening to support a less-than-uniquely-named URL parameter?