in-web-browsers

https://github.com/ipfs/in-web-browsers/issues/121#issuecomm... > Google Chome makes SXG indistinguishable from regular HTTPS, which breaks basic assumptions around how users understand the green padlock in location bar (aka "nobody but me and the Origin server can see the payload"). UX of regular HTTPS is reused as-is, pretending that end-to-end HTTPS transport was used with Origin from location bar, which is not true. https://blog.intelx.io/2019/04/15/a-new-type-of-http-client-... https://docs.google.com/document/d/1ha00dSGKmjoEh2mRiG8FIA5s... > Big changes need strong justification and support. This particular change is bigger than most and presents a number of challenges. The increased exposure to security problems and the unknown effects of this on power dynamics is significant enough that we have to regard this as harmful until more

One interesting use case for SXG is to allow decentralised and offline websites, since the site's data can be tied to a key/certificate/domain without having to be downloaded from a specific server. As an example, the IPFS project is already trialling the technology: https://github.com/ipfs/in-web-browsers/issues/121

Lidel has written a lot about this in issues (nice index here: https://github.com/ipfs/in-web-browsers/issues/147), but I think the live (recorded) demo will have to wait. =]

A known good entry point could be delivered over a content-addressed medium like IPFS, and if you layer on SXG the consumer might still be able to validate the origin of the entry point. https://docs.ipfs.io/guides/concepts/ https://github.com/ipfs/in-web-browsers/issues/121

Does it make sense to add support for Signed HTTP Exchanges (SXG) to this? https://github.com/ipfs/in-web-browsers/issues/121

You can do this if you have IPFS Companion installed. Eg: ipns://dist.ipfs.io => http://localhost:8080/ipns/dist.ipfs.io Firefox only as noted by devttyeu There is talk of adding signed HTTP exchanges (same thing AMP uses to achieve the same idea[0]), but with content hosted on IPFS[1]. Native support for this may land in Brave someday currently there is an effort around adding IPFS[2] [0] https://news.ycombinator.com/item?id=19678914 [1] https://github.com/ipfs/in-web-browsers/issues/121 [2] https://github.com/brave/brave-browser/issues/819#issuecomme...