this post was submitted on 08 Nov 2023
178 points (97.8% liked)

Technology

58752 readers
4300 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
178
Google turns to regulators to make Apple open up iMessage (www.theverge.com)
submitted 11 months ago by [email protected] to c/[email protected]
44 comments fedilink hide all child comments
 

Google turns to regulators to make Apple open up iMessage::iMessage serves should be regulated under the EU’s new Digital Markets Act (DMA), Google and a group of major European telcos has told the European Commission.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 21 points 11 months ago (2 children)

RCS is an open standard, isn't it? Are you referring to the E2E encryption that Google added to Android?

[–] [email protected] 50 points 11 months ago (2 children)

Googles implementation of RCS, the one they are pushing as standard, is indeed proprietary

[–] [email protected] 14 points 11 months ago (1 children)

Eh? GSMA created RCS and Google simply setup their own servers to run it. So I guess you could argue that Google's RCS network is proprietary, but RCS itself is most definitely not. There's technical documentation freely available for implementing your own RCS client/server, if you care to do so.

[–] [email protected] 9 points 11 months ago (1 children)

Well didn't they initially want carriers implementing RCS with interoperability between each other to sunset sms? But that didn't quite pan out. IIRC there was a time when Verizon had a limited number of devices that supported RCS but only on their network, similar story with Bell in Canada. Hell at one point even Samsung had RCS but only with other Samsung phones. Fragmentation was rampant so Google took matters into their own hands. Not saying I'm happy Googles at the helm but they didn't start out with that intention.

[–] [email protected] 3 points 11 months ago

Yeah it’s unfortunate we weren’t able to get RCS everywhere, as an improvement over sms. I imagine the encryption to be a sticking point preventing ubiquity

[–] [email protected] 3 points 11 months ago (1 children)

You got a source for that?

[–] [email protected] 7 points 11 months ago (1 children)

https://en.m.wikipedia.org/wiki/Rich_Communication_Services

So any RCS w/ Encryption that you see is referring to Google’s implementation that only runs on Google servers.

[–] [email protected] 1 points 11 months ago

So their implementation is RCS standards with an added encryption layer. What's the issue?