Re:Vapor – Decentralized Web over Bitcoinized HTTP
by X6S1x6Okd1st on Wednesday October 07, 2020 @02:53PM
(#24711365)
You only know that the connection has not been MITM if you have actually identified that the public keys that you want to use or trust that they are correct due to a WoT (e.g. they are signed by a CA your OS trusts or GPG WoT).
Re:Vapor – Decentralized Web over Bitcoinized HTTP
by monokh on Wednesday October 07, 2020 @12:58PM
(#24710202)
2 identities knowing data came from each other due to the properties of public key encryption. Is this a good summary? For which use cases should this property come in handy?
Re:Vapor – Decentralized Web over Bitcoinized HTTP
by jkhdigital on Wednesday October 07, 2020 @07:10PM
(#24713899)
Yeah it took me a while to figure out this is what’s going on, I don’t understand why it was tossed in a word salad.
Because the goal is not to lower hosting costs and avoid DDoS, but to create a data structure that can be routed around in a trustless manner (by double signing the HTTP requests and encapsulating in an offchain Bitcoin transaction format with unique SHA256 hash ids for secure synchronization), it's solving a completely different problem. The features were derived from this goal.