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].
It didn't fail, one just couldn't see its success. I was part of many lovely unite communities. No one was interested in serving huge audiences, we just made tools for ourselves.
Also worth shouting out Widgets, which were a great super interesting ultra flexible PWA-like-things before PWAs. ;)
They were more a micro-app store model than web pages that could be appified, but they had much more creative control over themselves. They arrived in 9.5, a year before the launch of the Palm Pre, a first & second star in the constellation of web-based applications.
Crypto is effectively monetising everything. Couldn’t this kind of system be tokenised, where you’d receive X reward for becoming a server on a decentralised web? I am not a crypto fanatic but seems like an interesting idea
you'd likely then have to pay a little micropayment for every site you go to, which would mean you'd be paying more for slower connections to a small collection of sites, which is not a great user story
Wouldn't that just lead to centralization anyway? If X reward is being dished out per server, why not scale your 1 server to several hundred, and hoover up all the rewards? You could then offer to host other people's apps, and give them a fraction of the tokens you got in return?
Nice, this sentence actually seems to explain pretty well why after more than 10 years for most of cryptocurrency tokens adoption and usability for common people is really minuscule. It looks like trying to design something with intention to "monetize" first and then invent purpose as an afterthought could be not easy endeavor.
9 comments
[ 2.3 ms ] story [ 34.6 ms ] threadmore 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-fe...
[2] https://github.com/rektide/ipvsixland
They were more a micro-app store model than web pages that could be appified, but they had much more creative control over themselves. They arrived in 9.5, a year before the launch of the Palm Pre, a first & second star in the constellation of web-based applications.
It was the centrepiece in the battle between visionaries and the money makers at a very decisive moment for Opera
A battle the visionaries lost.
The world would probably have been more interesting if they had chosen the blue pill instead of the red pill.
Not certain the shareholders would have been happier though. It is easy to root for the visionaries, but the choice is never that simple.
Nice, this sentence actually seems to explain pretty well why after more than 10 years for most of cryptocurrency tokens adoption and usability for common people is really minuscule. It looks like trying to design something with intention to "monetize" first and then invent purpose as an afterthought could be not easy endeavor.