On: Vapor – Decentralized Web over Bitcoinized HTTP

[synctext]

> "trustlessly replicated to other Vapor nodes"

Instead of using central web servers, it is replaced with a network of Vapor nodes. I don't see this solving any problem. Just because HTTP requests have a Bitcoin signature, that does not solve any web-of-trust issues.

> record authenticated HTTP requests and replay them anywhere.

This is confusing, either identities cost real Bitcoin or you have a Sybil attack problem (numerous fake identities). If you need real Bitcoins, it requires lots of effort to use Vapor. As it is written, this is not going to work.

[larrysalibra → synctext]

It’s called “Vapor” as in “vaporware” and makes absolutely no sense.

I’m going to go out on a limb here and say we’re being trolled. The emperor is naked.

[m463 → larrysalibra]

The buzzwords are strong in this one.

[volaski → synctext]

Maybe wallets can implement an identity system (either as a standard or through federation among vapor nodes)?