|
Corresponding ticket: [[!tails_ticket 14567]]
|
|
Corresponding ticket: tails/tails#14567
|
|
|
|
|
|
|
|
|
|
|
|
[[_TOC_]]
|
|
|
|
|
|
[[!toc levels=3]]
|
|
|
|
|
|
|
|
# Characteristics of mobile messengers
|
|
# Characteristics of mobile messengers
|
|
|
|
|
... | @@ -89,7 +91,7 @@ more than an actionable decision. IMO we need finer-grained prioritization. |
... | @@ -89,7 +91,7 @@ more than an actionable decision. IMO we need finer-grained prioritization. |
|
## Tox
|
|
## Tox
|
|
|
|
|
|
- [Tox website](https://tox.chat)
|
|
- [Tox website](https://tox.chat)
|
|
- [[!tails_ticket 10071]]
|
|
- tails/tails#10071
|
|
- client (qtox) available in Debian Buster
|
|
- client (qtox) available in Debian Buster
|
|
- decentralized
|
|
- decentralized
|
|
- it is possible to set it to work with Tor as a SOCKS5 proxy
|
|
- it is possible to set it to work with Tor as a SOCKS5 proxy
|
... | @@ -105,7 +107,7 @@ more than an actionable decision. IMO we need finer-grained prioritization. |
... | @@ -105,7 +107,7 @@ more than an actionable decision. IMO we need finer-grained prioritization. |
|
## Matrix/Riot
|
|
## Matrix/Riot
|
|
|
|
|
|
- [Riot website](https://matrix.org/docs/projects/client/riot.html)
|
|
- [Riot website](https://matrix.org/docs/projects/client/riot.html)
|
|
- [[!tails_ticket 15209]]
|
|
- tails/tails#15209
|
|
- decentralized
|
|
- decentralized
|
|
- Riot supports: IM, VoIP, Videocall & - conferencing, File Transfer (of course) and SMS
|
|
- Riot supports: IM, VoIP, Videocall & - conferencing, File Transfer (of course) and SMS
|
|
- bridges to Slack, Gitter, IRC, Telegram, Twitter etc.
|
|
- bridges to Slack, Gitter, IRC, Telegram, Twitter etc.
|
... | @@ -121,7 +123,7 @@ more than an actionable decision. IMO we need finer-grained prioritization. |
... | @@ -121,7 +123,7 @@ more than an actionable decision. IMO we need finer-grained prioritization. |
|
## Signal
|
|
## Signal
|
|
|
|
|
|
- [Signal website](https://signal.org)
|
|
- [Signal website](https://signal.org)
|
|
- [[!tails_ticket 15200]]
|
|
- tails/tails#15200
|
|
- centralized server
|
|
- centralized server
|
|
- mass adopted
|
|
- mass adopted
|
|
- the Chromium-based app actually moved to the Electron application framework in early 11/2017
|
|
- 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: |
... | @@ -156,7 +158,7 @@ feedback from testing the flatpak based installation: |
|
## Wire
|
|
## Wire
|
|
|
|
|
|
- [Wire website](https://wire.com)
|
|
- [Wire website](https://wire.com)
|
|
- [[!tails_ticket 15196]]
|
|
- tails/tails#15196
|
|
- desktop client ("it is an experimental build", from wire webpage)
|
|
- desktop client ("it is an experimental build", from wire webpage)
|
|
- centralized
|
|
- centralized
|
|
- works over Tor
|
|
- works over Tor
|
... | @@ -167,7 +169,7 @@ feedback from testing the flatpak based installation: |
... | @@ -167,7 +169,7 @@ feedback from testing the flatpak based installation: |
|
## XMPP
|
|
## XMPP
|
|
|
|
|
|
- [XMPP website](https://xmpp.org/)
|
|
- [XMPP website](https://xmpp.org/)
|
|
- related: [[!tails_ticket 11541]]
|
|
- related: tails/tails#11541
|
|
- Protocol with [lot of choices for clients](https://xmpp.org/software/clients.html)
|
|
- Protocol with [lot of choices for clients](https://xmpp.org/software/clients.html)
|
|
- decentralized
|
|
- decentralized
|
|
- desktop client available
|
|
- desktop client available
|
... | @@ -178,8 +180,8 @@ feedback from testing the flatpak based installation: |
... | @@ -178,8 +180,8 @@ feedback from testing the flatpak based installation: |
|
|
|
|
|
# Related
|
|
# Related
|
|
|
|
|
|
* [[VoIP_support]]
|
|
* [VoIP support](VoIP_support)
|
|
* [[replace_Pidgin]]
|
|
* [replace Pidgin](replace_Pidgin)
|
|
|
|
|
|
# Free and random thoughts
|
|
# Free and random thoughts
|
|
|
|
|
... | @@ -197,3 +199,4 @@ are open sourced for review. some messengers implement free software protocols o |
... | @@ -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
|
|
- 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.
|
|
- 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).
|
|
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).
|
|
|
|
|