@manchicken @spycrab @shipwreckt I mean, if you want to gamble upon the #Trump regime not weaponizing #CloudAct and thus force @signalapp 's staff if not @Mer__edith herself at gunpoint to d0x their users (cuz they collected #PII in the form of #PhoneNumbers with no legitimate interest which is a #GDPR- & #BDSG violation!), then please go ahead.
Whereas with #XMPP+#OMEMO (or #PGP/MIME if you want to use @delta / #deltaChat) YOU ALONE are in control of all the keys, so even if say @monocles #monocles' staff were held at gunpoint, they can't decrypt your comms nor #MITM stuff in that scenario either.
You can't do that with #Signal and all their #Security is a "#TrustMeBro!" when it comes to it, whereas you can setup your own XMPP serbers and put them on @torproject / #Tor as #OnionService or behind your own #VPN in an organizational Network...
Seriously, please go outside and #TouchGrass!
Profanity crashes a lot... Here's to hoping that the Snikket SDK makes way for a better TUI.
@CafeJunkie @threemaapp Ganz einfach: Weil dann müssten diese gegenseitig und öffentlich zugeben, dass diese effektiv nur #XMPP-Klone sind oder gar XMPP direkt unter der Haube haben.
Weil XMPP+#OMEMO & XMPP+#PGP/MIME gibt's seit langem und funktionert.
Egal ob @gajim / #Gajim auf Desktop, #ProfanityIM auf #CLI oder @monocles / #monoclesChat auf #Android.
Und ja, es gibt da bereits einige Anbieter und wie bei #eMail kann Mensch zwischen diesen umziehen...
https://github.com/greyhat-academy/lists.d/blob/main/xmpp.servers.list.tsv
The #XMPP Newsletter for October '22 is out!
Read about the latest XMPP universe updates, such as #ejabberd, @Monal, @prosodyim, #ProfanityIM and of course the latest updates on our #Standards!
Enjoy! 📰 ☕
So the maintainer of the #profanityim #slackbuild script said that he isn't gonna maintain it anymore. So I got to work and got a good slackbuild going with the latest sources and when they open it back up I'll be taking over maintenance of my favorite #XMPP slackbuild.
Yay!