Ah yes, RCS, the project by big carriers to wrestle back control of the text messaging from the separate / secure / innovative over-the-top apps. No, thank you.
I don't understand this. From a network communication point of view, it doesn't matter. Can you give an example?
Read my post, when you have a 89 year old grand father that can barely work the phone and now introduce a new app is pretty much impossible not to mention some people just don’t want to hassle with using multiple messaging apps.
There lies one of the problems, Google shouldn't be running with the ball. Instead, the GSMA really should be implementing a lot of these feature into the standard (including securing the protocol).RCS and Google RCS are not the same thing, the latter is not official nor is it a standard, official RCS is not encrypted
The person with the substandard product is the Lagdroid user.>implying you would want to talk to a lagdroid loser
How is admitting you have a substandard product and begging other people stoop to your level to make something work convincing??
I'm more concerned about why a massive advertising agency, whose entire business model is mining data off of their sheep... wants Apple to use their sponsored messaging platform...It is bad for the consumer when large corporations like Apple refuse such a simple fix in the name of profits. Do I blame them? I can't say that I do, it makes sense that Apple doesn't have any interest in fixing texting. But at the same time, I can't get behind something that ultimately only hurts the consumer, and this does.
Texting iOS to Android is horrible but it doesn't have to be that way, and it shouldn't.
This is why we can't have nice things 😢The person with the substandard product is the Lagdroid user.
Why should I want to hear from them?
I'm more concerned about why a massive advertising agency, whose entire business model is mining data off of their sheep... wants Apple to use their sponsored messaging platform...
Sounds like a ginormous predator scheme.
This behaviour you see is common across all E2EE services, because both ends need to negotiate keys before sending. So if network connection is spotty, negotiation fails and it will have to try again.I don't know about transitioning between WiFi and cellular networks, but I have noticed that iMessage is more finicky about sending a message when there's initially poor reception.
My coverage in parts of my garden, both my own WiFi and cellular coverage, is quite poor. Quite often I'll try to send a message only to realise that it's not going out, so I'll move to where I have better reception.
On Signal and WhatsApp that usually, but not always, does the trick and the message sends almost immediately. iMessage, on the other hand, quite regularly refuses to acknowledge that the situation has changed and the blue bar at the top will take forever to move across the screen, only for the message to still fail to send. Sometimes it will send on the second try, sometimes I have to completely close the Messages app and start over.
I have SMS fallback disabled because I don't want to use it (cost for international messages, poor media quality).
It's not a dealbreaker, but I've definitely seen it happen a lot.
Google wants to make the messaging experience between Android devices and iOS devices "better" (i.e., better or more appealing for Android users). However, Apple supporting RCS doesn't mean iMessage has to go away or be replaced by Google Messages.
![]()
iMessage and RCS: An unlikely pair we all want to see
iMessage is pretty great, there’s no denying that, but adding RCS support to the app would make a better user...9to5mac.com
This behaviour you see is common across all E2EE services, because both ends need to negotiate keys before sending. So if network connection is spotty, negotiation fails and it will have to try again.
Edit: This is why for websites that does 2-way SSL, it takes longer, because both ends need to negotiate keys before secure communication can start.
I think it’s more that Google has realized that they’ve sat back and let other messaging services take over the world. They know it could have been them. Anyone with a network of contacts already set up on WhatsApp (or LINE, or WeChat, in and out of country) aren’t going to switch to a Google RCS service which may cause SOME of their contacts to be charged to receive the message (or not be able to receive the message at all as it doesn’t fallback to SMS). The ONLY country where non-carrier based methods aren’t the defacto standard is the US. Thus, this is ALL about a last ditch effort to try to obtain some relevancy before Android users in the US drop Google Messages and also use one of the world’s leading communication services.Which is also why Apple is so terrified, I think, to even open up a tiny because by now they've built this system that holds some (primarily US-based) users in the ecosystem. It's also why Google keeps pushing, because removing a barrier to move to Android obviously helps them.
Then Apple should release iMessage on Android.RCS is security issue waiting to happen.
![]()
How RCS exposes mobile users to hackers
Discover how the implementation of Rich Communication Services (RCS) could expose mobile users to hackers, and the security risks associated with RCS deployments.www.autobahn-security.com
And this is why Apple never implemented, and never will. iMessage is still super encrypted and is the gold standard for encrypted messaging.
…. security by Google.
Not gonna happen. That’s also another huge security risk Apple doesn’t want to happen.Then Apple should release iMessage on Android.
We pay a premium for Apple products and Apple exposes us to insecure messaging with Android users. Why? Because they hope to use us to convert Android users to iPhone users. We pay a premium, but we are also part of the product.
I think it’s more that Google has realized that they’ve sat back and let other messaging services take over the world. They know it could have been them. Anyone with a network of contacts already set up on WhatsApp (or LINE, or WeChat, in and out of country) aren’t going to switch to a Google RCS service which may cause SOME of their contacts to be charged to receive the message (or not be able to receive the message at all as it doesn’t fallback to SMS). The ONLY country where non-carrier based methods aren’t the defacto standard is the US. Thus, this is ALL about a last ditch effort to try to obtain some relevancy before Android users in the US drop Google Messages and also use one of the world’s leading communication services.
[...] Apple’s not terrified, they just literally don’t care to help Google in their effort to obtain some messaging relevancy. Every US Android user that switches to Signal or Telegram or WhatsApp, though, scares Google tremendously. And, I’m sure that Google has internal metrics that show how many folks Google Messaging activities are dropping off.
with the exception of group messages. The only thing I could find is that group message E2EE is in beta
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.RCS and Google RCS are not the same thing, the latter is not official nor is it a standard, official RCS is not encrypted
Quite possibly, I didn’t ask and couldn’t really see since it was still set up for Covid protection. It could have been a service like the one you mentioned, I have seen that some businesses use those and some that just have a cell phone or cellular tablet that they use. I have had similar instances with standard cell carriers though tooI wonder if it is a failure of the carrier network... or a failure of the dentist's cloud-based messaging service or whatever.
I'm guessing your dentist is using some sort of messaging service like Podium. I doubt the dentist office is texting on an actual smartphones. (but I could be wrong)
🤔
Correct, the “default” RCS protocol is client to server encryption. Problem is that’s hardly any more secure than SMS. The carrier/service whose RCS protocol you are using has the keys since it is client to server. Basically no different than it is now the only different is your neighbor can’t just intercept your texts. So just how it is now a simple request of phone records will still give info just as SMS.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.
The RCS protocol is encrypted in transit.