Skip to content

Blog: instant messengers, not one size for all, what do I miss? (In other words or close to threat modeling?) #338

@Mikaela

Description

@Mikaela

Chatting at Keyoxide Matrix room (https://matrix.to/#/%23keyoxide%3Amatrix.org/%24_0RWnAFyj185DKZdesHGhJjI-xoAU1ZsNsBDw_z_FZw?via=matrix.org&via=mackenba.ch&via=libera.chat) brings up this as blog idea, while I have been wondering about this otherwise too.

So if it were up to you we should all be using _____ and why? :)

"whatever suits our needs in this context" and "this is not one size fits all question"

My comfort zone would be 1. E2EE 2. self-destructing messages 3. knocking.
And this is widely supported until adding 4. open source and suddenly about everything disappears. Don't even dare to think of 5. support for multiple accounts or 6. support for multiple devices.

The first three are provided by WhatsApp and Signal. Telegram misses 1. Matrix misses 2. and client implementation of 3. (with the exception of #nheko:nheko.im 💜). SimpleX.Chat that I have recently been optimistic about is missing 3. and 6. Additionally it places user privacy before actually getting messages delivered, so sometimes it's even worse than Matrix eventual consistency taking months for messages to appear 🫠
and my comfort zone is not public world-readable room such as this, so this is not to be taken as suggestions for Keyoxide project

Loosely related to #244?

Metadata

Metadata

Assignees

Labels

blogBlog ideas and issues

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions