So in the new upcoming major feature update for IOS, Apple is adding RCS support in there messaging app. What are the privacy implications of adopting RCS?
Is there any other apps that have RCS support on Android other than Google's own messaging app?
The reason for my asking is because I was considering migrating my relatives' messaging app to a RCS supported one because they will probably most likely enjoy the extra bandwidth of RCS.
Note, they're already using Signal, Telegram, and WhatsApp for most of their conversations.
My family already uses signal as are default form of communication between each but the point that I forgot to add was for the 1% of conversation. Some of my family member have there own businesses that mostly use email but when we are in the field we use regular SMS/MMS/imessage for quick communication between "us" and the client. At least here we most only use plain SMS or iMessage if applicable is used because most people see messaging apps like Signal, WhatsApp and other third party apps for personal use only.
most people see messaging apps like Signal, WhatsApp and other third party apps for personal use only.
In Europe, businesses, especially small businesses often use WhatsApp, to the point of putting its logo next to their phone number on signs. I wonder what creates the perception where you are that messaging apps are for personal use, not business.
I think using the RCS can raise legal issues if Google/Apple collects the messages, especially if you're in the EU. I don't remember how RCS works and I heard it can be E2E encrypted but seeing the comments makes me less sure about the safety of using it in a business environment. SMS isn't encrypted at all and easy to intercept but there's less chance of it being automatically collected for marketing purposes.
Using apps is better tbh unless you make your own apps to create more bloat and fragmentation. Here where I live nobody uses SMS anymore.
Here's the problem, RCS isn't a truly open thing and Google kind of maintains a lot of the software that even carriers use for it. It essentially opens the door for the tech companies to take over yet another big chunk of the carrier services and tap into more user's data at the network level.
In June 2019, Google announced that it would begin to deploy RCS on an opt-in basis via the Messages app, with service compliant with the Universal Profile and hosted by Google rather than the user's carrier, if the carrier does not provide RCS
In October 2019, the four major U.S. carriers announced an agreement to form the Cross-Carrier Messaging Initiative (CCMI) to jointly implement RCS using a newly developed app. This service was to be compatible with the Universal Profile.[33] However, this carrier-made app never came to fruition. By 2021, both T-Mobile and AT&T signed deals with Google to adopt Google's Messages app.[34][35][36] In 2023, T-Mobile and AT&T agreed to use Google Jibe to implement RCS services, and in 2024 Verizon agreed to use Google Jibe.
Apple stated it will not support Google's end-to-end encryption extension over RCS, but would work with GSMA to create an RCS encryption standard.
Why do I need another shitty messaging app that's tied to my phone number, in the 21st century, when I've had proper hardware-independent network-based, cross-platform, messaging apps on my phone since 2009?
What are the privacy implications of adopting RCS?
When it first came out, I specifically remember that trying to turn it on in the messages app makes you agree to hand over all your messages to google, so I never used it. But now it just seems to support it anyways, so not sure what happened to the agreement I never clicked on.
You’ve likely accepted it without knowing, or at least been registered as accepting. Google are using dark patterns all over android to get away with this sort of thing.
I'm fairly sure the only reason for which Apple is using RCS is to circumvent the EU DSA, which requires them to make iMessage interoperable with other chat systems. So instead of opening access to iMessage they're using a completely different system as a distraction.
I mean, they could've said that iMessage is already interoperable via SMS but the feature disparity is too large. RCS will serve nicely to confuse the issue.
There's otherwise nothing to gain for Apple by adopting RCS. iMessage already does everything RCS does and more.
They could also kill RCS tomorrow if they wanted to, by simply releasing iMessage for Android. But then they wouldn't have a red herring to show the EU — if anything they'd be in an even worse position as per DSA. It would also antagonize Google although I'm not sure how much they care about that.
With the higher character limits you can just PGP encrypt your text outside of the message client and send the encrypted block via RCS or literally any other secure or insecure band you want.
RCS is just SMS experience through Google's servers, just like what you have with iMessage. It may even be worse in term of what the companies extracts from your messages. Only usage I could see is if you want to use a matrix bridge that only works with RCS, like Beeper (since Apple does not enjoy users signing in with the iMessage bridge)
Oher than that, I enjoyed RCS messages when I was a Google fanboi and did not care about privacy. It still offers a better "security" than regular SMS, but you chose to deliver your texts to Google
It will go through Google servers if you want to talk to an Android user... If Apple implemented RCS only for its own users there wouldn't be much point to it. 🙂
Encrypted XMPP/IRC+ZNC/other plain text protocol is the best. Mobile data is everywhere and cheap, especially for text messages. Only one person has to do the heavy lifting setting up the server on a VPS with encryption; connecting the clients is easy. The hard part is getting people to use them when network providers and Android/iOS devs shoehorn SMS/MMS/RCS as the default and only option.