this post was submitted on 16 Nov 2023
469 points (98.2% liked)
Technology
59708 readers
1960 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.