spheric
About
- Username
- spheric
- Joined
- Visits
- 245
- Last Active
- Roles
- member
- Points
- 3,055
- Badges
- 1
- Posts
- 2,477
Reactions
-
Apple's flavor of RCS won't support Google's end-to-end encryption extension
-
Apple's flavor of RCS won't support Google's end-to-end encryption extension
-
Apple's flavor of RCS won't support Google's end-to-end encryption extension
gatorguy said:ericthehalfbee said:Apple basically said “fuck you” to Google.
I’ve repeatedly said Apple should counter Google’s shame campaign by announcing they’ll support RCS when Google opens up their RCS APIs for everyone. Including competitors like WhatsApp or Telegram.
Google has their own RCS APIs in Android but Samsung is the only one allowed to use them. Developers have asked and Google has done nothing to allow other Apps to implement RCS via their system and use E2EE.
So Apple did one better and said they’ll work with standards bodies to improve RCS.
Now Google’s hopes of a messaging duopoly are finished.
Since they don't, we can assume that interoperability is not a priority — it's getting people to use Google's own messaging app. -
Google now tries getting EU to force open iMessage
gatorguy said:spheric said:gatorguy said:spheric said:kmarei said:Google has BBE
blue bubble envy
If you send a message from your iPhone to an Android user they don't see a blue bubble, will have no visual clue the message came from an iPhone, and might well have no idea what all the blue bubble ruckus is because they've never seen it unless they have some iPhone owning friend who shows them.
Pinning it all on a blue bubble is just an effort at being dismissive, "it's all just a juvenile vanity thing", instead of negatively effecting messaging services' continuity, security, and privacy.
I just find it curious that they're apparently playing that angle in a jurisdiction where it's completely irrelevant.
When Android users converse with each other in Google Messages, their texts and shared media can be both private and highly secure due to E2EE RCS. That all changes when an iPhone enters the room.
Once your iPhone's Apple Messages, AKA iMessage, joins the conversation, the discussion is compromised: No longer secure, no longer protected from eavesdropping, no longer encrypted as it travels between the devices used in the conversation. Because of an iPhone user the security, privacy, and continuity is thrown out the window.
It's for that reason that E2EE interoperability between messaging services is essential if we are to discuss things in private, no governments or cell carriers listening in.
The EU is doing a good thing IMHO, and MLS Protocol RFC 9420 will enable it.
Google is just trying to leverage the EU to gain more control over a protocol that they themselves only partially support (so far as it's to their advantage).But my point was the Blue Bubble Envy, which is a real phenomenon in the United States, but simply Not A Thing here in Europe. -
Google now tries getting EU to force open iMessage
gatorguy said:spheric said:kmarei said:Google has BBE
blue bubble envy
If you send a message from your iPhone to an Android user they don't see a blue bubble, will have no visual clue the message came from an iPhone, and might well have no idea what all the blue bubble ruckus is because they've never seen it unless they have some iPhone owning friend who shows them.
Pinning it all on a blue bubble is just an effort at being dismissive, "it's all just a juvenile vanity thing", instead of negatively effecting messaging services' continuity, security, and privacy.
I just find it curious that they're apparently playing that angle in a jurisdiction where it's completely irrelevant.