100% the most important "failed" innovation on the web. 100%. we absolutely should have paid attention & figured out how to do more with this. the market failed

100% the most important "failed" innovation on the web. 100%. we absolutely should have paid attention & figured out how to do more with this. the market failed to see a good thing, failed to embrace it. more recently, there was Foreign Fetch[1]. i forget what particular sad pathetic excuse of a demise axed this brilliant follow up, but again, another total game changer re-decentralizer that even more alas, is left on the chopping room floor. actually wait, i do remember: Google wanted to use it for hosting fonts, but then Host Cache Partitioning came along, and it's champion's star use case became uninterested in it & it collapsed overnight. Foreign Fetch made all the sense in the world. if Service Workers can render resources for a origin, why not let it render resources for other origins? that's still within a single browser though. Unite is next level bold: why not let a client render resources for other clients? i still think Foreign Fetch is one of the alltime easiest/clearest/best wins the web could have had, would have radically re-enabled offline first, and set forth the idea that a origin loaded on user-agent/browser deserves real presence. some day i really want to make a web page where components can have ipv6 addresses, and then just internetwork components across network tunnels[2]. [1] https://developers.google.com/web/updates/2016/09/foreign-fetch https://developers.google.com/web/updates/2016/09/foreign-fe... [2] https://github.com/rektide/ipvsixland https://github.com/rektide/ipvsixland