News for hackers. Stuff that matters.

A comment on Ask HN: Why does P2P encrypted messaging still suck?. Parent comment

Re:Ask HN: Why does P2P encrypted messaging still suck? by nosuchthing on Tuesday April 03, 2018 @04:10PM (#16748621)
Who would want to store their private messages on a public database?

Not to mention needing to buy ETH some how and than paying for every message?

[ Parent | on HN ]
Re:Ask HN: Why does P2P encrypted messaging still suck? by gravityblast on Wednesday April 04, 2018 @03:56AM (#16752883)
You don't need ETH to send messages on whisper. And Whisper doesn't store your messages on the blockchain.

https://github.com/ethereum/wiki/wiki/Whisper

[ Parent | on HN ]
Re:Ask HN: Why does P2P encrypted messaging still suck? by nosuchthing on Wednesday April 04, 2018 @05:04PM (#16759079)
Interesting protocol, thank you for sharing and correcting my misunderstanding.

  Uncertain-latency Not designed for RTC.
At first glance, this looks like a client broadcasts the Whisper to another server which than places it in a cache and might forward to more clients if enabled. Eventually the cache is cleared and there's no telling if the message will propagate successfully in any given time frame?
[ Parent | on HN ]
Re:Ask HN: Why does P2P encrypted messaging still suck? by adambbb on Thursday April 05, 2018 @10:30AM (#16765202)
More or less it's how you described it. The current implementations broadcast messages to all connected peers supporting the protocol every a few hundreds of milliseconds.

It's also true that there is no confirmation that the message reached the recipient (in order to provide dark routing). This can be built on top of Whisper in a separate communication protocol.

[ Parent | on HN ]