4 ms·
They should implement the version (and extensions) that gives them interoperability with the most users. Which, yes, would probably be whatever Google implemen
by kelnos 4y ago
They should implement the version (and extensions) that gives them interoperability with the most users. Which, yes, would probably be whatever Google implemented, including the E2EE extensions. This... isn't really hard?
- inferiorhuman 4y agoWhy should Apple (or anyone) be on the hook for implementing proprietary extensions? Once you peel back the marketing schtick this is just demanding that Google be able to determine which proprietary services are included on an Apple product. That's ridiculous on its face. If the issue is interoperability with Android users, fine. Google had successful messaging apps on iOS (I used a few) and they destroyed them through their own mismanagement. RCS doesn't solve that in the slightest. > This... isn't really hard? If you want E2EE the demand is now that Apple spin up its own Google-RCS servers and/or rely on Google's infrastructure. If you want Apple to rely on the carriers you don't get E2EE. Rather than work with the carriers Google fragmented RCS making implementation that much more difficult.
- int_19h 4y agoAt the end of the day, what we need is interop, so Apple should be forced to either open the protocol, or adopt something that is already open. But either option is strictly better than the existing mess.
- simonh 4y ago>or adopt something that is already open Like SMS?
- anifru 4y agoObviously we're talking about something more modern than SMS here.
- simonh 4y agoThe problem is none of the 'more modern' open alternatives to SMS actually seem any better.
- int_19h 4y agoHow exactly RCS is not strictly better than SMS?
- inferiorhuman 4y agoTurn that on its head. What does RCS bring to the table? RCS brings two types of features: those that carriers will try to monetize (file transfer, VoIP, visual voice mail) and those that seek to drive "customer engagement" (chatbots, carousels, branding, quick-reply suggestions, "rich" cards). From the Wikipedia page: RCS Business Messaging (RBM) is the B2C (A2P in telecoms terminology) version of RCS. *This is supposed to be an answer to third-party messaging apps (or OTTs) absorbing mobile operators' messaging traffic and associated revenues*. While RCS is designed to win back Person-to-Person (P2P) traffic, RBM is intended to retain and grow this A2P traffic. … RBM is expected to attract marketing and customer service spend from enterprises, thanks to improved customer engagement and interactive features that facilitate new use cases. *This was the primary reason for the development of RCS by the GSMA*. No. Thanks. As I said, I don't really care if Apple implements RCS support in their Message app. If they do it's just one more thing I'll disable. My take is that carriers should be dumb pipes. Voice, SMS, and data routing and that's it. Part of the reason RCS is already fragmented is because the carriers are trying to monetize it, you can bet your ass they're going to continue to drag their feet with E2EE – which is why Google's stood up their own separate RCS infrastructure.
- int_19h 4y agoEven just fixing group chats alone is a big deal.
- 4y ago
- inferiorhuman 4y agoBut either option is strictly better than the existing mess. Disagree. We have interoperability, just not with advanced features within the default messaging apps. To me that's not a big deal at all as there are other, popular, options. We should get out of the habit of relying on carriers to provide much more than dumb pipes. To that end SMS (not MMS) works just fine and RCS is just going to continue to get bogged down. It's easy to say that if Apple bent to the will of the carriers the iPhone would never have been as good as it is. But look at RCS, Google had to stand up their own infrastructure because the carriers weren't cutting it. It's not that RCS is not the right product it's that RCS is the wrong approach entirely. Even in the United States Android is wildly popular. They've had every opportunity to create a wildly popular messaging platform and have failed. Google killed their own products as a result of their internal culture. This isn't Netscape vs IE again, it's more like Mosaic vs Gopher (or AOL vs Netscape if you like). I was going to write "as much as I'd like to see non-Apple devices brought into the iMessage fold" but then I realized that's not true. I don't care because I'd just use Signal. In fact I still use Signal with some friends that have iPhones. RCS wouldn't change that, it'd either be one more shitty carrier product to avoid or one more shitty Google product that's going to get killed in a few months.
- gumby 4y ago> They should implement the version (and extensions) that gives them interoperability with the most users They already have that, with SMS. Perhaps you only exchange messages with people in rich countries so don’t notice what is most commonly implemented by carriers?