weird internet kid. helping Creators with /seemore. yapping on /okbanger. curating in /creators and /cameron. dev + veteran + HBS. 
seemore.tv/cameron 🫡

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.

GP @ Monochrome Capital ◢◢ [B2B Web3 + other stuff]

Co-Founder @ Mnemonic [NFT Data API]

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

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.