3 ms·
Why I chose not to use SimpleX after investigating it last year: - No multi-device support. I want to send and receive messages using any of my devices, indepe
by foresto 10mo ago
Why I chose not to use SimpleX after investigating it last year:
- No multi-device support. I want to send and receive messages using any of my devices, independently, no matter where they are. (Being able to tether a phone to a computer is not sufficient.)
- Messages are dropped if not retrieved a timely manner. 21 days by default, which is shorter than some of my vacations.
- It was not clear to me what happens to undelivered messages when a queue server crashes, loses power, or reboots for maintenance.
- Establishing a chat requires sharing a large link or QR code through some out-of-band channel, which I often find inconvenient.
- Funded almost entirely by venture capital. This suggests to me that it is likely to either vanish or turn to some form of exploiting users, eventually. I don't want to build my contacts network upon that foundation.
- It was not clear to me who controls the queue servers, what incentives exist for their operators, or how their maintenance is funded. Absent that information, I must assume that most or all of them are run by the same people, making it a hair's breadth from a centralized service.
- Frequently repeated marketing claims of having no user IDs, when its message queue IDs are user IDs. The privacy improvement vs. a traditional service is through generating a distinct ID for sharing with each contact in 1:1 chats. (Group chats do not have this feature.) While I consider this valuable (it's like automatically giving you a separate email alias for use with each contact), I despise that it was presented as something that it is not. Perhaps they have stopped making the original claim by now, but even if so, the fact that they lied to people in the first place makes me unlikely to entrust my communications to them.
I prefer Matrix. I'll comment separately regarding why.