←back to thread

It looks like Signal isn't as open source as you thought it was anymore

(www.androidpolice.com)
242 points raybb | 4 comments | 06 Apr 21 18:04 UTC | HN request time: 0s | source
Show context
chrisco255 ◴[06 Apr 21 19:55 UTC] No.26716611[source]▶
Just use Status: https://status.im/private-messenger/

Mozilla Public License - E2E Encryption - P2P Messaging - Active community & git repo - Integrated Ethereum wallet for Web3 access

replies(4): >>26716753 #>>26716797 #>>26717291 #>>26717352 #
speedgoose ◴[06 Apr 21 20:12 UTC] No.26716797[source]▶
The integrated ethereum wallet is a red flag for me.
replies(3): >>26716827 #>>26716880 #>>26717595 #
1. ubercow13 ◴[06 Apr 21 20:15 UTC] No.26716827[source]▶
The messaging itself actually runs on the ethereum network.
replies(1): >>26717510 #
2. michaelsbradley ◴[06 Apr 21 21:18 UTC] No.26717510[source]▶
No it doesn't.

The messaging is run on a decentralized network that uses the Waku protocol.

Currently the clients (mobile and desktop) use Waku v1: https://rfc.vac.dev/spec/6/

But work to transition to Waku v2 is underway: https://rfc.vac.dev/spec/10/

replies(1): >>26717881 #
3. ubercow13 ◴[06 Apr 21 21:56 UTC] No.26717881[source]▶
Yes but isn't the Waku v1 protocol running on ÐΞVp2p, which uses the Ethereum network? The protocol is Waku, but as far as I understand the 'decentralized network' is the Ethereum network?
replies(1): >>26718157 #
4. chrisco255 ◴[06 Apr 21 22:27 UTC] No.26718157{3}[source]▶
Here's the specs: https://specs.status.im/spec/10

That's correct. It uses Waku for routing and messaging, but the Waku nodes are Ethereum nodes with Waku v1 enabled.

Here's more from VAC, the org behind Waku and their plans for v2: https://vac.dev/waku-v2-ethereum-messaging