@Blaumensch1 @kuketzblog nein.
#XMPP+#OMEMO & #PGG/MIME mit #SelfCustody und Anbietern in der #EU, die keine Niederlassung, Geschäftsrätigkeit oder Anteilseigner aus den #USA haben.
Bspw.: @monocles / #monoclesChat und @delta / #DeltaChat.
#Signal würd' ich mir auch nicht geben...
@lastquake do you also have an #XMPP / #Jabber - #bot as well?
@joo4mart @phreaknerd @melsdung Ja und entgegen @nocci's reply liefer ich "Praktikable Lösungen" auch.
Ich helfe auch gern, nur gegen Unwillen und Faulheit kann ich nicht agieren.
Gibt @cryptoparty@mastodon.earth / @cryptoparty@chaos.social für jene die sich drum scheren.
Macht doch was ihr wollt aber heult nicht wenn vorhersehbare Konsequenzen weh tun!
@phreaknerd @melsdung @nocci exakt deshalb rate ich zu #XMPP+#OMEMO ( @monocles & @gajim ) sowie #PGP/MIME ( @delta & @thunderbird ), denn nur #dezentral mit #SelfCustody aller #Keys besteht echte #E2EE!
Ich helfe gern "#Normies" und "#TechIlliterates" darauf umzustellen...
@pixelcode @phreaknerd @melsdung @nocci das bzgl. #Signal halte ich bestenfalls für ne #Werbelüge, weil nicht evidenzierbar!
Und wer #monocles oder anderen Anbietern nicht vertraut kann #XMPP selbst.hosten und hat bei #OMEMO ohnehim doe Kontrolle über die Schlüssel.
Alles andere ist naiver Glauben dass @Mer__edith für Nutzer*innen Knast riskieren würde…
https://infosec.space/@kkarhan/114234551915193036
Just like #IRC & #XMPP+#OMEMO and #PGP/MIME will do the same for #GroupChats and #Messaging in general!
@phreaknerd @melsdung @nocci bis darauf dass #Signal auch unter #CloudAct fällt und genauso zentralisiert ist wie #Telegram und genauso #TrustMeBro in Sachen Nicht-Kooperation agiert...
@AndreasEsch Garnicht!
Solche #Gruppenzwang|skinder kannste nur dazu zwingen, indem du konsequent auf #XMPP+#OMEMO migrierst und dich allem anderen verweigerst!!!
Open Letter to Meta: Support True Messaging Interoperability with XMPP
The European Digital Markets Act (DMA) is designed to break down walled gardens and enforce messaging interoperability. As a designated gatekeeper, Meta—controlling WhatsApp and Messenger—must comply. However, its current proposal falls short, risking further entrenchment of its dominance rather than fostering genuine competition.
...
Meta Has Already Used XMPP—Why Not Now?
WhatsApp was built on an XMPP-based server, and Meta has previously supported XMPP in Facebook Messenger. The protocol is already battle-tested at scale. Furthermore, Meta is embracing federation for Threads with ActivityPub, proving that interoperability works when it serves Meta’s strategic interests.
If Threads can federate, so can WhatsApp and Messenger.
@Wyatt_H_Knott precisely that
There are evidently superior alternatives like the #Fediverse & #XMPP+#OMEMO like @gajim / #gajim and @monocles / #monoclesChat.
This is an expecially good time to be around #XMPP
#profanity and #poezio were recently updated, while #gajim (and soon #converse.js) got a new major release. These are all #XMPP clients, if you're not familiar with those names: first 2 are console-based, while gajim is a desktop client and converse.js is a web client.
Even #Movim (web client) will have another big release soon, supporting #audio #video #calls and #screensharing.. Want to give it a go? 
I just donated to #Monocles as I use their #XMPP chat app on a daily basis.
Please help them by extending your support 
https://www.startnext.com/en/monocles.
"Open Letter to Meta: Support True Messaging Interoperability with XMPP"
https://xmpp.org/2025/03/open-letter-to-meta-support-true-messaging-interoperability-with-xmpp/
There are no known security issues with "Siacs OMEMO" / OMEMO v0.3¹ despite of what some very loud Signal fans would like you to believe. It has been audited by a third party² who took a longer look at it than all of the Signal fans combined.
Yes, #OMEMO v0.7+ (or TWOMEMO 
) is a cleaner spec with more features (most notably Stanza Content Encryption). That’s why we wrote it. I’m a co-author. That doesn’t mean v0.3 is insecure.
¹: https://xmpp.org/extensions/attic/xep-0384-0.3.0.html
²: https://conversations.im/omemo/audit.pdf
@signalapp no it's not.
Being a #centralized, #SingleVendor & #SingleProvider solution subject to #CloudAct makes you inherently vulnerable by your own choice and thus trivial to shutdown compared to real #E2EE with #SelfCustody of all the keys and true #decentralization as well as #SelfHosting (i.e. #PGP/MIME [see @delta / #deltaChat et. al.] and #XMPP+#OMEMO [see @monocles / #monoclesChat et. al.]!)
And don't even get me started on you collecting #PII (espechally #PhoneNumbers) for no valid reason, (thus violating #GDPR & #BDSG)...
But yeah, I'll be patient to shout "#ToldYaSo" to your annoying cult of fanboys!
