@gnomon consider also #RocketChat and #XMPP+#OMEMO, depending on your needs and workflows.

#IRC obviously runs on every shitbox, so obviously makes sense to take a deeper dive.

@mauve #Bluetooth would make most sense, as even if you were to transfer like vCard files over original Bluetooth speeds (732,2 kbit/s) that would be convenient and fast enough.

• Problem may arise supporting #iOS as that only supports sending pictures, so you gotta have to do like some "Airgapped Transfer Protocol" thingy and like #MattKC shove it into a PNG of a QR-Code…
• As for the chat itself, you could use #WebRTC infrastructure like #WebCall or just mandate people to have like an #XMPP+#OMEMO account somewhere…

@TheMorpheus normal.

JEDE Person die sich zur #FDGO und den Werten des #Grundgesetz|es bekennt ist für das #Trump-Regime der #USA ein Staatsfeind!

• Anders kann Mensch diese shice nicht mehr in Worte fassen ohne Gefahr zu laufen justiziable Äußerungen von sich zu geben.
  • Folglich: #EncryptHarder! #XMPP+#OMEMO & #PGP/MIME!!

#USpol #Faschismus #Überwachungsstaat

@TheMorpheus Also letzteres Problem hab ich nicht.

#XMPP+#OMEMO funktioniert, und diverse Clients wie @monocles /#monoclesChat & #gajim machen es einfach.

• Alternativ gibt's mit @delta / #deltaChat nen exzellenten #Messenger der auf #eMail - Infrastruktur aufsetzt!

#Matrix ist in meiner Erfahrung jetzt noch nicht so pralle und nur dann sinnvoll wenn Leute #SelfHosting umsetzen können oder wollen.

• D.h. in Organisationen und Gruppen sinnvoll, aber für #TechIlliterates wohl kaum!

@andybalaam I disagree, because "truly end-to-end encrypted, decentralized & federated messaging" has been done at leadt trice befire #Matrix came along:

• #XMPP+#OTR ( @gajim & @monocles / #monoclesChat)
• #XMPP+#OMEMO ( #Gajim & monocles chat)
• #PGP/MIME ( @delta / #deltaChat & @thunderbird / #Thunderbird)…

Like I've been in #PGP-encrypted #MailingLists before Matrix and @signalapp were even proposed!

@lackthereof no, it's not because unlike #Phones and #PhoneNumbers, #eMail is not necessarily traceable by circumstances.

• Because a Phone "Line" (regardless of whether it's POTS, ISDN, VoIP, GSM, VoLTE, …) and #telephony in general are designed for realtime communication, they inherently necessitate an active, ongoing connection.
  • Even if it's just some App/PBX/… to connect to the provider and constantly state "I am on the network and able to recieve calls!" (with PSTN networks, there a physical line that gets assumed to have a phone connected)…

Whereas with eMail (and any #asynchronous #communication) you don't have that requirement.

• So unless the provider is being taken over or otherwise "cooperative" there's no means for a sender to know where, when and how a message was retrieved unless the recipient wants the sender to know of it!
  • Besides, even if you don't have an eMail provider like cock.li which natively supports @torproject / #Tor useage with an #OnionService, unless said provider explicitly prevents you from doing so, you can use not just Tor but also other techniques to make it extremely hard (not necessarily impossible, but at least unfeasible at scale!) to get tracked down.
  • In fact, you could even use #Sneakernet - Style distribution through "#MeatProxies" and #DeadDrops (aka. #dr0p) to further twart tracing attempts.

Or to put it simple:

• You can ring up someone and thus circumstantially verify the chain of #PhoneNumber -> #IMSI -> #ICCID -> #SIM -> #IMEI -> Device -> Location -> Owner quite quickly.
  • Whereas you can't positively verify whether an eMail address and/or #XMPP+#OMEMO account belongs to me unless I want you to know that it does!

So either way a phone number is just a horrible means of doing that.

• And don't even get me started on the fact that legally speaking noone truly owns their number.
  • Because even if you got some spechal case number (like UPT was) you still depend on neither regulators nor telcos to not block or otherwise interfere with it. Which is in contrast to say an OnionService which can only be shutdown effectively by sabotage aka. (more or less figurately) "unplugging" it.

I mean, it's not as if I didn't gave @signalapp a fair chance.

• I wanted #Signal to be good - honestly...
  • But I'm old enough that things rarely are that simple as #TechPopulism & #Propaganda claim it to be.
  • Just like 5th grade #SexEd is not a substitute for Endocrinology, Gynecology and Andrology and actually licensed, medical professionals.

So any #Messenger service that requires a #Phone Number for signup and/or useage is truly not a real replacement and inherently makes PROVEN WRONG assumptions [i.e. that it is legal and possible to obtain a phone number anonymously at someone's juristiction] about it's customers' ability to shield their privacy…

• Cuz all the "#Metadata" claims of Signal are complete #MarketingLies by virtue of them storing a Phone Number and not just being (as per admission by @Mer__edith) 'hard locked-in' with #aws but also subject to #CloudAct.
• They certainly are not deploying real #E2EE cuz you neither get #SelfCustody nor #SelfHosting and have to blindly trust them (aka. "#TrustMeBro!") that what they release as #SourceCode is actually what they deploy.
  • It's like all those "#VPN" shillings which one cannot verify to be true or false!

THIS is why I am going fucking ballistic on #TechPopulism aiming at #TechIlliterates because it's spreading a "false sense of #security" whilst completely disregarding absolute fundamentals when it comes to the underlying systems.

• And I don't mean shit like #Govware of the #SS7 kind, but absolute basics in #ITsec, #InfoSec, #OpSec & #ComSec that every @cryptoparty / @cryptoparty / #CryptoParty worth it's name touches on.
  • Signal can't and won't save peoples' asses and the sooner we realize that "complex problems are hard to fix" the less we waste Resources on #HoneyPots that stench like #CrytpoAG & #ANØM!