Apple is bringing RCS to the iPhone in iOS 18
www.theverge.com
Ding dong, the SMS is dead.

The long-awaited day is here: Apple has announced that its Messages app will support RCS in iOS 18. The move comes after years of taunting, cajoling, and finally, some regulatory scrutiny from the EU.

Right now, when people on iOS and Android message each other, the service falls back to SMS — photos and videos are sent at a lower quality, messages are shortened, and importantly, conversations are not end-to-end encrypted like they are in iMessage. Messages from Android phones show up as green bubbles in iMessage chats and chaos ensues.

Apple’s announcement was likely an effort to appease EU regulators.

  • ᗪᗩᗰᑎ@lemmy.mlEnglish
    652·
    7 months ago

    It’s a terrible move, especially to make it default.

    Subjective, but lets see what you bring to the table.

    It’s just as bad a protocol as SMS in its own way: It’s still tied to a phone number/sim, so you can’t just login to the service via a browser or an app.

    That’s how text (SMS/RCS) messaging works. Did you expect something different? Did you expect the SMS replacement to not require a phone number?

    It has lots of failures, worst of all, SILENT FAILURES, where you don’t even know your messages aren’t being sent - just look at the communities around here discussing it.

    I’ve been using it without issue for quite a while now, but that’s just one data point. If you have stats to back up your claim, I would love to see that.

    There’s no common protocol here really, …

    “The GSMA’s Universal Profile is a single, industry-agreed set of features and technical enablers developed to simplify the product development and global operator deployment of RCS” Source: https://www.gsma.com/solutions-and-impact/technologies/networks/rcs/universal-profile/

    lots of parts work only by decree of each host (e.g. iOS won’t have E2EE with anyone not on iOS, because that requires every cell provider to agree to the config they’re going to use.

    This is how distributed/federated systems work and this is one of their cons. They won’t always be 100% compatible as each component is independent but the goal is to eventually reach feature parity. See Matrix chat clients that didn’t all have encryption (or other features) on day 1 or XMPP which has lots of clients, none of which support all features.

    This is the 21st century, and this is the best they can do - a protocol that fails with no notice? Without standardized encryption? That’s tied to hardware?

    Please post evidence of this. Again, I’ve had zero issues and every Android user is using RCS by default now - have heard zero complaints.

    I had a better experience in 2009 running Pidgin on my phone and my laptop using XMPP. That didn’t require a phone number - I could login and see my messages in both places simultaneously… 15 years ago.

    Correct! XMPP is not an SMS replacement and thus it doesn’t need a phone number. In fact, you can’t “text” an XMPP user, so I’m not sure what you’re complaining about here?

    No, RCS is a way to make the plebes think they’ve got a new and better system while still delivering garbage.

    RCS vastly improves over SMS with the following features:

    • High Quality Multimedia Messaging: Unlike SMS/MMS, which is limited to text and potato sized image/videos, RCS allows sending and receiving photos, videos, and other files at significantly higher quality.
    • Rich Content Sharing: RCS supports sharing richer content formats like GIFs, location sharing, and contact cards.
    • Improved Group Chatting: RCS provides a more feature-rich group chat experience with features like group chat names, adding/removing participants, and seeing who has read messages (with read receipts).
    • Typing Indicators: Similar to many messaging apps, RCS lets you see when someone is typing a message.
    • Improved Message Reliability: RCS messages are sent over data networks, so unlike SMS, they shouldn’t get lost due to network congestion.
    • End-to-End Encryption: RCS can offer end-to-end encryption for chats, providing an extra layer of security for your messages (availability varies by carrier).

    But keep spreading FUD and hating on something that actually moves the needle forward.

    Love you downvoters that don’t know enough to argue, just drive by and downvote.

    I think they’re downvoting you because you’re wrong - plainly wrong - and in this day and age its much easier to bury (downvote) blatantly wrong information than to reply to it. So I’m replying for everyone else but I will not be downvoting you. FUD should be fought back with evidence, but MAAN is it tiring.

    ONE person had the guts to say why he disagreed with me.

    It’s not about guts, its about wasting time, effort, not giving a shit. I slightly give a shit and want people who are less educated on the subject to see the other side of it.

    Nevermind that BorgDrone explained what’s wrong with RCS better than I care to. You drive-by downvoters can’t even be bothered to learn about RCS.

    Nothing to comment on here.

    RCS is garbage. Plain and simple. I will never allow it on my devices, …

    At the end of the day RCS is objectively better than what exists today in the world of carrier messenger services (SMS/MMS). Is it better than iMessage? I don’t think anyone would agree, especially not if you only message other iPhone users. Is it a better out-of-the-box experience for interoperability? Absolutely! And you’re being disingenuous if you disagree, but I’m happy to hear you out.

    just like with Whatsapp, Facecrap, Twitter, Instagram, etc.

    We can agree to these being garbage ✊

    All that said, am I actively going to ask people to use RCS? Never! The same way I wouldn’t ask someone to use iMessage if I had an iPhone. They’re both products developed ultimately to push users into their respective ecosystem to the benefit of Google/Apple/Carriers.

    I’ll stick to Signal and Matrix until something better comes along.