At lease with Apple stepping into RCS it will get better. Having them contribute research would add more features or at lease actual End to End encryption to the GSM Universal profile. Not just Google and Google Messages.
I think initially RCS features were determined by what Server was hosting it. Google of course wanted everyone to use their profile on their servers… With a great reputation on data retention and privacy Google was of course getting Apples approval.
Google of course wanted everyone to use their profile on their servers…
Not exactly; they spent years trying to herd the carriers into doing RCS the GSM way. They only shifted to the iMessage-like strategy when the carriers couldn’t get their act together. They reached a “Fine, I’ll do it myself” moment, and suddenly, finally, the ball really started rolling for RCS.
Google finished adding full E2E encryption a few months ago. It’s actually more secure than iMessage now since your RCS messages aren’t stored on the cloud like iMessages. I’m guessing this is also one other reason Apple is adopting RCS.
I thought RCS only works with a server present to act as the host. Having things pass through a Google controlled server was the privacy concern. Since they can easily retain that data in its encrypted form. Which they could likely just as easily unencrypt.
While Apple relies on AWS and Azure for their cloud services. I’m sure they have some sort of agreement or control over the data that limits what Amazon and Microsoft could potentially access.
Apple however can’t guarantee the security or privacy of the Apple user when interacting with an Android phone via RCS. I wonder how they will twist a false sense of privacy
Having them contribute research would add more features or at lease actual End to End encryption to the GSM Universal profile.
It’s not a lack of research that hinders E2EE on the universal profile. Google only did it themselves because the standards bodies and carriers just wouldn’t do it themselves.
At lease with Apple stepping into RCS it will get better. Having them contribute research would add more features or at lease actual End to End encryption to the GSM Universal profile. Not just Google and Google Messages.
I think initially RCS features were determined by what Server was hosting it. Google of course wanted everyone to use their profile on their servers… With a great reputation on data retention and privacy Google was of course getting Apples approval.
Not exactly; they spent years trying to herd the carriers into doing RCS the GSM way. They only shifted to the iMessage-like strategy when the carriers couldn’t get their act together. They reached a “Fine, I’ll do it myself” moment, and suddenly, finally, the ball really started rolling for RCS.
Google finished adding full E2E encryption a few months ago. It’s actually more secure than iMessage now since your RCS messages aren’t stored on the cloud like iMessages. I’m guessing this is also one other reason Apple is adopting RCS.
https://www.theverge.com/2023/8/8/23824800/google-messages-rcs-end-to-end-encryption-default-group
I thought RCS only works with a server present to act as the host. Having things pass through a Google controlled server was the privacy concern. Since they can easily retain that data in its encrypted form. Which they could likely just as easily unencrypt.
While Apple relies on AWS and Azure for their cloud services. I’m sure they have some sort of agreement or control over the data that limits what Amazon and Microsoft could potentially access.
Apple however can’t guarantee the security or privacy of the Apple user when interacting with an Android phone via RCS. I wonder how they will twist a false sense of privacy
It’s not a lack of research that hinders E2EE on the universal profile. Google only did it themselves because the standards bodies and carriers just wouldn’t do it themselves.