468
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
468 points (100.0% liked)
Technology
59379 readers
2219 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
Bingo. This whole case is designed to make Apple look like the bad guy whilst Google hides their real agenda of forcing Apple to use a protocol Google controls and thus stamp out Google’s competition.
From what I've read, Google just owns the reference implementation. Apple could implement it themselves, but then lose out on certain non-cross-platform features, like e2e encryption.
I’ve read the specification. Google’s implementation is the only real implementation (raw RCS is basically a dead project) as Google have added a load of custom extensions to RCS that means, to be interoperable, you’d need to use Google’s (which I imagine requires licensing since it doesn’t appear to be open source).
That's basically what I said, but better.