I sometimes delete random green bubbles and say I never got them which pisses off android users and they blame their carrier. 🤣No one cares.
I sometimes delete random green bubbles and say I never got them which pisses off android users and they blame their carrier. 🤣No one cares.
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.I sometimes delete random green bubbles and say I never got them which pisses off android users and they blame their carrier. 🤣
That was Apple's position, but it was an obvious lie: SMS isn't encrypted either. It was about selling iPhones. It always was.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.
Example of a person I would never willingly associate with right here.
Do better.
To be honest, SMS is worse for security than RCS without E2EE. At least RCS is always encrypted in transit. SMS sends plain text all the way.That was Apple's position, but it was an obvious lie: SMS isn't encrypted either. It was about selling iPhones. It always was.
Assuming banks switch to using RCS instead of just continuing with SMS.the only value is not SMS hacked for multi factor, which is pretty common for all banking and everything.
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?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.
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.
It’s so asasine of apple to do this and it’s apple at its worse.The bubbles will still be green though.
O2 does too.A pity only EE and BT use RCS in the UK. A lot of providers still don't do Visual Voicemail
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).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.
Agreed. For those of you in the USA it’s hard to overstate how unimportant imessage is for the rest of the world.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.
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).The specifications make it mandatory otherwise you cannot claim to be UP X complaint.
This will, at most, be relegated to a tiny tile on their iOS wrap up feature slide.Will be great to see this. Hopefully it will be rolled out quickly. Maybe there will be some more information about it at WWDC
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.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).
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)....
ETA: will this give us the option to toggle read receipts on/off?
I'm aware but those features are mandatory.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.
Shall: These terms dictate that a functionality and/or process is Mandatory
emoji reactionsR5-33-1 The client shall be capable of selecting a message to send a Reply Message to, in Chat conversations.
message editingR5-35-1 The client shall be capable of selecting a message to send a Reaction to, in Chat conversations.
message deletionR5-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.
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.
Think for a second, how do you think RCS currently works when you send a message from iOS to Android in the US.Running on Google Servers under Google's control. Google wanted Apple to route messaging through Google's systems, under Google's control.