Les Greys
@les
Beeper.com Genius!
13 replies
0 recast
1 reaction
@
0 reply
0 recast
0 reaction
Ben Metcalfe
@dotben
The issue is that it breaks e2e because they host the receiving endpoints and federate them through to the local app. That frustrates me not only because it's not obvious to non-technical users but I, on the other side of the e2e messaging interaction, wrongly assume our communication is protected.
1 reply
0 recast
0 reaction
Eric Migicovsky
@ericmigi
You will be able self host your own bridges, which does not break e2ee. Also keep in mind that 12 out of the 15 networks on Beeper do not even have e2ee in first place. Some people choose to use Beeper only for those networks. But above all, we are giving users the choice.
2 replies
0 recast
0 reaction
Eric Migicovsky
@ericmigi
We also inform users of the choice they are making https://beeper.notion.site/Welcome-to-Beeper-f7087411cbdc465198c3299bc42d8aaa
1 reply
0 recast
0 reaction
Ben Metcalfe
@dotben
I'm being pedantic here, but in any e2e communication there are 2 (or more) users involved and only the user running Beeper is informed. If I'm chatting with you Eric via Signal I'm assuming you're receiving the comms e2e down to the native app on your device. I have no way of knowing you're using Beeper, and it's not
1 reply
0 recast
0 reaction
Eric Migicovsky
@ericmigi
If you send a message to someone else, you have to assume that they can do anything they want with it. Take WhatsApp and iMessage for example. They are 'e2ee' but both have default backup options that backup messages in cleartext (WA) or with dencryption keys (iCloud)
0 reply
0 recast
0 reaction
