I asked Signal motivations for SMS removal
3 years ago
Here is their answer:
Hi,
Thank you for your thoughts on the announced SMS removal. The blog post describes all of the biggest factors in making this decision, but I know this is a change that is difficult to adjust to, so I wanted to chime in with some additional info that might give some more context.
1. RCS (Rich Communications Services) is coming, and it doesn’t play well with Signal. I once had a situation when I was sending SMS to one of my friends via Signal, but I wasn’t seeing any of their responses – this was because their app was automatically responding via RCS, which wasn’t delivered to Signal. This is going to continue to get worse, and Signal cannot add RCS support because there’s no RCS API on Android. Honestly, the days of any third-party SMS app are numbered.
2. Proper SMS/MMS support is hard. Signal has to support thousands of devices running dozens of versions of Android. Now multiply that by the hundreds of cell carriers running an inherently bad/buggy protocol, and you’ll start to understand the weird MMS bugs we can run into. And any time spent trying to fix them is time invested in an insecure protocol.
3. SMS/MMS has plenty of its own bugs. Remember that incident a few years ago in which everyone got old Valentine’s SMS messages delivered 9 months later? It was an SMS protocol bug for which some users blamed Signal. Other weird bugs like temporarily-split MMS groups, bad image quality, and the general inability to leave MMS groups are flaws in MMS that also get attributed to us.
4. Spam. My goodness, SMS spam is a real thing, and many people who use Signal cannot tell the difference between SMS spam and Signal messages if both come through Signal. They think we’re responsible for the spam.
5. Finally, Signal having SMS support gives a lot of people the wrong impression of SMS. They think that because SMS is being sent through Signal, it’s actually secure or as secure as an encrypted Signal-to-Signal message, and that’s just not true. We can add unlocked padlock icons to each SMS message, and we can label the message compose box as “insecure”, but the misunderstanding would continue. The only thing we can do is store the SMS messages encrypted on the device, but in my opinion that matters very little when anyone who wants your SMS messages can just get them all from your cell carrier.
In short, SMS is on its way out in general, and in a world where Signal supports SMS, all of SMS shortcomings are often attributed to Signal itself, all while confusing people into thinking their SMS messages are secure.
In my opinion, a secure SMS app does not exist. Just choose the one with the best layout or usability, and preferably one that supports RCS (which I believe at this point are Google and Samsung Messages), because at least then there’s some chance that they might end up being encrypted in the future.
I hope that helps give some more context. And please know that I understand this is difficult to adjust to. I can relate. I’ve used Signal as my SMS app for over 6 years, but I truly think it’s for the best.
I think you're forgetting the main reason: the group of people using it to communicate is really small and shrinking every year.
The only large group of people who still primarily use SMS to communicate person-to-person is Android users in the USA.
Every other country has settled on either Telegram, WeChat, WhatsApp or FB Messenger, or other niche apps. These apps work on both iOS and Android and often also Windows. I haven't sent an SMS in probably 12 years. I don't know anyone who has.
It's only in the US that iMessage is so prevalent that Android users have to use SMS, the only other way of messaging iOS devices. And the US is quickly becoming a de-facto iOS only country. It already has more than 50% market share, even 80% among young people.
With the US going (almost) full iMessage and the rest of the world having already settled on another app there simply no point to supporting SMS.
SMS is still rather common here in Europe. Even if a ton of people use whatsapp and such SMS is often a safe option to initiate with or something trough which you get certain kinds of automated messages like appointment reminders or verification codes.
I think that differs very much per country. The last time I have received an SMS from a human in NL must have been a decade ago. In many European countries, sending SMS was quite expensive, leading to early and very wide adoption of WhatsApp.
22 replies →
I really hope SMS keeps on going - it's as a solid of a protocol as email is - no matter where you are, as long as there is a mobile network, you can send a text message.
2 replies →
Not sure that can be said as a blanket statement for the whole of Europe. In the UK SMS isn't common at all anymore.
13 replies →
I concur, SMS is DEFINITELY still common in Europe. Removing support for SMS would mean all of family will stop using the app now, this is completely silly and US-centric...
Automated messages are pretty much the only thing I get via SMS. Other than the occasional message from my mum who likes to randomly flip between WhatsApp and SMS depending on which way the wind blows.
It's still used in that sense but it's very rarely used for actually sending texts between people.
Basically, SMS used to be a big revenue driver for operators. That business has dried up almost completely. The notion of paying per message is just completely gone. So, operators stopped caring about SMS a long time ago. In the same way, call minutes are increasingly less relevant. It's all about 4G and internet now.
2 replies →
I can only offer a personal anecdote. In Sweden the only SMS messages I receive are marketing spam and appointments from various places (from my hairdresser to dental appointments). Everyone else is either on various messaging apps (FB Messenger, Telegram) or chat apps (Slack, Discord)
What country do live in? I haven’t received an SMS from a human in probably ten years; I live in Europe and everyone uses Signal/WhatsApp
Which countries? It has zero use in the UK (apart from for stuff like parcel deliveries and 2FA). We're 100% WhatsApp.
6 replies →
I send maybe one SMS per year, not every year, when I think a person could be offline or in low signal areas. SMSes get where data don't.
I receive dozens of SMSes from banks with one time passwords for 2FA and payments notifications, from delivery companies to notify me about progresses in my orders plus some spam. It's easier for them to use SMS than anything else because every phone receives SMS right out of the box.
A bit weird for the "I don't use it so who cares" view to take a firm hold here.
SMS is:
1. not controlled by a single company
2. a different network than the internet
3. a fail safe for people who don't use apps or are unable to at a given time for some reason (inc 2fa)
4. a fail safe for a "small group of people" who are suffering the consequences of a natural disaster.
Though perhaps not economically feasible for certain companies, supporting redunancy is as much an honorable goal as privacy.
And totally readable and accessible by any third party
3 replies →
I'm from Europe and use SMS only, I don't get it how having a dozen of messaging apps and remembering who uses what is better than a simple SMS that I can send to absolutely anyone with a phone..
Pretty much this. I only ever send out SMS if I am the one who initiates the conversation on a phone, but other people send me messages on other apps.
However most of my instant messaging is done on a computer using discord, so I might not be in the prime user base of these apps
SMS is still used in France too.
> I don't get it how having a dozen of messaging apps and remembering who uses what is better than a simple SMS
Indeed, especially now that Telegram is taking off by times in Europe (in Belgium / Spain / France at least Telegram is getting used by a lot of people) and that some people now refuse to use WhatsApp.
In addition to appointment reminders from doctor/dentist/notary/whatever and delivery tracking numbers I still exchange SMS with quite some people.
It's not as if it was exactly hard to open and reply to a SMS you just received from someone: takes exactly the same time as answering using WhatsApp or Telegram.
4 replies →
I guess that varies from country to country. In Spain, it's WhatsApp for everybody with Telegram recently making inroads for specific topic groups.
SMS is used by companies to send notifications and asking for confirmation, even (ouch!) banks. I haven't sent one in more than a decade.
Same
>The only large group of people who still primarily use SMS to communicate person-to-person is Android users in the USA.
BS. I visited city I grew up recently, met with a few (9+) people (25-32 years old) and only one of them had WA, most haven't heard about Signal, everyone simply uses SMS. It's simply multiplatform, works with their gradmas and no one wants to install __another__ app to send messages to people. No one cases about RCS that will be used to push QR codes and ads, people will use SMS for its simplicity and reliability. I'll be dropping Signal and moving to WA once Signal drops SMS support.
If you're going to bother migrating and presumably taking people with you, why migrate to another company's proprietary service, rather than an open protocol?
Or (bluntly): why not Matrix (and/or XMPP)? What makes WA so much better that you're willing to go all-in with this company?
2 replies →
but… WA also doesn’t have SMS support?
4 replies →
>Every other country has settled on either Telegram, WeChat, WhatsApp or FB Messenger, or other niche apps. These apps work on both iOS and Android and often also Windows. I haven't sent an SMS in probably 12 years. I don't know anyone who has.
SMS is big in Europe (yes, Europe is not a country. I just mean "dozens of countries in Europe"). All courriers have plans with SMS focus.
I'm on a prepaid plan. I had the maximum plan (unlimited data, unlimited voice) for two decades but with home office, I spend most time indoors so I've switched to a <10% cost prepaid plan which works mostly fine.
Some months my data volume doesn't last till the end of the month. I use SMS instead of the Signal protocol then.
Yes I might be a minority, but if you're not the market leader, cutting out minority groups of users will not make you more successful.
What's your mission: Giving secure communication to everyone or become the next WhatsApp?
Your data is completely switched off when you run out? In Europe it would be illegal to market this tariff as a "flatrate" and typically data plans are just reduced in bandwidth once your volume is used up.
2 replies →
<<It's only in the US that iMessage is so prevalent that Android users have to use SMS, the only other way of messaging iOS devices. And the US is quickly becoming a de-facto iOS only country. It already has more than 50% market share, even 80% among young people.
Do you have any data to back it up? I have trouble believing that, but I am admittedly biased against Apple devices.
> With the US going (almost) full iMessage and the rest of the world having already settled on another app there simply no point to supporting SMS.
I think you just described the core of the problem: Signal has a very US-centric view of the market, and has no clue that SMS is actually still relevant elsewhere, and a low-hanging fruit for capturing user-base.
I have most of my friends using some messenger app and based on that I run―because I basically have to run―Whatsapp and Signal myself. But those are all people I know. What would you use but SMS when contacting people you don't?
Typically, if I try to reach someone but they don't answer I'll follow up with an SMS to explain what I tried to call for. If it's a co-worker, or an acquaintance, I'll send an SMS to make sure they receive my message. SMS is more reliable, doesn't require you to know which apps the other party runs, and it comes through to the recipient as SMS is a basic service in the telecom networks.
When I get to know a new person there's a transition to "oh, you're on $APP too", and I might starting moving non-urgent messages to $APP. But if you don't know the other party well or there's a question of reliability, what is an alternative backbone for messaging if not SMS?
> What would you use but SMS when contacting people you don't?
Here in the UK, whatsapp is the default first try, at least with anyone I've interacted with. The dog groomer even messaged me on whatsapp to tell me dog is ready, completely unprompted.
Where are you getting 80% among young people? A quick google search only returned numbers around 55% among younger people. That's a looong way from a de-facto iOS only country.
Recent thread[0] about it.
0. https://news.ycombinator.com/item?id=33169684
1 reply →
> Every other country
That's obviously not true. I live in a European country where a lot of people are still using SMS.
In Australia, SMS is still fairly widely used for messaging people you're not in usual contact with (to be fair, Facebook Messenger and Instagram are far more popular for communicating in general if you've added each other).
> the group of people using it to communicate is really small and shrinking every year
Group of people using it to communicate might be small, but group of people using SMS to get verification codes, messages from delivery company about scheduled delivery, doctor appointment reminder etc. will be for sure 90% or more phone users at least in Europe
So I find it very stupid to say nobody use SMS, because pretty much EVERYONE use them, just not to communicate with other, but to receive messages and you still need some app to receive these messages. So while I can communicate with almost everyone through Whatsapp I still need to use SMS app almost every day and I'd rather have all my communication consolidated in one app than must switch between apps to check the codes or other stuff, man I wish Whatsapp supported at least receiving SMS, actually I'm pretty sure that would be enough for majority of people which don't really need to compose message.
> Every other country has settled on either Telegram, WeChat, WhatsApp or FB Messenger, or other niche apps. These apps work on both iOS and Android and often also Windows. I haven't sent an SMS in probably 12 years. I don't know anyone who has.
This is a big call. I live in a country where SMS is still standard. Most communication with friends and family is done by it.
Can you please provide a source?
At this point, my entire family, including my 80 old grandmother, use Telegram for communication. I often find myself having to visit her house to show her how to “report spam and leave” random crypto groups she gets added to.
this really speaks to the urgent need of making interoperability legally mandatory for the bigger actors so one isn't socially forced to use one or two applications that are provided by a private actor
The answer doesn't always have to be larger governments and more oversight.
Users can switch to another OS if they really cared that Apple refuses to use industry standards, hamstrings their own mobile browser to bolster app sales, and violates antitrust laws with their ban on third party browser rendering engines.
2 replies →
I'm in the US, have android and use sms a lot, almost entirely to communicate with users of "dumb phones".
In fact, all the ios users I communicate with do it over whatsapp or telegram.
Today I had an ios user sms me asking if he could send me a voice message. I honestly have no idea if that would have worked but I directed him to whatsapp (that he already had installed) and it was frictionless thereafter. I expect I'll never see another sms from him again.
> The only large group of people who still primarily use SMS to communicate person-to-person is Android users in the USA.
This is precisely why RCS and MMS support aren't important. I just need Signal to deliver SMS authentication codes and notifications. For person-to-person communications I'll use Signal protocol.
Don't forget 2FA from shitty European companies! And pizza delivery notifications!
Jokes aside, I see SMS as a useless protocol; because it cannot be used for identification, and neither can anything be encrypted nor verified without another communication channel.
It's also not in the power of the end user to decide whether or not their number gets reassigned, blocked, or does work at all. Most US people seem to think that it's normal to have "one" number for years on end. For the rest of the world, it's not true.
For example: If I don't use my SIM card to make phone calls (which get billed) for 6 months, it's gone and reallocated to a different person.
> Most US people seem to think that it's normal to have "one" number for years on end. For the rest of the world, it's not true.
Uh, I’m from Germany and had the same mobile number for over 20 years.
5 replies →
I'm not sure what you mean about a reassigned number? Do you mean that people risk getting a new number, whether they want it or not? Because that shouldn't be an issue - I believe all of Europe (at least EU) demands that the customer can transfer their number to a new provider or whatever, whenever they want. So maybe you mean something else?
2 replies →
> And the US is quickly becoming a de-facto iOS only country...
I love that "there are two big players in the market with a literally 50%/50% split" means that iOS dominates. iPhones have always been popular among teenagers, if Millennials are any indication it levels out over time. It's just one of many weird demographic splits, not some grand trend. People need to not fall into the fallacy that "something is popular with young people" means that thing will remain popular as they get older.
iOS is more popular among women, young people, liberals, professionals, upper-middle and high-income, people with post-secondary education, and urbanites.
As well as the inverse of the above Android is more popular with people who work in IT, and people who follow tech news.
SMS is still very common in India.
You're forgetting that there's more than just person-to-person SMS.
No I'm not. I receive automated SMS messages all the time. 2FA codes, parcel tracking, my appointment at the dentist reminder etc...
But that's pointless to have inside the Signal app, which is for person-to-person communication. I wouldn't even want those messages in WhatsApp even if it could do it.
1 reply →
SMS was, in my opinion, the killer feature for Signal. Telling people to install yet-another-inbox which was only going to be used by their one privacy-weirdo friend was a non-starter.
Saying "this is a better SMS app" got people on-board and let them "upgrade" to secure messaging. That's why I started using it in the "TextSecure" days.
But, sadly, I agree with Signal's reasoning here. Mixing the two protocols was annoyingly complex. If someone stopped using Signal, messages you sent to them would never arrive - with no notification. And there's no obvious way to "downgrade" to SMS.
I was working on RCS a decade ago. I'm glad to see it is finally getting somewhere - but I'm sad it is at the expense of better and more secure protocols.
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.
3 replies →
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).
3 replies →
As a Dutch person, I'm still amazed that the US still seems to use SMS as much; mind you, our phone plans here were "you get 1000 text messages and X minutes or a bajillion megabytes of data"; that + 'free' international messaging / calls with services like Whatsapp quickly pushed people to data-only messaging like Whatsapp or maybe FB Messenger. We also have a big immigrant population that like to chat with their family wherever they may live, and international calls / text messages are stupid expensive.
I can imagine that's less of an issue in the US; do you pay extra for text messages and calls that go across state lines?
FWIW, I'm not American.
In the UK, where I am, most contracts have unlimited SMS. I think even the cheapest PAYG plans include massive bundles.
Lots of companies send out reminders by SMS because it is universally accepted. Not every customer has WhatsApp.
We do generally pay extra for international calls, though text messaging is often free (assuming you’re talking about international states. US states, of course, are all treated as the same country).
Almost all phone plans have unlimited (domestic) texting and calling and differentiate themselves with data, reliability and ”free” perks like subsidized Netflix. You really have to go out of your way to find a plan with limited texts/calls.
7 replies →
Why are you people always so proud of having all your communication owned by Meta? With Meta dictating which phones you can use to communicate with others?
2 replies →
No, my phone plan in the US was unlimited call and text. So it was either imessage with everyone or text.
I've gotten SMS messages from iPhone users. In some Apple centric areas (rich people or people who think/want to pretend they're rich), I think iMessage is the default.
Fine by me. If they want a better experience, I have almost every messaging app on the Dutch market bridged to my Matrix server so I don't care, they'll just have to live with the lack of features if they want to chat with me (or install something like Signal).
I don't care about RCS and other ISP standards that exist to squeeze more money out of texting. I'll use Telegram/Signal/WhatsApp calling before I'll use my phone app because my subscription doesn't include free minutes (and I barely call anyway) so I've gotten the benefits of tech like WiFi calling through VoLTE for years before ISPs bothered sending their VoLTE profiles to my phone.
Probably because I haven't witnessed the Textsecure days: I didn't even know Signal was doing SMS, until these days. Certainly didn't convince anyone to use Signal by telling them it was a better SMS app. So SMS as killer feature seems to be, at least for my peer group, firmly in the past.
Signal's maneuver may be rational, but that doesn't make it good business. You can't just release a chat app into the wild. You need some strategy for how you will bootstrap users. If you build it they won't come.
Some chat apps bootstrapped by riding emerging markets with exorbitant SMS costs. Others bootstrapped by cross-promotion from existing popular communication networks.
Signal's strategy was to replace your current SMS app as-is and then incentivize you over to their network one contact at a time. It didn't work, for the stated reasons, which honestly sound like failures of product design and engineering more than anything else. Apple's Message app has the same strategy and it's working.
We haven't actually seen what Signal's next strategy will be, which is maybe a timing mistake as announcing a viable alternative could have taken some heat off the SMS retirement announcement. Or maybe there isn't a next strategy?
'The super secure chat network' is not a bootstrap strategy, it's a build it and they won't come strategy; so I think it's fair to remain bearish on Signal's future even after reading a rational take on why writing SMS apps are difficult.
> Apple's Message app has the same strategy
Maybe coming preinstalled on all i-devices helps?
You're right, I guess they're a blend of the cross-promo strategy as well.
This is a fantastic summary.
I once spend several euros sms-ing instead of what I thought was Signal-ing with someone in another country. Since then I keep the two strictly in 2 different apps.
I certainly wont mourn for this. Sms gets super expensive to other countries (outside the EU), it also gets super expensive when you don't pre-pay for a bundle (it's 2 eur for 1000 messages, then 25ct per message after that, ridiculous). Imho dutch carriers did everything they could to kill sms, and now I'm happy for it. The only bad thing is that my society at large seems to have chosen Whatsapp as it's replacement...
I have 2 issues with RCS:
1. Requires data connection, either WiFi or mobile data. SMS does not.
2. On Android, it goes through Google Messages. I don't trust Google.
So, I replaced Messages with another SMS app that doesn't spy on me and disabled RCS. If I wanted to do rich messaging through data connection, I would use Signal or similar.
So, RCS is not a replacement for SMS. It's just another IM protocol. And we have enough of those.
As for others replying through RCS, that's a failure of the messaging app, should recognize that the counterpart is SMS and reply in SMS. It's an attempt to force RCS...
SMS is for fast short messaging between mobile users, and that is its killer feature, it's universal. Every mobile phone supports it.
Signal dropping SMS support makes no difference for me, never used it for SMS, I used Signal for the secure conversations. Two different methods of contact.
"2. On Android, it goes through Google Messages. I don't trust Google.
So, I replaced Messages with another SMS app that doesn't spy on me and disabled RCS. If I wanted to do rich messaging through data connection, I would use Signal or similar."
3rd party SMS apps use a Google provided API to send and receive SMS messages on an operating system provided by Google. I'm not sure how you think using a 3rd party SMS app would be protecting you if Google cared about spying on your messages.
RCS through Google Messages is end to end encrypted while SMS is not, so you haven't eliminated Google in theory spying on your messages but you have assured that your carrier, the recipients carrier and whomever controls the OS and app on the destination device can potentially spy on your messages.
1. True RCS isn't supposed to go through internet, it's supposed to go through same way as SMS and voice calls (which is also a data connection, but specific to sms/rcs/voice)
2. That's not a requirement even though Google does their best to kill all alternative implementations. (Samsung had one, but Google paid them a lot of money to get rid of it. I have to admit I don't know who is left with their own RCS client)
> So, RCS is not a replacement for SMS.
It's 100% a replacement to SMS, it's literally defined in the same spec as SMS over LTE, as an upgrade to SMS. Though yeah Google made it, this... uh... thing. RCS is technically a federated standard, but Google killed every part of the federation and some parts of the standard.
RCS might be a federated standard, but before Google not even Verizon at AT&T wanted to federate.
3 replies →
> So, I replaced Messages with another SMS app that doesn't spy on me and disabled RCS.
I think you know this based on the rest of your post but there is no “another SMS app that doesn’t spy on me”.
Why not? SMS apps no need internet access, so only one spying there can be carrier.
This was posted in the Signal discourse on the same day of the announcement (and linked deep in 630+ comments of the HN post), and I'm glad it's reposted here because it paints a very different picture than the previous blog post.
The hidden gem is that basically Google is taking over control of RCS, and by proxy "text messages". There will only be one Android implementation, and it's Android Messages. It (finally) comes with E2EE messages with something resembling the Signal protocol, but you lose the possibility of writing a custom UX for that, as was possible since Android 1.0. It's particularly ironic during Google's campaign pushing Apple to support RCS.
I haven't looked into the RCS protocol myself but what is preventing others from building their own RCS clients? As I understand the protocol, it's IP based rather than modem based, so external apps should work, right?
As far as I understand it right now its a lack of exposed APIs in Android to access the message stores. I suspect this is something that will be standardized and exposed in a future API revision, but as it stands right now using the official APIs I don't think you're able to make your own...
2 replies →
With Signal moving away from SMS, the required messaging app stack on my phone just to be able to receive everything sent do me will have to be:
- Signal -> Close friends & family I've convinced to use it.
- WhatsApp -> Most of my friends.
- SMS -> School notifications, 2FA, shipping updates, etc.
- Facebook Messenger -> Elderly relatives
- Telegram -> That one relative who wants to use this instead of Signal.
Is there a consolidated messaging app that the HN community recommends?
I can't be the only one suffering from messenger bloat.
I never understood Telegram. It's insecure by default, runs in a different jurisdiction. It's not even anonymous
But somehow people started using it because it was "more secure" than whatsapp.
> I never understood Telegram.
Telegram has amazing user experience. It's available for any platform, the messages are always backed up, the apps are high quality and responsive and they have great features for group messaging and group organization. They even give you a library you can build your own Telegram client with.
It's *great to use* - something that Signal people never prioritized and always rather pushed their sometimes horrible preferences down peoples throats.
Different jurisdiction to what? :)
My UK-based employer seems nonchalant about expecting me to agree to be subject to the laws and courts of California in order to receive internal company newsletters delivered via a 3rd party.
While I agree this is harmful to the user (or unpatriotic, if you prefer), it's extremely common thanks to the state of the global economy since the 1980s.
I'd wager that 99% of people in the UK would now be unable to contact their friends and family without relying on at least 1 large U.S. company.
Signal was late to market, and as much as I hate this in principle, it is unfortunate state of things.
Whatsapp has caught internationally but it's Facebook and its desktop app is a crashing dumpster fire.
Viber is another popular app, but has too many ads and visual noise.
Telegram has caught on as a good alternative for all, because it does everything good. Apps are functional, fast and stable. Interface is clean. Also Telegram channels were genius idea to increasing market penetration. Nowadays all social networks are heavily abused by bot abusing abuse feature (hehe). Basically any post containing "politics" let alone "war" content can be taken down by abuse spam. Be it facebook, twitter or reddit, all the same. So political and social "influencers" are rapidly creating backup or new main channels in the Telegram to post "controversial" information, and people reading news and blogs in Telegram will also message there too.
Anonymous groups are one killer app: you can easily join interest groups without leaking your phone number or other obvious ID (Facebook identity etc).
Of course, it's not really "anonymous" if a nation-state wants to come after you, but that's not the threat model for most people.
1 reply →
telegram doesn't make me share my phonenumber with everyone. i would use signal, but sharing my phone number is a no go.
maybe now that signal is switching off SMS it can implement user handles that people can share instead of their number. once they do i'll give it a try
It has channels, which are a great middle ground between Twitter and Substack.
Telegram is now more to Discord than friends and family messaging app. You use Telegram and Discord similar on how you use Reddit or Hacker News.
> It's insecure by default
Any proof? If you're calling MTProto 2.0 'insecure' then you should know it's already been audited multiple times in the last 2 years. If insecure means not using E2EE, then I guess the whole infrastructure of the internet is insecure.
> It's not even anonymous
It's more anonymous than Signal is. It requires phone number to register but you don't need to share a phone number or any personal detail to communicate with people.
7 replies →
> I never understood Telegram.
A lot of piracy stuff on it.
No, there isn't any, because outside Telegram and SMS, none of those apps really support any APIs or 3rd party clients.
Signal team is also actively hostile to any 3rd party client usage of their service.
And that's always cheered on this website - just remember the RCS topics where people were making fun of attempts to add some basic standardisation to this mess.
> Signal team is also actively hostile to any 3rd party client usage of their service.
"actively" is a big word, there are several 3rd party clients and no big push to make them stop. They don't want widespread 3rd party clients though.
> Is there a consolidated messaging app that the HN community recommends?
I am not HN community, but there is Beeper or Texts.com possibly others, there are also (other) Matrix bridges, but it's PITA to set them on your own.
Personally I'd just move family and (old) relatives to Whatsapp and you will have everything consolidated in one app used by everyone anyway. That one relative would have easy choice, either Whatsapp or SMS if they wanna talk to me, not keeping extra app for one special snowflake.
Plus you need to keep SMS app to receive all those codes, shipping updates since Whatsapp sadly doesn't support SMS.
That's also my setup - Whatsapp+SMS, used to have also Signal years ago with family before we ditched it en masse after PINgate for Whatsapp, my mother has also Facebook, I think father only Whatsapp, sister I don't talk to has also Whatsapp, wife has Whatsapp and (Google) Messages which she use just for receiving SMS.
If I would be moving somewhere my family (parents, wife, kids) I'd go for Element (Matrix) - decentralized network, various apps to choose from, no phone required.
Another alternative but without (video) calls would be using some email app like Delta Chat or Mailtime for instant messaging, that would require no signing up for new service, I like the idea, though I guess messages would be quite slow.
Btw. Messenger and Skype (Lite) supports SMS, so since you use Messenger anyway you could ditch SMS app and Signal after they remove SMS, if you wanna keep more IM apps than having everyone on Whatsapp.
There is some critical mass fortunately. The driver for most people in my group to get it was that they’d miss out on a group chat if they didn’t have it.
I now have everyone I talk to regularly on Signal (30-40 people), but it took years.
I don't think that would work, because then they'd just introduce their own messaging standard.
https://xkcd.com/927/
> the difference is that matrix isn't trying to become the One True Standard, but just glue the others together. @xkcdComic
https://twitter.com/matrixdotorg/status/841424770025545730/p...
1 reply →
Matrix
Matrix has fundamental security problems that they seem unwilling to fix. Almost a polar opposite to Signal.
7 replies →
It is my understanding that this mostly works with rooms/channels over bridges - not with individual, 1-on-1 communication. Do you have a hint how to set this up?
2 replies →
That should have been written into the blog post. Not the current tasteless PR.
This is genuine; the PR messages are for businesses and shareholders; especially for publically traded companies, they have to be Very Careful with what they say in public.
Signal is not a publicly traded company and does not have shareholders; it's a non-profit.
What they said was outrageous, "Google is screwing us and screwing you" would have been received more warmly.
1 reply →
I think this is basically this excellent explanation: https://community.signalusers.org/t/signal-blog-removing-sms...
And their president also commented on it a bit at https://www.theverge.com/23409716/signal-encryption-messagin...
The "there's no RCS API" sounds more like an excuse or at least a pretty shallow take. There is none now. But chances are that there will be an RCS API in the near future.
E.g. EU countries are split between plain SMS and WhatsApp as the preferred messaging platform for automated interactions with services. Google not offering an RCS API would be like pushing everyone to use WhatsApp for automated interactions. Would Google risk that? Probably not.
By pulling the plug from SMS support now, Signal just makes it certain that they will lose user base, no matter what Google does.
And it is also kind of disrespectful to anyone who spent their personal time advocating the use of Signal to friends and family.
> Just choose the one with the best layout or usability
This was Signal for me. I understand the reasons to get rid of SMS support but I strongly disagree. Unfortunately I don't have enough people in my life on Signal to justify keeping it around as yet another messaging app.
I've a loyal signal user since it came out. Seemless SMS fallback is why I used it.
I was hoping to read here someone had forked it here. I won't be continuing with Signal.
Thank you for sharing this; this is very useful context. I wonder if it would have reduced the outcry from their initial blog post if they'd included these examples.
SMS integration is a lost opportunity in so many ways.
I wanted a no-code solution to push my bank-sent SMSs into a real-time transaction database. Apparently this is impossible on iOS, and on Android it's incredibly unreliable (IFTTT & Tasker keep getting shut down by the OS). Fortunately, before writing my own solution, I found messages.google.com/web. I have to scrape this, but that's simpler than maintaining an Android app.
Somehow, it's 2022 and if I want real-time banking information I have to write code to consume SMSs OR hand my banking credentials over to a third party to scrape my bank statements.
Have you tried Twilio or some similar SMS solution that doesn't involve your phone. Admittedly this costs money but potentially you could use a number there to consume everything.
Alternatively if you are in Europe/UK the openbanking API is quite widely used now
Why not scrape your bank directly? For semi-auto I used to use TamperMonkey to help turn a statement into a CSV if the bank didn’t have a download.
This (weirdly) edited copy-paste should be replaced by the source: https://community.signalusers.org/t/signal-blog-removing-sms...
Can someone ELI5 the RCS thing for me? I don't get it...
From the answer and the wikipedia page it sounds like this might be a decision that the other side's client (SIM? carrier?) makes, to reply via RCS.
And my device would be able to receive this only via data connection? Or would my carrier detect that I'm not currently in 4G covered area (middle of Germany for example...) and send the text via regular SMS?
I'm a bit worried by the first point, really. What does that mean for e.g. pinephones or google free android? Do I risk silently missing text messsages?
I think it'll get clearer when you realise that SMS (and MMS) is also nothing more than a "data connection" message that carriers chose to classify as zero-cost and available during roaming via different pricing.
RCS - and VoLTE for example - is in this way no different. It's just a data message that gets sent to a configured endpoint (either on Google or your carriers' servers, depending on your carrier preference).
Of course, the carriers still remain the dumbass link in this chain as usual. I've just had to deal with a carrier that charges VoLTE call configuration setup connection as normal foreign data roaming with minimum pricing. The phone ate through 30EUR of costs despite having mobile data disabled.
When Signal finally drops SMS support, I will also drop Signal. It always was SMS foremost, secure communications second when I initially started using it. Having people on Signal was an added benefit, not the main drive for using it.
For me personally, Signal will turn into a messaging app among dozens of similar apps, of which I have enough already. SMS was why I stuck with Signal over the years I used it and now I have no real reason to stay on it.
I remember when Signal was called Textsecure and did E2E encryption for SMS - just to rant about argument number 5.
They've been fundamentally dishonest in their messaging. The truth is that they don't want to support SMS any more, and they don't care about usability or barriers to entry this causes. If they'd just said that I wouldn't be so annoyed with them.
> Getting someone to sort of clock the difference in a protocol layer security property, that’s an education task that is pretty steep
This is the signal president's stated reasoning on why they couldn't have a blue-message (secure) / green-message (insecure) dynamic, akin to iMessage. I think she is being disingenuous, and that the development effort of MMS is the driving motivation, but I am cynical.
1 reply →
Tangential, but to 1.: Isn't RCS just built upon TCP/IP and SIP? Why can't you just implement it in user space? Or does it need to send some magic packets through the modem? It is really hard to find details on the protocol.
Another problem is that Google's RCS implementation has a Signal-protocol prekeys-exchange server in the loop that is not accessible for the public. So even if you'd implement RCS you could not send messages to android devices as you can't fetch the prekeys through anything but the Messages app.
So sounds like Google pretty much owns the RCS protocol? I know it's meant to be an open standard, but sounds like there's no point in any third party app implementing if it can't send messages to people with Google Messages.
Yes, TCP/ip and SIP, no magic packet, but: 1. You need to do challenges with the SIM card for authentication 2. On most carriers, "ims" is on a special IPv6 data connection that can't be used by apps.
The specifications are public, but yeah it requires a lot of work to get into.
That being said, I think neither of those limitations apply to Google's "RCS" (which bypasses carriers, so they can't get their own IPv6 connection and I don't think they can use SIM challenges for auth), so I think it should be possible in a 3rd party app.
> RCS (Rich Communications Services) is coming
Has there been any new press on this? The last nugget I heard was https://www.android.com/get-the-message/, which didn't really announce any progress.
I think many people don't realize they have it or use it, but if I would send a Message via my default "SMS" App to another Android User they will very likely receive this as an RCS Message.
Besides being available and enabled by default on pretty much all Android phones these days?
FYI, https://silence.im/ An open-source Signal fork dedicated to SMS encryption
This doesn't seem to be in active development sadly
FYI this was linked[0] and discussed on the previous discussion[1] of Signal's decision, and is available to view on their community forums[2].
[0] https://community.signalusers.org/t/signal-blog-removing-sms...
I agree with all the points mentioned. I hope this accelerates the development of signal - especially on desktop where there is still no integrated video player!!
I was amazed to learn, a few days ago, that you can send/receive SMS via Signal. It's like being able to send faxes from google hangouts; unencrypted paid messages just seems completely opposite to what the project stands for.
Which is not to say that I can't see the rationale, but I didn't know and it surprised me.
The next thing I wondered is how much work it is to maintain two entirely separate messaging systems in one app. How much did this drag them down over the years? I agree with you and hope that it can finally get Signal moving forward, there are so many missing features compared to Wire and, especially, Telegram that it is currently a pretty tough sell to move anyone away from Telegram.
Apple seems to maintain iMessage and SMS in one app just fine. Granted, they're a bigger company, but it's hard to say just how large the Messages development team is. It could conceivably be even smaller than Signal's workforce!
Apple's iMessage/SMS handling is a perfect model for how Signal should have approached SMS support: a firm hand of features and UI reinforcing the fact that SMS sucks, but reasonable enough support that you can send and receive SMS/MMS just fine.
Signal having SMS is the only reason for me to use it. The decision was specifically made to insist on people using their phone numbers it's rubbish to demand that and then yank this functionality.
If it doesn't support SMS I have zero reasons to use it I may as well use anything else that had less friction.
I liked your application enough to pay a reoccurring subscription, removing this functionality means I've cancelled my subscription.
I'll say what I said to Edith on twitter:
------------------
This will relegate Signal to niche use.
I don't even know if I will keep it and I've been a booster for years. I'll have to remember which ~5 of my contacts use Signal, and mentally update that list when/if any join?
Can't take on that cognitive load for everyday comms.
-------------------
The cynic in me says this looks more like a marketing/pr technique than an honest answer to an email.
Does it? What would an honest answer look like to you?
One of:
- we don't have the dev resources to keep SMS/MMS working
- with RCS becoming more common and no Google API for RCS, we don't have the ability to fully replace Google Messages any more
- since we can't support SMS/MMS on iOS, we decided to kill the feature for Android users for the sake of maintenance
They shouldn't pull punches and pretend that this feature removal is for the "protection" of users who accidentally send SMS instead of Signal messages. That's a strawman, anyway -- if a user manages to send SMS in the Signal app, it's because the person they're trying to communicate with doesn't have Signal installed... so there inherently isn't a secure communication path. Users who pay per SMS should disable it in the app settings, and you can easily add a popup the first time you send an SMS/the first time you open the app to make that clear.
This is 50% Signal trying to streamline development, 50% Google's push for RCS (and their lack of APIs to build alternative RCS apps on Android). They should be honest about that instead of making up nonsense about misguided users getting confused.
Thanks for mentioning it!
My initial response on it being announced in the Signal app was "Oh no, that's terrible!". Followed by "Meh, all software goes to shit eventually. Now it's Signal's turn". Now I already don't really care anymore.
I have been using Silence [0] as my sms app for a day and don't really miss the Signal sms integration anymore.
What bugs me more is that the text message export from Signal seems incomplete. Oh well, I will get over that as well.
[0] https://silence.im/
(Funnily enough Silence is a fork of Signal for SMS only. I thought it looked quite familiar but just realised it is the case)
Due to MMS/SMS messages getting hung I switched to YAATA for messaging people who do not have Signal. It is unfortunate Google is going to take exclusive control of SMS on Android with this RCS implementation. Just another "baked" in half-assed feature that android will permission wall its users from and support at the minimum level they can get away with. Now SMS can be natively as broken as notifications, face proximity sensors, file management, background service management, power management, and a myriad of other android "features" they refuse to fix.
6. A2P and 10DLC - since allowing sprint and T-Mobile to merge the primary carriers here in the US decided to charge business like signal to continue to have access to the messaging services via monopolies like the campaign registry.
Well I have to congratulate Signal on the thorough response.
I can't remember the last time I got such a response. It's a challenge to get them to respond to complaints
Turning RCS into their own private messaging platform on Android has to be peak Google.
They tried to make a bazillion messenger apps, all of which failed, and now they try to piggyback on an existing standardized protocol but don't expose any APIs for other apps.
> Turning RCS into their own private messaging platform on Android has to be peak Google.
While at the same time pushing this "Apple is bad because green bubble" narrative because Apple doesn't support it. It's somewhat amusing in some ways. Companies (Google or Apple) are never on the consumers side, and yet we fall for it all the time.
> and yet we fall for it all the time
Really? Do "we"? Everyone keeps warning of these issues while getting laughed out of the room. At some point I have to believe that most of society actually actively wants to be screwed over.
1 reply →
> Companies (Google or Apple) are never on the consumers side, and yet we fall for it all the time.
It genuinely surprises me how often the HN crowd falls for it.
I would have expected them to be more aware than the average consumer of how tech companies use lock-in to trap their users.
Perhaps there's a blind spot because lots of HN folks work on projects or for companies that (hope to) use the same tactic?
1 reply →
And for real, who cares about a green bubble? Seems to be the epitome of pettiness
If you need to actually send files etc use another one of a multitude of messaging apps out there including the latest Google TalkMsgChatThing (but it works)
And it's not only on the client side, but also server side. There are carriers who implemented Universal Profile on their own and cannot connect to the ones running Jibe. So much for a federated protocol.
So today it's either Google or Samsung messages and Jibe, otherwise RCS is essentially useless. From what I know Facebook wanted to get on board at some point, I'm not sure why this didn't work out.
The fact Google publicly whining about the iMessage lock-in is pretty rich.