I care. I even put in a feature request for it.Most Apple users don't care about RCS. Run a poll here and see how that works out for you. Texting works good enough with Android and that 70% market share is mostly overseas.
I care. I even put in a feature request for it.Most Apple users don't care about RCS. Run a poll here and see how that works out for you. Texting works good enough with Android and that 70% market share is mostly overseas.
you are assuming most people use SMS they don't, they just use WhatsApp, signal or telegram its secure?? They still don't have secure text when sending to anything other than an Apple product. It's defaults back to SMS/MMS, which is definitely not secure.
Google wants iOS to have RCS to make their advertising business prosper. Have a worldwide customer base. I’m glad iPhone doesn’t support RCS. I don’t want ads.don’t really care, text message spam ads are worse with RCS btw.
I doubt iPhone-using Americans keep a separate app for their few friends who have Android. Americans, the target of Google's ads and the main users of iMessage. So yes, most people who fit this criterion do use SMS when iMessage isn't supported.you are assuming most people use SMS they don't, they just use WhatsApp, signal or telegram its secure
RCS is just the protocol, I believe you can support a subset of it in such a way that ads aren't supported.Google wants iOS to have RCS to make their advertising business prosper. Have a worldwide customer base. I’m glad iPhone doesn’t support RCS. I don’t want ads.
Have a read :
![]()
I enabled RCS on Google Messages and all I got was ads (Update: Google responds)
If ads have started to appear in your Google Messages app, you're not alone. The RCS messaging standard may be responsible.www.androidauthority.com
![]()
RCS Business Messaging | Google for Developers
Bring branded, interactive mobile experiences to the default messaging app with Rich Communication Services (RCS).developers.google.com
True, though I think it was considered the first "home computer", ie reasonable size/accessibility/affordability?There were lots of computers before Altair, some even as small as a home built Altair machine. (but most were much bigger.![]()
WhatsApp is owned by Facebook. Never trust your data with Facebook, EVEN IF ITS ENCRYPTED.Clearly you don't know what the term "gold standard" means. Signal is the gold standard, followed by Telegram, followed by WhatsApp.
And frankly, as mentioned above, most folk outside the U.S. do not use iMessage or, frankly, SMS in general. My European friends all use WhatsApp and look on us as being backward af.
It's a strong assumption where I live, the U.S., we all do.you are assuming most people use SMS they don't, they just use WhatsApp, signal or telegram its secure
Mostly true, but there were a couple of kits to make your own 8008 processor computer before the Altair. It was the first that sold a lot though! I was working on DEC machines in high school when that stuff came about.True, though I think it was considered the first "home computer", ie reasonable size/accessibility/affordability?
It‘s standard TLS encryption. What‘s there to provide a source for? It‘s been the norm for decades and you‘re using it right now with this website (secure connection as indicated by https in the URL and a valid certificate). It‘s nothing special but it makes sure that only the client and the server know the content of messages, something SMS/MMS doesn‘t have.i believe they want a source for the information
if you can't provide a source why bother even postingIt‘s standard TLS encryption. What‘s there to provide a source for? It‘s been the norm for decades and you‘re using it right now with this website (secure connection as indicated by https in the URL and a valid certificate). It‘s nothing special but it makes sure that only the client and the server know the content of messages, something SMS/MMS doesn‘t have.
…..
Literally standard encrypted connections, like this website works… ?
the fact you want to limit yourself is your problemWhatsApp is owned by Facebook. Never trust your data with Facebook, EVEN IF ITS ENCRYPTED.
Telegram, well let’s just say some certain government might be able to spy on users, even with the claim that it’s encrypted.
Signal is okay. But still not as super encrypted as how Apple does iMessage.
Apple stays at middle ground in terms of messages with iMessage.
If I'm not wrong, the GSMA standards mandates secure channel for cellular transmission between device to cell tower. If that's the case, SMS/MMS are sent via secure channels to your provider's network, like TLS. And I believe most tower will send data via VPNs back to the service provider's data center.The RCS protocol is encrypted in transit. Do you know what that means? It‘s a secure transaction between a client and a server, something SMS/MMS does not have.
Encrypted in transit is not the same as end to end encryption and it doesn‘t have to be, they are different levels of protection. End to end encryption is the icing on the cake but I‘d rather take transit encryption over no encryption at all.
No but they care about videos of grand children. RCS is not just about emojis.Do 89 year old grandfathers that can barely work the phone care about higher resolution photos and cross platform emoji reactions?
Didn't know we had GSM standard experts like yourself on the forums, apologiesAhem ‘that improves upon the current SMS experience’.
Why is so many people here talking tech advancements yet unsure how to properly use the legacy terms ?! I’m t should be MMS not sms as the latter does not support rich text.
iMessage is fine if it does all that you need but for a lot of people it doesn't which is why unfortunately messaging apps like WhatsApp, and the likes, are vastly more popular.Apple stays at middle ground in terms of messages with iMessage.
if you can't provide a source why bother even posting
I believe not for messaging, but correct me if I am wrong.
My comment was basically intended to say: Is the message encrypted on transit from the device to Google’s RCS servers? I think that the answer is no, and in any case Google has the slurping and data collection keys. Hooda thunk it?
If I'm not wrong, the GSMA standards mandates secure channel for cellular transmission between device to cell tower. If that's the case, SMS/MMS are sent via secure channels to your provider's network, like TLS. And I believe most tower will send data via VPNs back to the service provider's data center.
You know that most TLS implementation stops are the web-server right, due to performance reasons? After that, all data are sent in the clear within the data center network.
So in essence, there is no difference in terms of security between SMS/MMS and RCS (the non-Google version.)
Happy to be corrected tho.
Chat features by Google uses Transport Layer Security (TLS) encryption to protect your messages. This means that anyone trying to intercept your messages between you and Google would only be able to see encrypted, unreadable text.
So, an android user recently shared a video with me of their kid taking their first steps. I’m sure that it would have been sent to the grandparents, too. Now, while I couldn’t see the texture of the cloth that the kid was wearing and I couldn’t see the taste buds on their tongue sticking out of their smiling face, and, no, I couldn’t very clearly see the grain on the wood they were walking on, I’m pretty sure that anyone that received the video would not only clearly know what it was, but it would also have the expected emotional impact. Current tech provides that quite well.No but they care about videos of grand children. RCS is not just about emojis.
Google RCS is NOT RCS and the point someone made was about RCS not Google RCSHow RCS chats keep your conversations secure - Google Messages
RCS chats let you send messages over mobile data and Wi-Fi, share files and high-resolution photos, show you when someone is typing, and show you when messages are read. When you use RCS chats, yoursupport.google.com
Entry „How we protect your data“
But Google is the only one really the only one really working on theirs. Last I checked I think Samsung is too, but it certainly doesn't seem to be a priority for any of the businesses except Google. Google wants their protocol to be used or else why spend the millions on advertising that they have done? Hint: Because if they get their way Google will make far more.RCS is just the protocol, I believe you can support a subset of it in such a way that ads aren't supported.
Didn't know we had GSM standard experts like yourself on the forums, apologies
Either way, you know what i meant so the point still stands.
iMessage is fine if it does all that you need but for a lot of people it doesn't which is why unfortunately messaging apps like WhatsApp, and the likes, are vastly more popular.
Also why a cross-platform (there's more mobile OS's than Android and iOS) standardised "rich" messaging protocol isn't a bad shout but it needs to be the GSMA running the show not a single vendor/network etc.
I didn't say as opposed to anyone. Nor did I make any comparison.As opposed to who ?
Google ? Google makes over 90% of its profits from advertising and that requires them to be able to "target" adverts, and they do that by tracking you, tracking your information, and selling that information.
Google has been found to illegally track children, do end runs around "do not track" choices, etc etc.
This is why you can not delete email from gmail, they get "archived", ie google gets to snoop over all your past activity too.
The only company that is worse than Google is Facebook
I figured it‘d be easier to digest for the vast majority of armchair devs in this topic, but okay…Google RCS is NOT RCS and the point someone made was about RCS not Google RCS
16.3.3 Encryption
The User Network Interface transactions should be always encrypted to prevent eavesdropping of the user’s personal communication in the various access and transit networks. RCS makes use of the common encryption protocols, i.e. Transport Layer Security and IPsec. Clients conforming to the profile defined in this document shall support the encryption for all signalling and media traffic technologies described in this document.
There is a difference when the spec is written as "should" instead of "must". Anyway, the transport channel should be secured, e.g. with TLS 1.2 at a minimum or other protocols, now compared to previously, where CPU overhead for encryption is comparitively higher.I figured it‘d be easier to digest for the vast majority of armchair devs in this topic, but okay…
As defined by the Universal Profile (version 2.5 from 16th October 2020, the last version I bothered downloading). Feel free to sign up and download the most recent whitepaper on the gsma site yourself: https://www.gsma.com/futurenetworks/rcs/universal-profile/