this post was submitted on 12 Oct 2023
677 points (95.4% liked)
Technology
59092 readers
6622 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
I don’t see any public license for GSMA Universal Profile and it seems you have to engage directly with GSMA to get any detail on the standard. Very much the opposite of things like Signal which not only are the standards public but so are the reference implementations.
I still don’t see an argument for why yet another proprietary standard and protocol is a good thing.
well RCS is to be the successor to SMS, which I believe was also introduced by GSMA
What you are using on Android isn’t RCS, it’s RCS+Google’s proprietary extension. There is no encryption in the spec, and the original implementation that went through carriers is ignored and it goes through Google. It’s essentially Google’s iMessage and they are trying to find their way into breaking Apple’s market share under false pretense.
I’ve just been reading the RCS Universal Profile Service Definition Document and it does stipulate encryption should be used but it is hardly defined how encryption should be implemented nor does it set an interoperable standard for it. I like RCS even less now.
“Methods for encryption, client verification, user authentication and access authorisation are applied by the client and the network on a per interface and protocol basis.”
So basically RCS is happy for there to be interoperability with regards to encryption, almost forcing interoperable implementations to forgo encryption so that different implementations can communicate.
Signal protocol is far far far better a standard than this lazy “service definition”.
Yea, the standard is great for a decade+ ago when it came out, but I’d never trust it as is over other things like Signal or even iMessage. Google’s RCS implementation is as trustworthy as anything else Google makes. They don’t even support it across all their products last I heard. It’s a joke.
Not to mention, you will get bored of it in two or three years and kill it off.
I know, but isn't the point that Google Messages is interoperable with other implementations such as T-Mobile's or Verizon's?
That may be the point, but it’s not working out that way. The spec is older than iMessage. It failed. Google just took it and made their own implementation. I’m not sure if Google’s RCS works with Verizon’s for example, I’m sure basic things do. AFAIK third party developers can’t implement it in their apps, so you have to have an Android phone to use it. Someone correct me if I’m wrong. The entire thing relies on Google to keep it running.
RCS is still IP based so why SMS should be replaced with RCS over Signal still isn’t clear. RCS and Signal are both IP based protocols yet one is proprietary and the other is libre. If we’re getting rid of SMS, we should be replacing it with something anyone can implement without any concerns for licensing or the standard being controlled by a single entity (which Google seems to be positioning themselves to be).