- Riot supports: IM, VoIP, Videocall & - conferencing, File Transfer (of course) and SMS
- bridges to Slack, Gitter, IRC, Telegram, Twitter etc.
@@ -121,7 +123,7 @@ more than an actionable decision. IMO we need finer-grained prioritization.
- centralized server
- mass adopted
- the Chromium-based app actually moved to the Electron application framework in early 11/2017
@@ -156,7 +158,7 @@ feedback from testing the flatpak based installation:
- desktop client ("it is an experimental build", from wire webpage)
- works over Tor
@@ -167,7 +169,7 @@ feedback from testing the flatpak based installation:
- related: [[!tails_ticket 11541]]
- related: tails/tails#11541
- Protocol with [lot of choices for clients](https://xmpp.org/software/clients.html)
- desktop client available
@@ -178,8 +180,8 @@ feedback from testing the flatpak based installation:
# Free and random thoughts
@@ -197,3 +199,4 @@ are open sourced for review. some messengers implement free software protocols o
- nearly every mobile messenger is (money-wise) free-to-use
- in the end, even if a product is presented and promoted as open source aka. free software, it may be, but won't be totally. The providers claim that the client software is free software. And it indeed is in nearly every case, even if it's doing some weird stuff (looking at Telegram here). But no one will effectively show us what's running on the other side. Maybe some source code is opened, but in the end no one will know, what is executed on the shiny silicon of WhatsApp, Telegram, Signal, etc. We even won't know what metadata will be kept there, for how long, for which purpose, and witch which and with whom this data is going to be shared.
Let's assume that the math in the modern crypto works. The provider/state will only see encrypted garbage. Fine. But what about the layers around? From, at which time the message is leaving, to which data center? (etc. etc. you get the picture) This is definitely not in our hands anymore (in most places).