this post was submitted on 27 Jun 2024
238 points (96.5% liked)

Technology

59288 readers
3612 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. 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
[–] cm0002@lemmy.world 1 points 4 months ago (1 children)

For one, Google never wanted to implement or run RCS, the carriers were supposed to do that specifically to prevent the fragmentation issue. But they couldn't get off their ass, even after Google spent years pushing them to do so.

For two, even after Google said fuck the carriers I'll do it myself, Apple was invited to participate in its implementation and Apple refused. They could have worked with Google to implement RCS across all devices. They didn't because they want to keep people locked into their ecosystem. They had a great opportunity to ensure all the privacy and encryption features were implemented how they liked.

[–] chiisana@lemmy.chiisana.net -5 points 4 months ago (1 children)

Again, Android problem, not Apple problem.

Apple stated clearly they’re keen on working with GSM Consortium (who owns RCS and has more sway on carriers than Google does) on bringing E2EE to the masses.

If Google’s reputation of finding new and exciting ways to sell targeted ads doesn’t precede them, then they might have a better chance of getting a first party solution like Apple does with iMessage. But alas, Apple is not responsible for Google’s business plan or public image, and that problem is Google’s to solve.

[–] cm0002@lemmy.world 5 points 4 months ago (2 children)

who owns RCS and has more sway on carriers

If that were true, RCS would have been implemented by carriers LONG ago like they were supposed to (the original spec was launched in 2008), well before imessage came out in 2011 and we wouldn't be having this conversation.

But you know who actually does have a TON of sway with Carriers? Apple. You know who probably could have actually gotten them to implement RCS? Apple. Apple could have solved the RCS dilemma even before Google decided to do things themselves.

Apple didn't even need to do much, just drop the mere hint that if carriers didn't start implementing RCS they might stop selling the iPhone through them and they would have bent over backwards to get it done.

They didn't because iMessage is just another tool to keep people locked into their ecosystem, and they've admitted as much. And any excuse of "Oh we wanted to work with the GSM consortium blah blah blah" is just that, an excuse for Apple fanboys like you to latch onto and parrot.

[–] MrSpArkle@lemmy.ca -1 points 4 months ago

Apple couldn’t get the carriers to do shit. They blocked eSIMs for years on iPhones, meanwhile the iPad eSIM implementation was happily allowed.

Even up to the iPhone launch nobody wanted to collaborate with Apple(especially for the voicemail) except Cingular.

[–] chiisana@lemmy.chiisana.net -5 points 4 months ago

They didn’t because it’s not their problem. Other platforms’ users have that problem; Apple users have iMessage.

You buy a Windows phone, you buy a blackberry, you buy a flip phone, you’re using carrier messaging, or whatever app you can run on those platforms.

You buy an Android and suddenly you feel entitled to demand Apple to go to bat for you on carrier messaging? That’s a very entitled hot take.

Apple users have iMessage… amongst other third party chat apps that works fine across different platforms. Apple doesn’t have any obligations to go to bat for other platforms on carrier messaging that they already support.