Beginning to believe messenger apps need modes corresponding to threat models. So you can set conversations sensitivity levels and trade off features for security depending on content.

Living at defcon 5 all the time is shit and a guarantee against adoption.

Not having security as an option is equally bad.

Reply to this note

Please Login to reply.

Discussion

I agree. For example, sending spoof messages to prevent timing-based surveillance requires a lot of bandwidth if you have thousands of DMs. It’s definitely a “defcon 5” feature.

Yep. This is something you should only have on if your threat profile requires it.

But that can even trickle down to e2e, perfect forward secrecy, notifications, etc. For some conversations I don’t mind a little meta data leakage, especially if it’s to gain useful and fun features. For other conversations I want ft. Knox.

Yes. And messenger apps need to...

- support migration to new devices

- allow different auto fetch and render URL rules per contact

- allow geofencing and expiration per contact

- allow different personas per contact

- allow naming, tagging, notes for a contact

Even nostr apps miss the last which is super low hanging fruit. No matter how many times TheSameCat changes their display names, nip05 ref, or profile pics to resemble long haired college Tatum, I want my constant label to appear so I know who im talking to

I love all these features. Per contact or conversation.