News for hackers. Stuff that matters.
Re:Firefox Send: Private, Encrypted File Sharing by the8472 on Wednesday October 11, 2017 @02:20PM (#15451946)
This would also have the added bonus that one could reload such pinned resources from anywhere once you got the pin. Even without TLS setup or having to trust certificate chains.

Caching proxies would suddenly become viable again because only the first download has to through HTTPS while "I don't have this in the local cache anymore, can you serve me this content" requests could go through sidechannels or outside the TLS handshake or something like that. Caches could even perform downgrade non-attacks.

Re:Firefox Send: Private, Encrypted File Sharing by Dylan16807 on Wednesday October 11, 2017 @04:11PM (#15453016)
How many pins would you expect a browser instance to have? I feel like most of the time the pinned content could fit in the browser cache and make this variety of proxy-side caching pointless.
Re:Firefox Send: Private, Encrypted File Sharing by the8472 on Wednesday October 11, 2017 @05:00PM (#15453442)
Immutable content is a prerequisite for pins. The caching benefits mostly fall out of the immutability, not the pinning. So as long as the hypothetical standard would allow one to be used without the other additional uses could fall out of that stack.
Re:Firefox Send: Private, Encrypted File Sharing by Dylan16807 on Wednesday October 11, 2017 @06:31PM (#15454111)
My point is, those particular benefits only exist in a narrow circumstance where the browser is half-caching.