this post was submitted on 16 Jun 2024
342 points (93.2% liked)
Technology
59223 readers
3357 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
Only Google’s proprietary extension has encryption. The actual industry standard specification of RCS has no encryption defined at all.
Edit: It turns out Apple have refused to use Google’s proprietary encryption implementation and are instead working with GSMA to update the RCS Universal Profile specification to finally have encryption defined and standardised so that any RCS client can handle encrypted payloads (whereas only Google Messages today can do encrypted RCS and requires other users to be exclusively using Google Messages otherwise messages are sent unencrypted).
So….Apple good?
I'll take that as a win!
We will find out when they push the update.
Yes, that’s the right thing todo. My understanding was that Google went down this path and didn’t succeed, so went ahead with their own. Maybe have the other major mobile os onboard will be enough to get the carriers off their asses