Comment by rjzzleep

3 years ago

Problem is Signal people had really odd visions how to make basic functionality work. This isn't really because SMS/MMS are bad(yes they are).

But there are threads in their issue tracker where Signal people would disagree with basically functionality of responding to text messages on dual sim devices. "We'll always use the Signal registered number as default".

One part of this is a terrible(but working) protocol, the other is really weird product management where basic needs of the consumer are brushed aside with a "I know best approach" that doesn't really work when you're not in the shoes of apple and have the ability to just replace SMS altogether.

Yeah, I've hit this interesting attitude from Signal developers when I noticed they hijack the SMS datastore which then becomes inaccessible to tools like SMS Backup & Restore and tools that forward SMS notifications to other devices.

The developers were adamant that they know better than me what I want from my SMS tool. And then proceeded to work on crypto and stories.

Agreed. I remember when - years ago - they unilaterally switched all Android devices to use the Apple emoji. No consultation, no investigation with users, no reason other than they wanted consistency across their apps.

Took a lot of grumpy users before they backtracked.

I use and like Signal. I'm not smart enough to disagree with some of their technical decisions, but I wish they could have found a way to make SMS/RCS work.

One thing you need to keep in mind is that if you want an app with strong security, the less code you have, the easier it is to achieve the goal.

By definition, Signal is not going to have bells and whistles and niche features, to keep the codebase lean and easier to avoid security weaknesses.

If you want an app with many features, use Telegram.

(They did however ship emoji reactions in Signal because most people actually like it and the other apps do have it; curiously missing in Telegram).