Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I sometimes delete random green bubbles and say I never got them which pisses off android users and they blame their carrier. 🤣
That's some deep dedication to the brand there, big shooter. I sure hope Apple rewards you well for your service, because it would be pretty sad to see you willingly sabotage your own social life to carry water for a trillion-dollar corporation that doesn't even know or care that you exist and for you to receive nothing in return.
 
Rich communication🤣 there’s nothing rich about it. It’s garbage.🙀 very limited in sending capability.
 
If my memory serves me right. I think one of the major reasons Apple didn’t want to do RCS was the lack of E2EE. Yet, large countries that don’t care about E2EE wanted it and forced Apple’s hand.
 
If my memory serves me right. I think one of the major reasons Apple didn’t want to do RCS was the lack of E2EE. Yet, large countries that don’t care about E2EE wanted it and forced Apple’s hand.
That was Apple's position, but it was an obvious lie: SMS isn't encrypted either. It was about selling iPhones. It always was.
 
Will be great to see this. Hopefully it will be rolled out quickly. Maybe there will be some more information about it at WWDC
 
  • Like
Reactions: mganu
the only value is not SMS hacked for multi factor, which is pretty common for all banking and everything.
 
It isn't even a privacy issue, as it's all encrypted. It's just Apple being Apple and forcing others into complying with their draconic ways.
Both RCS and VoLTE are based on IMS architecture. Most of carriers have successfully transited from CSFB to VoLTE, and working perfectly. Then why they cannot make their own RCS server and just hand to Jibe to run it?
 
  • Like
Reactions: ennisw
Google does not use a proprietary standard for E2EE. They rely on the open-source Signal Protocol, the same encryption standard used by popular messaging apps like Messenger, WhatsApp, Instagram, and Skype.

Running on Google Servers under Google's control. Google wanted Apple to route messaging through Google's systems, under Google's control.
 
  • Like
Reactions: ennisw
Running on Google Servers under Google's control. Google wanted Apple to route messaging through Google's systems, under Google's control.

Google didn't start with RCS servers, they wanted the carriers to handle it. The carriers never did, so google built their own.
 
Generally this is great and I’d be interested to know how e2e will be implemented. Presumably the encryption is at the edge/device level?

Or do carriers have to flick a switch ? If so I can see that a lot won’t. And if it’s dependent on carriers hopefully it’ll be clear when encryption is not on.
 
Generally this is great and I’d be interested to know how e2e will be implemented. Presumably the encryption is at the edge/device level?

Or do carriers have to flick a switch ? If so I can see that a lot won’t. And if it’s dependent on carriers hopefully it’ll be clear when encryption is not on.
Presumably the networks will need to update to support the new version of RCS (whether that be their own server or a third party server bought in).
 
  • Like
Reactions: bluecoast
RCS is superior as it's built in and cross platform.

The whole green Vs blue bubble thing is very much an American thing and only helps solidify the poor opinion the rest of the world has of that country. It's the epitome of American culture and it's toxic AF.

The rest of the world uses WhatsApp anyway.
Agreed. For those of you in the USA it’s hard to overstate how unimportant imessage is for the rest of the world.

Everyone really does use WhatsApp which has become a lingua Franca for messaging - whether you like it or not.
 
now this is news I care about…

what about audio calls between iPhone and Android? Is this something that can be incorporated down the line? I’m specifically referring to E2EE calls between iPhone and Android..

ETA: will this give us the option to toggle read receipts on/off?
 
Last edited:
The specifications make it mandatory otherwise you cannot claim to be UP X complaint.
Not everything in UP is mandatory. Quite a few features are optional, like typing indicators or read receipts in groups (which coincidentally happens to be how Apple has always treated iMessage group chats).

Not sure what category the new tentpole features fall into, but I hope they‘re mandatory.
 
Will be great to see this. Hopefully it will be rolled out quickly. Maybe there will be some more information about it at WWDC
This will, at most, be relegated to a tiny tile on their iOS wrap up feature slide.
Presumably the networks will need to update to support the new version of RCS (whether that be their own server or a third party server bought in).
Since no network runs their own RCS hub on iOS, instead opting to provide Jibe endpoints, it will probably work right away once Google updates Jibe. There is a tiny chance that Apple exposes a boolean property to toggle this on/off for carriers in their carrier profile, but I don‘t think that happens.
...

ETA: will this give us the option to toggle read receipts on/off?
You can already toggle read receipts on a global (via the toggle in the settings app) and contact basis (via the conversation info sheet). I have read receipts off globally for everything (iMessage & RCS).

I did read about people saying that it doesn‘t work for them (works for me though), so it‘s probably one of the many bugs that RCS on iOS has.
 
Not everything in UP is mandatory. Quite a few features are optional, like typing indicators or read receipts in groups (which coincidentally happens to be how Apple has always treated iMessage group chats).

Not sure what category the new tentpole features fall into, but I hope they‘re mandatory.
I'm aware but those features are mandatory.

Shall: These terms dictate that a functionality and/or process is Mandatory

in-line replies
R5-33-1 The client shall be capable of selecting a message to send a Reply Message to, in Chat conversations.
emoji reactions
R5-35-1 The client shall be capable of selecting a message to send a Reaction to, in Chat conversations.
message editing
R5-39-1 The client shall allow the user to select an already sent message and to send an edited message to replace the selected message.
message deletion
R5-41-1 The client shall allow the user to select one or more RCS Messages that they have already sent and to delete them for the user themselves and for the recipient.
 
  • Like
Reactions: TimFL1
Running on Google Servers under Google's control. Google wanted Apple to route messaging through Google's systems, under Google's control.
Think for a second, how do you think RCS currently works when you send a message from iOS to Android in the US.

Hint: all carriers in the US currently use Google Jibe and in order for cross carrier interconnectivity to work, they all have to connect to Google Jibe RCS Hub. All your RCS messages from iOS is routed through Google's systems under Google's control. Google does not need to demand anything of Apple, that is simply how it must work.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.