this post was submitted on 12 Oct 2023
743 points (95.6% liked)
Technology
59243 readers
3315 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
You used a lot of words, just too say that you don't know what you are talking about.
Well then go on, why am I wrong? Or do you just not like my opinion and are grasping at straws to make youself feel better?
RCS is an open standard created by GSMA. That's why you're wrong.
Googles implementation of the RCS standard has extra things not included in the base standard. The encryption for example is something Google added that is not part of the standard.
Additionally, Google does not allow any other implementation of RCS to talk to their jibe servers to pass messages without them explicitly approving it.
So what Google has functionally created is a proprietary messaging service built on top of an open standard. This is what most people miss about all of the coverage of Google pushing for RCS.
I didn't know that Google built encryption on top of the standard, I thought it was part of it.
Besides that though, Google would be making the dumbest business move if they didn't let Apple's potential RCS implementation talk to theirs.
Besides that, the point that RCS is still an open standard stands and should replace SMS just because of how archaic and old it is. Heck, there's still a character limit.