> It won't work "unilaterally" for obvious reasons but there are lots of p2p, e2e, security and crypto type apps where creators would love to be able to reduce the degree to which infra like CDNs and hosting need to be trusted.
If we are moving out of the http/web space into some sort of distributed protocol, just use magnet links, problem solved. Or some equivalant hash based content-addresable scheme. (How applicable depends on what space we are talking about)
I agree but now you are asking your users to either install an extension or download something.
What many people want is the convenience of http/web with the immutability of content addressing and the frustration of OP at the start of our thread is that SRI feels so close to being able to provide that but stops short.
This has been a really interesting discussion for me because I think you understand the use cases and alternatives but it seems like you don't agree that hash pinned / immutable web sites natively in the browser would enable many interesting use cases.
I think i don't like it if its implemented as metadata stored separately from the url. As a separate url scheme where the url scheme includes both the hash and the document location, i think it would be cool. Really that essentially comes down to supporting magnet links with the webseed (ws) parameter in browser. Which would be really cool.
Actually, a browser COULD implement subresource integrity for bookmarked urls - it would just require another field in the bookmark metadata. They could arrange for 'rightclick, save as bookmark' to pull the sri hash from the link and autocopy it into the bookmark.
#featurerequest
If we are moving out of the http/web space into some sort of distributed protocol, just use magnet links, problem solved. Or some equivalant hash based content-addresable scheme. (How applicable depends on what space we are talking about)