this post was submitted on 15 Jul 2023
342 points (99.4% liked)
Technology
3 readers
7 users here now
Talk about anything tech related!
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Dropping SMS alas was necessary (and not just for Signal, but for messengers-with-SMS as well) because of the general play Google is doing with SMS → RCS. IMO, Signal held the idiot ball quite strongly by not just picking TextSecure from their old archives, tuning it up and releasing it as an updated, separate "Signal SMS" app.
I feel like they could've just put text messages in one tab and Signal messages in another tab. Like, iirc, their whole deal was that they were opposed to potentially misleading people about text messages being secure just because they were being sent through Signal.
I seem to remember something like that was discussed at some point in Signal Community and one of the big arguments contra was that the normies and even some advanced people who use Signal just don't "get" UX warnings any more: you could have put all the red tabs, cross signs and unlocked padlocks on the screen you wanted, they were still gonna complain openly on the internet and discredit Signal for not actually "securing muh messages". It's actually part of the same argument why they don't let you export your own messages.
Besides, having to use the same engine (tab and all) in the same app for two things with vastly different reaches of security was murder on the dev team. There were things they were not able to keep testing because of clashing against SMS compat. It is one of the reasons why I think the smart thing to have done would have to keep the "original" app as the Signal SMS.