#SingoeProvider

Kevin Karhan :verified:kkarhan@infosec.space
2025-01-10

@tejan the only correct way to deal with this is using proper #E2EE like #PGP/MIME & anonymous eMail accounts.

  • Providers can only #decrypt and #read for what they have the keys!

Same goes with #Messengers, which is why I only recommend #XMPP+#OMEMO (i.e. @monocles / #monoclesChat & @gajim / #gajim ) & PGP/MIME (i.e. @delta / #deltaChat & @thunderbird / #Thunderbird), because unlike #proprietary #SingleVendor & #SingoeProvider solutions, they offer #SelfCustody so even if a provider is cooperative or served a #subopena or got theor equipment seized, they can't decrypt the contents!

Kevin Karhan :verified:kkarhan@infosec.space
2024-11-19

@dnsprincess @WiGLEnet @eff

#XMPP + #OMEMO >>> @signalapp simply because #Signal falls under #CloudAct and demands #PII like #Phone numbers ehich they shouldn't and have no business to even request for.

Also all #centralozed, #SingleVendor & #SingoeProvider solutions are inherently insecure per design.

@Mer__edith et. al. will snitch when threatened with lifetime for not doing so.

#OpenSource #OpenStandards #Decentralization

Client Info

Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst