Apple can implement RCS, but what then?
Currently people not using Apple approved device in US can be marginalized. After RCS people not using Apple or Google approved device are going to be marginalized. And they both have wide requirements in order to be approved, recently Google started requiring Play Integrity check. So no RCS after you get rid of YouTube app for example.
This is the same discussion all over about defaults like if this was LibreOffice vs MS Office debate.
Marginalising people for green bubbles is not something Apple can fix, that’s just shitty people being shitty to people.
RCS does solve the real-world problem of “sending images larger than 1MB” and “sending videos larger than 3MB”. It also fixes the god-awful group messaging standards, adds a whole range of modern texting abilities, and practically removes the character limit. That’s objectively better than how things are right now.
The RCS payment standard requires blocking rooted or jailbroken phones. Implementing payments (and I don’t know if they already do) and permitting rooted phones would actually violate the standard. If Google makes it so you can send people money through RCS the same way you can with iMessage, they have a very good reason to ban these devices, even if I may personally disagree with it.
I don’t text so I don’t give a fuck about what colour my bubble will be. It would be nice for Google to open their encryption system to the GSMA so E2EE RCS would actually be a possibility, but even without E2EE RCS would allow me to group text again (MMS has been disabled by most carriers here, SMS doesn’t support groups).
As for your Youtube app: you can disable it with ADB without root. There are good reasons for rooting your phone, but just removing Youtube is not one of them. If you did root your phone, you can turn RCS back on with the standard Magisk hiding procedures; once you get Google Wallet to work again, Google Messages should work fine, too.
If you did root your phone, you can turn RCS back on with the standard Magisk hiding procedures
I really do not want to use hacks like that in order to send a text message.
It reminds me of the:
Voting in elections now requires buying a Big Mac and having receipt for verification, I don’t want that.
No problem with that, just ask a friend to buy it for you. Or you can just fake
A messaging standard that requires carrier, phone modem and phone operating system all implementing in order for it to work is outdated mindset from the era of flip-phones. We have Internet now, which allows sending any data to any device and we have installable apps that can send anything through it. Implementing an awful and already outdated standard in a most user freedom unfriendly manner just to replace even more outdated standard is not great.
Imagine if Google now started promoting a FAX 2.0 protocol for fax machines, which would implement some of basic email features already being in email for 20. No, just use email and if your friends do not have it show them how to use it.
Well, if you can convince my carrier to embed XMPP into their texting network, I’d gladly take it over RCS. In practice, you can pick between “works on any phone” and “not designed for carriers”.
Using the carrier standard is entirely optional. I only use it in extreme circumstances, like with outdated 2FA websites and when half a bar of 2G is all I can get. I like it that the built-in app will have modern features on any modern phone soon, but that’s about all I feel about it.
If anything, the relative openness of RCS at least lets you write bots and other tools. There are a bunch of open source libraries that can communicate with RCS servers. Can’t say as much with WhatsApp (outside of the EU) and iMessage.
deleted by creator
Apple can implement RCS, but what then? Currently people not using Apple approved device in US can be marginalized. After RCS people not using Apple or Google approved device are going to be marginalized. And they both have wide requirements in order to be approved, recently Google started requiring Play Integrity check. So no RCS after you get rid of YouTube app for example.
This is the same discussion all over about defaults like if this was LibreOffice vs MS Office debate.
Marginalising people for green bubbles is not something Apple can fix, that’s just shitty people being shitty to people.
RCS does solve the real-world problem of “sending images larger than 1MB” and “sending videos larger than 3MB”. It also fixes the god-awful group messaging standards, adds a whole range of modern texting abilities, and practically removes the character limit. That’s objectively better than how things are right now.
The RCS payment standard requires blocking rooted or jailbroken phones. Implementing payments (and I don’t know if they already do) and permitting rooted phones would actually violate the standard. If Google makes it so you can send people money through RCS the same way you can with iMessage, they have a very good reason to ban these devices, even if I may personally disagree with it.
I don’t text so I don’t give a fuck about what colour my bubble will be. It would be nice for Google to open their encryption system to the GSMA so E2EE RCS would actually be a possibility, but even without E2EE RCS would allow me to group text again (MMS has been disabled by most carriers here, SMS doesn’t support groups).
As for your Youtube app: you can disable it with ADB without root. There are good reasons for rooting your phone, but just removing Youtube is not one of them. If you did root your phone, you can turn RCS back on with the standard Magisk hiding procedures; once you get Google Wallet to work again, Google Messages should work fine, too.
I really do not want to use hacks like that in order to send a text message.
It reminds me of the:
A messaging standard that requires carrier, phone modem and phone operating system all implementing in order for it to work is outdated mindset from the era of flip-phones. We have Internet now, which allows sending any data to any device and we have installable apps that can send anything through it. Implementing an awful and already outdated standard in a most user freedom unfriendly manner just to replace even more outdated standard is not great.
Imagine if Google now started promoting a FAX 2.0 protocol for fax machines, which would implement some of basic email features already being in email for 20. No, just use email and if your friends do not have it show them how to use it.
Well, if you can convince my carrier to embed XMPP into their texting network, I’d gladly take it over RCS. In practice, you can pick between “works on any phone” and “not designed for carriers”.
Using the carrier standard is entirely optional. I only use it in extreme circumstances, like with outdated 2FA websites and when half a bar of 2G is all I can get. I like it that the built-in app will have modern features on any modern phone soon, but that’s about all I feel about it.
If anything, the relative openness of RCS at least lets you write bots and other tools. There are a bunch of open source libraries that can communicate with RCS servers. Can’t say as much with WhatsApp (outside of the EU) and iMessage.