Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I am excited for Apple to support this future RCS update in 2029.

You may not be far off - 1st a E2EE implementation has to be agreed upon (Google is offering its own I'm guessing) and ratified into the current RCS standard. And there may be some countries who use RCS that may not want such a thing in the standard, like that country where much of our stuff is made. So it could be a good while before it makes it into the RCS standard with a bit of an if on that.

Guessing once it makes it into the standard we'll see Apple add support on its next .0 release, but we'll see.

WhatsApp belongs to Zuckerberg. You can’t trust them.
Well, it does use Signal's E2EE encryption method - so your message contents are almost certainly private. But you can trust Facebook / Meta / Zuck to data harvest who you contacted, when you contacted them and lets throw location in there too. But for alot of users and most of the world (where its WhatsApp or Facebook Messenger as the primary messaging app for the whole country), that's okay with them.
 
Last edited:
You may not be far off - 1st a E2EE implementation has to be agreed upon (Google is offering its own I'm guessing) and ratified into the current RCS standard. And there may be some countries who use RCS that may not want such a thing in the standard, like that country where much of our stuff is made. So it could be a good while before it makes it into the RCS standard with a bit of an if on that.

Guessing once it makes it into the standard we'll see Apple add support on its next .0 release, but we'll see.

I hope we get RCS 2.7 support at least in iOS 19

I am bummed we didn’t get in line replies or rcs reactions in this release.
 
Please, SMS isn't E2EE either.

Apple just didn't want to because they're scummy, they love that Americans bully people over green bubbles.

China thankfully told them to get with the world or go home.
if someone is bullying you about the color of your bubbles, should you be messaging them in the first place? :rolleyes:
 
  • Like
Reactions: 4ppleJack
Yes and what's worse, Google is also effectively a gatekeeper for many. RCS only works on Google Messages. Use Textra or anything else and it just doesn't do it, apparently because it's a private API and Google doesn't let anyone use it.

And on their own Google Fi MVNO they have failed to provide Apple with the carrier bundle to enable RCS, so it still doesn't work on iPhone.
Wrong. Google has provided Apple with the needed bundle. It's Apple who has yet to get around to employing it.
 
You may not be far off - 1st a E2EE implementation has to be agreed upon (Google is offering its own I'm guessing) and ratified into the current RCS standard. And there may be some countries who use RCS that may not want such a thing in the standard, like that country where much of our stuff is made. So it could be a good while before it makes it into the RCS standard with a bit of an if on that.

Guessing once it makes it into the standard we'll see Apple add support on its next .0 release, but we'll see.


Well, it does use Signal's E2EE encryption method - so your message contents are almost certainly private. But you can trust Facebook / Meta / Zuck to data harvest who you contacted, when you contacted them and lets throw location in there too. But for alot of users and most of the world (where its WhatsApp or Facebook Messenger as the primary messaging app for the whole country), that's okay with them.
Google has already stated what E2EE implementation they are currently working with GSMA for a standard, and which will work cross-platform, securely and privately. So what is this method Google has into facilitate the first cross-platform E2EE, so that an iPhone sharing texts with an Android one will be just as secure and private as with native iMessage or Google Messages? It's not Signal, or some unique Google creation.

Message Layer Security (MLS). This was discussed months ago, so it's not new.
 
Wrong. Google has provided Apple with the needed bundle. It's Apple who has yet to get around to employing it.

You're sure? There's a lot of finger pointing going every which way. Regardless of whose actual fault it is, looks like it won't be happening until at least 18.1.

Last I checked Google says Apple has to support it, Apple says the network operator has to support it. I haven't seen any updates as to who has the ball in their court at this point.
 
You're sure? There's a lot of finger pointing going every which way. Regardless of whose actual fault it is, looks like it won't be happening until at least 18.1.

Last I checked Google says Apple has to support it, Apple says the network operator has to support it. I haven't seen any updates as to who has the ball in their court at this point.
Google tells us that “only Apple has the ability to enable RCS interoperability for iPhone users on Fi.” The Google MVNO has done all the necessary work to support iPhone RCS on its end.
 
The question is going to be: will it be like iMessage where the keys are on device OR will it be like other systems where someone else holds the keys? (Some is better than nothing, but the devil is in the details).
End to End Encryption (E2EE) means: keys generated at call time on communicating phones as a result of their authentication. Not generated/stored/retrieved on any server. Some devils in the details:
- what is not encrypted or server/vendor-encrypted (metadata, keystrokes, drafts, autoscreenshots...) can and will be read by agencies
- background processes such as sync with devices or cloud if using non-E2EE (e.g. encrypted with server key) => read
- protocol backdoors (like Apple quietly inviting agencies in all group discussions as was disclosed last year) => read
- crypto backdoors (like RNG info or related encryption keys, weak key agreement parameters...) => read
However, if correctly done, Apple servers are unable to decrypt E2EE conversations, so it's very good security.
 
If only the NSA didn’t have on screen viewing tech … think your eyes are the only ones looking at your screen … guess again
 
Google tells us that “only Apple has the ability to enable RCS interoperability for iPhone users on Fi.” The Google MVNO has done all the necessary work to support iPhone RCS on its end.

I can’t find a quote on whether Google or Apple has confirmed that Google has actually done their part. They also lacked 5G support on iPhones forever. Not sure whose fault that was either.
 
Apple’s been finally forced to take it’s head out of its fat ass by the European Union and implement RCS into it’s main messaging app so anyone without an iPhone / iMessage doesn’t get the finger or ridiculous green bubble when they text you or text within a group of other people all on iMessage.

One step closer to ending the annoying AF snobbery from iPhone users. THANK GOD.
 
Apple’s been finally forced to take it’s head out of its fat ass by the European Union and implement RCS into it’s main messaging app so anyone without an iPhone / iMessage doesn’t get the finger or ridiculous green bubble when they text you or text within a group of other people all on iMessage.

One step closer to ending the annoying AF snobbery from iPhone users. THANK GOD.
I keep seeing that repeated, it wasn’t the EU, it was China that forced Apple’s hand. When China says jump Apple says how high? None of this waffling around like with the EU. Is it because China can basically shut them down overnight? Pretty much
 
Sure. But you need to agree to Meta's terms to use it.
A decentralized system like RCS is superior, IMO, but it's probably way too late.


I don't know about the world, but the US probably should stop issuing "regional" phone numbers to cell phones. In other countries you can keep your cell number for life.
I've had my cell phone number since the '80s. I've had it in multiple states, and with multiple carriers. Dunno who told you that you couldn't.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.