@signalapp It's not #disinfo when one points out that you demand #PII aka. #PhoneNumbers from Users and that is literally a architectural vulnerability, alongside your #proprietary & #Centralized #Infrastructure.

• #Signal being a #SingleVendor & #SingleProvider #Solution is literally the reason why I consider it #insecure.

Not to mention the lack of @torproject / #Tor support with an #OnionService or the willingness to fulfill #cyberfacist "Embargoes" or shilling a #Shitcoin #Scam named #MobileCoin!

• #KYC is the illicit activity!!!

And don't get me started on the #cyberfacism that is #CloudAct.

• If you were secure, criminals would've used your platform so hard, it would've been shutdown like #EncroChat and #SkyECC.

I may nit have allvthe.evidence yet, but #Signal stenches like #ANØM: #Honeypot-esque!

@Natanox @ccc@anonsys.net @chaosupdates @CCC@social.bau-ha.us @ccc@chaos.social @ccchh leider ist m2ylflyeak6i6o4hsfwcrfwcq2bbjxk6nf2rnmm7fu6qiuu3hybenzid.onion / http://jabber.ccc.de #OnionService immernoch down!

@rysiek @agturcz that's not how you fix #TechIlliteracy, espechally since things changed for the better.

@monocles / #monoclesChat & @gajim / #gajim are quite easy, whereas @signalapp / #Signal demands #PII in the form of a #Phone number which is more often than not not legally obtainable without "#KYC" aka. "forced #SelfDoxxing" all whilst being an extremely #centralized, #SingleVendor & #SingleProvider solution that falls under #CloudAct ant thus cannot adhere to #GDPR & #BDSG!

• Sorry, but "#TechPopulism" alike "JuSt UsE sIgNaL !" won't fix #TechIlliteracy but rather provide false sense of security to #TechIlliterates when the correct solution is to teach proper #TechLiteracy like @cryptoparty@chaos.social / @cryptoparty@mastodon.earth / #CryptoParty does...

Otherwise we'd only perpetuate the #Enshittification-#Lifecycle as has happened with #AIM, #ICQ, #BBM and so many more...

• Mark my words, cuz I've been proven correct up to this point.

If #Signal and @Mer__edith actually cared, they would've setup their system truly decentralized as an #OnionService over @torproject / #Tor!

@agturcz @rysiek Use @torproject or better yet, #XMPP+#OMEMO with an #OnionService aka. #Server on a .onion domain...

• Then you don't have to trust anyone else...https://infosec.space/@kkarhan/113868473221719432

@lmorchard @vkc nodds in agreement I'm flabberghasted by rising #MediaIlliteracy & #TechIlliteraxy despite things being easier to do than ever before.

• This ain't like 1999 where one had to buy a book to learn #HTML and be rich enough to afford #ADSL!

Nowadays even a cheap smartphie can host an #OnionService and stuff like #OnionShare even makes way easier...

• Not to mention how cheap simple #Webhosting and #VPSes and #ReburbishedHardware is these days...

#WasFehlt:

Nen #Stellenmarkt

• ohne #Bullshit,

• mit #Gehaltstransparenz,

• ohne #Filler-Anzeigen ohne spezifische Vakanz dahinter,

• mit verbindlichen Angaben zur Position wie #Arbeitszeiten, #Arbeitsort, #Vertragsart, #Gehalt, etc.

• ohne erkaufbare und wegnötigbare #Bewertungen,

• nur mit anonymisierten & verifizierten Bewertungen,

• ohne "#KI" #ChatBots, #BotAccounts, #Spam und #Werbung,

• mit Verbot doppelter Anzeigen und klarer Deduplikation sowie tatsächlichen #Moderatoren die #Meldungen bearbeiten und beantworten,

• ohne Bullshit wie #JavaScript, #Cookies, #Tracking, etc,

• mit wirklichen, verpflichtenden #Kontaktdaten, gern auch als #OnionService auf #Tor wie #eMail + #PGP-Pubkey, #XMPP+#OMEMO für #Chat und #WebCall für #Bewerbungsgespräche - sofern diese auch nur ansatzweise notwendig sind.

• ohne #BuzzwordBingo und anderen Bullshit...

@delta TBH, I think that #deltaChat, alongside @monocles / #monoclesChat is one of the few real #E2EE #Chat & #Messaging solutions (which allow for full #SelfCustody of keys as well as being based on #OpenStandards for a #MultiVendor & #MultiProvider ecosystem) and even out-of-band verification and key exchange...

• The main difference is that deltaChat implements #PGP/MIME on #IMAP+#SMTP, which may be easier to setup in some cases and also offer an easy pipeline to archival requirements in #business setups whilst #monocles chat uses #XMPP+#OMEMO first and supports PGP/MIME as a secondary option, making it a good option in individual setups...

Needless to say both support using @torproject / #Tor via #Orbot and thus connecting to an #OnionService or just anonymously connecting to the server one personally chooses...

• So unless a provider explicitly bans Tor proactively, they'll work just fine.

The advantage of XMPP is that it also allows for calls, whereas I've to see how one can do Group Chats on deltaChat at all...

@pixelcode @alshafei again: That is mitigateable by having plausible deniability of said identities and using @torproject / #Tor to connect to said services.

In fact, just using #Orbot and @monocles / #monoclesChat allows you to connect to any XMPP Service, including those that have an #OnionService.

It takes mere seconds to get someone setup and ready to go!

Whereas with #centralized, #proprietary & #SingleVendor / #SingleProvider services, your only security is said provider/vendor saying "#TrustMeBro!"...

Espechally tying accounts to #PhoneNumbers is a big no-go IMHO because that's trivial if not already being spied upon by LEAs and in more juristictions than ever before it's basically illegal to acquire any #SIM without "identification" aka. self-doxxing towards the provider!

And if you really need like an organization group chat, self-hosting #Zulip is an option, as the messages are kept on the server and you just kick user accounts if they get arrested or their equiment confiscated.

#ComSec & #InfoSec necessitate proper #OpSec & #ITsec anyway...