That's at the lowest level, as you work up the stack it gets even worse.
-
-
Replying to @mikeal
Another important point: non-web p2p clients have a high likelihood of being designed to "cheat" the network for their own benefit.
1 reply 1 retweet 6 likes -
Replying to @mikeal
A lot of work goes into preventing this behavior, and this goes beyond the "trustless" nature of p2p generally.
1 reply 1 retweet 6 likes -
Replying to @mikeal
But on the Web all of the code is "installed" by an authority (the website domain) and has a 99.9% chance of running un-changed.
2 replies 1 retweet 8 likes -
Replying to @mikeal
You still have to worry about proper signing and not entirely trusting other peers, but you can keep the network healthy pretty easily.
1 reply 1 retweet 7 likes -
Replying to @mikeal
In decentralized Web technologies the vast majority of peers can effectively be "controlled" by the installing authority.
1 reply 2 retweets 7 likes -
Replying to @mikeal
While today all this decentralization is viewed under the same umbrella, it's increasingly clear that they are going to widely diverge.
1 reply 1 retweet 7 likes -
Replying to @mikeal
History being a good guide, we can presume that things built outside the constraints of the Web won't survive a shift to the Web.
5 replies 2 retweets 14 likes -
-
Replying to @slightlylate @mikeal
Interestingly (to me, at least), going the other way is easier. Web is harder, so once something is "web ready", other stacks easily adopt
2 replies 0 retweets 1 like
(RTC, H/2, TLS, image formats, etc.)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.