Live data from Hacker News

Removing SMS support from Signal Android (soon)

signal.org

171–180 of 649 posts

Re: Removing SMS support from Signal Android (soon)

#171
> The most important reason for us to remove SMS support from Android is that plaintext SMS messages are inherently insecure.

This is an incredibly bad reason to remove SMS support. Sure, the fact "plaintext SMS messages are inherently insecure" is true, but the implication is not "remove SMS support".

Most people are motivated strongly by convenience. Signal is convenient because of its use as a drop-in replacement for your existing SMS client, so people use it, which increases their personal privacy and security. Removing SMS support will directly and substantially reduce Signal usage, and therefore both of those things.

The solution to "SMS is insecure" is pretty obviously "make a warning message telling users that", which also solves their second problem:

> This brings us to our second reason: we’ve heard repeatedly from people who’ve been hit with high messaging fees after assuming that the SMS messages they were sending were Signal messages, only to find out that they were using SMS, and being charged by their telecom provider.

...and the third problem:

> Third, there are serious UX and design implications to inviting SMS messages to live beside Signal messages in the Signal interface.

This is ridiculous. You're not making a paid product where if your app doesn't look perfect people won't use it - you're making a messaging app, and slightly ugly workarounds are perfectly OK.

> It’s important that people don’t mistake SMS messages sent or received via the Signal interface as secure and private when in fact they are not.

THEN DESIGN THE APP THAT WAY. IT'S NOT THAT HARD.

This post is a travesty, and the reasoning contained inside is completely insane.

Wikipedia says that Moxie is still on the Signal Board of Directors, but I find it hard to believe that he would let something this crazy go through.

Re: Removing SMS support from Signal Android (soon)

#172
post #29

I feel like all these messaging applications eventually mess up somehow. The one I keep coming back to is Telegram.

You do realise Telegram isn’t secure (non-e2ee), is Russian owned and is based in the Middle East. Enjoy whatever privacy that provides.

Mmm... You can use end-to-end encryption with Telegram if security is your main concern. I don't see how it being "Russian owned" is of any concern, but if you feel like privacy is an issue then you're free to claim their $300,000 prize at stake or just take part of their ongoing bug bounty programme and be rewarded by spotting flaws.

Re: Removing SMS support from Signal Android (soon)

#173
post #128

This is an awful decision. I've converted some friends and family to Signal over the past years (it took a while) and it is now their default messaging app on their phones. This is going to confuse them and is going to make it difficult for me to keep convincing them that Signal is the route to use. ("Why do I need 3 apps (Android Messages, Signal, Whatsapp) to talk to people?")

I use Silence. It hasn't been updated in a while, but I like the way it looks. I don't know anybody else who uses Silence so I could exchange encrypted messages with them. Oh well. Maybe somebody here could resurrect this? https://f-droid.org/en/packages/org.smssecure.smssecure/ https://git.silence.dev/Silence/Silence-Android/

Yea this is super cool

Re: Removing SMS support from Signal Android (soon)

#175
First, I detest this. As an iOS user it’s annoying to have another messaging app and I’m sure many android users will stop using signal. One day I converted my whole extended family to signal by just installing signal on their android phones. Done, no change for them in their user flow.

That said, I also want to use signal without my phone. Things like usernames would be great.

That said, part of me thinks that’s an engineering problem, not a UX problem. Why are engineering problems being pushed into the UX requirements?

Re: Removing SMS support from Signal Android (soon)

#176
It was obvious this was going to happen when they refused to implement RCS.

So instead of working on RCS, we got mobilecoin, stickers, gif search, and now yank out legacy SMS support so more "features" can be developed?

As an early adopter of TextSecure, through CyanogenMod integration, to Signal and everything in between, I have the t-shirts and all -- I am done with Signal.

Re: Removing SMS support from Signal Android (soon)

#177

This is bizarre. If this were an in-depth announcement with a long and well-structured technical justification attached, I could understand. Though I suspect I'd likely disagree with the decision, I could probably accept it as a simple different of opinion if the arguments were evidently well-thought-through and considered. This blog-post is so lightweight. There's no technical analysis. There's barely any justificat…

The answer is this: They dont want to add RCS support or spend the time to do it. It's all bullshit top to bottom.

Google also restricts their specific flavor of RCS (or at least they did awhile ago). I wanted to keep using Textra SMS but they never let Textra into RCS land.

Re: Removing SMS support from Signal Android (soon)

#178

This is bizarre. If this were an in-depth announcement with a long and well-structured technical justification attached, I could understand. Though I suspect I'd likely disagree with the decision, I could probably accept it as a simple different of opinion if the arguments were evidently well-thought-through and considered. This blog-post is so lightweight. There's no technical analysis. There's barely any justificat…

The answer is this: They dont want to add RCS support or spend the time to do it. It's all bullshit top to bottom.

If they said that up top I think many more people would be accepting of it.

Re: Removing SMS support from Signal Android (soon)

#179
> The most important reason for us to remove SMS support from Android is that plaintext SMS messages are inherently insecure. They leak sensitive metadata and place your data in the hands of telecommunications companies.

Ok I get that on Android the situation is such that, as a message provider, you don't give away "metadata" ie who is texting whom, keeping that data either for yourself or the highest bidder. WhatsApp, too, fuss about e2e encryption while conveniently not talking about the value of "metadata" for ad targeting and even want to aggressively grab and upload your contacts at every turn (despite it being illegal in EU to share PII without explicit and documented and revocable consent of all individual phone number holders stored in your phone book). But why does this change come only on Android? Would it be suicidal for signal to drop SMS/MMS when the default messaging app (iMessage) does fall back to SMS/MMS on iOS as is well known?

Re: Removing SMS support from Signal Android (soon)

#180

This is an awful decision. I've converted some friends and family to Signal over the past years (it took a while) and it is now their default messaging app on their phones. This is going to confuse them and is going to make it difficult for me to keep convincing them that Signal is the route to use. ("Why do I need 3 apps (Android Messages, Signal, Whatsapp) to talk to people?")

Why three tho? Use one – Telegram.
Post reply on HN