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 get it and if you want to provide the functionality you want to offer then there has to be some compromise. Personally I'm a huge proponent of e2e, even if I'm chatting with my wife to check what groceries we need from the store. And the integrity of that encrypted path breaks with this model. I'm sure others are ok
0 reply
0 recast
0 reaction
