Technology

59575 readers

4163 users here now

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

Our Rules

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

Approved Bots

founded 1 year ago

MODERATORS

472

Apple announces that RCS support is coming to iPhone next year (9to5mac.com)

submitted 1 year ago by kae@lemmy.ca to c/technology@lemmy.world

73 comments fedilink hide all child comments

In a surprising move, Apple has announced today that it will adopt the RCS (Rich Communication Services) messaging standard. The feature will launch via a software update “later next year” and bring a wide range of iMessage-style features to messaging between iPhone and Android users.

Apple’s decision comes amid pressure from regulators and competitors like Google and Samsung. It also comes as RCS has continued to develop and become a more mature platform than it once was.

you are viewing a single comment's thread
view the rest of the comments

[–] Kethal@lemmy.world 4 points 1 year ago (1 children)

Ok, so the gist of this that I'm getting is that there is an genuinely open RCS standard, but no one has implemented it. Instead, Google has their thing that's been modified for their benefit at the expense of consumer privacy, and that Apple seems to be making their own similar version. So RCS itself isn't bad, but it's being ruined by bad actors, and as of yet there are no good actors.

[–] Senshi@lemmy.world 1 points 1 year ago

Pretty much. RCS just defines the protocol. That is basically how messages are formatted, how recipients and senders are labeled, how timestamps are formatted, how messages are compressed, transferred and possibly stored and resent in case of inability to deliver (e.g. recipients phone is off) and a lot more technical stuff.

To use this, you need a network of servers that can actually receive messages from phones/ cell network, then possibly transfer them to a server/ cell tower near the recipient(s) to have it broadcast there, making sure only the intended recipient can decrypt it, and possibly storing it for an unknown duration and a number of attempts to deliver it if the recipient is unreachable. And possibly sending a receipt or failure-to-deliver message back to the sender as well. And all of this has to work reliably 24/7, because people will not accept downtimes.

And then you also need client software on the phones to send/receive messages using the RCS protocol as well, hopefully handling true e2e encryption as well.

It's a lot of hardware and software engineering to actuallyimplement such a seemingly fundamental standard.