464
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 08 Nov 2023
464 points (97.5% liked)
Technology
55744 readers
3701 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
It's quite literally well documented that Apple doesn't want to support RCS because it pressures people to get iPhones. SMS is an ancient garbage protocol, what Google is trying to do is get Apple to support SMSs 21st century replacement and RCS support will fix literally every issue iPhone users have texting Android users. Broken group chats, trash quality videos, ultra compressed images, no reactions or stickers, threaded chats etc etc
Google wants Apple to use Google’s proprietary extension of RCS, which runs on Google’s own servers as is precisely as open as iMessage. Effectively nobody uses the industry-standard version of it.
Where's the source for that? Last I read, Google was using the GSMA Universal RCS profile
Google does own and run the Jibe platform as an RCS vendor, but Apple doesn't need to use it. They can go with a different vendor or run their own RCS servers just as easily
Google's astroturf campaign for "RCS" promotes encrypted messages but RCS has no support for this. Google wants to force people to use its proprietary extension, which runs exclusively on Google's servers.
And absolutely nothing is stopping Apple from rolling its own RCS extensions that apps can support as well
So what’s the idea here? Apple rolls out another extended version of RCS that’s proprietary as well?
It might be proprietary, but at least any messaging app Android, iOS or some future third competitor will be able to implement it.
Unlike iMessage which is both proprietary and closed off from third party use
And yet, no developer other than Samsung has been granted access to Google’s version of RCS.
I’d love to see a truly standard, rich, secure messaging service, but I’m not convinced what Google is doing here is any better than Apple.
The difference is, you can choose not to use Googles RCS extension and opt for the Universal Profile standard instead and it will interop with people on other RCS profiles, even Googles, just fine.
iMessage doesn't do any of that, your choice is iMessage with other Apple users or a 30+ year old protocol. That's it.
Except that’s not what happened in reality before Google started rolling out their version of RCS.
The carriers implemented their own versions that didn’t weren’t interoperable with each other, and that was for the ones that even bothered with it at all.
And now they have even less incentive to try.
RCS is nice in theory, but no one is serious about implementing the universal profile.