@oceanhaiyang I only can link to documentation why you should use @monocles over @Tutanota & @protonprivacy because both refuse to elaborate or support #SelfCustody of #Keys!
Also Proton snitched on their users - as will every single provider cuz #corporations can't invoke the right to remain silent!
@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.
@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
@Komodore68 ich vertraue #1Password nicht, weil ich #CloudZwang & #SaaS misstraue!
@menel @patrick and #Signal despite their #FUD and #MarketingLies is a very #cebtralized, #SingleVendor & #SingleProvieer system relying on #GAFAMs and their #API|s as well as neither allowing #SelfCustody nor #SelfHosting.
Not to mention it's toxic followers that avt like cultists!
@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!
@signalapp I disagree because your platform is #proprietary, #SingleVendor, #SingleProvider and doesn't allow for #SelfHosting, #SelfCustody of all the Keys and you demand #PII in the form of a #PhoneNumber which can be used.to track users down!
@ueeu I think crucial parts is looking at it's components, dependencies, size and for apps permissions.
#ReproduceableBuilds for example are important, so the actually released source code is what people actually get served as basis.
Plus in terms of #security, choose *real #E2EE with #SelfCustody of all the #Keys!
@bdf2121cc3334b35b6ecda66e471 @froge @fj maybe but it's better than a #proprietary, #SingleBendor & #SingleProvider solutiom as it just works even on #throttled, sub-#2G speeds over #Tor...
@fj I still think @signalapp has fundamental flaws like demanding #PII (#PhoneNumbers can't be obtained anonymously around the globe and are trivial to track down to devices and thus users), being subject to #CloudAct as an unnecessary & 100% avoidable risk as well as #Shitcoin-#Scam shilling (#MobileCoin) and it's #proprietary, #SingleVendor & #SingleProvider nature that makes it inferior to real #E2EE with #SelfCustody like #PGP/MIME & #XMPP+#OMEMO!
@licho @osman provide evidence the code @signalapp released is actually being deployed.
git and builds it from source.Not to mention pushing a #Shitcoin-#Scam (#MobileCoin) disqualifies #Signal per very design!
https://www.youtube.com/watch?v=tJoO2uWrX1M
And don't even get me started on the fact.it's not sustainable to run it as a #VCmoneyBurningParty!
Same as identifying users: They already got a #PhoneNumber which in many juristictions one can't even obtain without #ID legally, thus making it super easy to i.e. find and locate a user. Even tze cheapest LEAs can force their local M(V)NOs to #SS7 a specific number...
Again: Signal has a #Honeypot stench, and you better learn proper #E2EE, #SelfCustody and #TechLiteracy because corporations can't pull the 5th [Amendment] on your behalf!
@osman If your #OpSec, #InfoSec, #ComSec and/or #ITsec relies on @signalapp and/or @Mer__edith risking jail or worse, you fucked up!
Seriously, to me #Signal stenches #Honeypot like #ANØM & #CryptoAG.
That's why I get people setup with it!
@Catwoman69y2k @dragonfriend most importantly:
Only with #SelfCustody of all the keys, #SelfHosting of the entire infrastructure and everything being #OpenSource, one can assure (and [let it be] audit[ed] independently) that the #advertised #promises are in fact true.
Cuz not expecting @Mer__edith to break is the same level of "#TrustMeBro!" assurances as #ANØM, #EncroChat, #SkyECC, #WhatsApp etc. do in their #advetising #lies!
@Catwoman69y2k @dragonfriend All #GroupChats that ain't fully #E2EE with #SelfCustody are inherently insecure.
@FediThing @nicoco @fabiscafe @vkc nodds in agreement
"Perfect" would be #OneTimePad, but that's just not in the cards - period!
#XMPP+#OMEMO & #PGP/MIME are the next-best options that are documented, multi-vendor & multi-provider standardsband offer #SelfCustody of all the keys.
@catsalad @Em0nM4stodon +9001%
My Energy is:
"#UnsupervisedChildren will be given free #USB Flashdroves with @tails_live / @tails / #Tails on and taught proper #E2EE with #PGP/MIME, #XMPP+#OMEMO, #SelfCustody as well as the concept of #STFUfriday!"
@cryptoparty / #CryptoParty NOW!
@m4ra which is why having real #E2EE with #SelfCustody of all the Keys is vital!