That’s because you’re using SMS, that’s not the fault of the messaging app. Using a third party messaging app is the correct way to go, it’s encrypted, supports group chats, and bigger messages.
So does iMessage, to be fair. The problem is that Apple decided not build clients for alternative platforms, but the app itself is quite competent.
Hopefully Apple can convince the telco people to implement E2EE in RCS (though good luck getting that through with wiretap laws all around the world, lol) so there’s some kind of cross-platform standard here. Apple is going to implement RCS to save Americans from blurry videos at the very least, but it won’t add Google’s proprietary encryption standard.
RCS is controlled by GSMA, not Google. I’m sure they’ll welcome Google’s extensions, but Google doesn’t get to decide.
Google can try to do the same thing they did to XMPP, but then they get the same “Androids don’t receive our pictures” problem that’s driving teenagers to buy iOS in the USA in the first place.
Specification may be not controlled by Google, but the single available client implementation is controlled by Google and almost all carriers are delegating managing their RCS servers to Google.
While XMPP or Matrix server you can host even on your LAN network between two computers.
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.
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.
That’s because you’re using SMS, that’s not the fault of the messaging app. Using a third party messaging app is the correct way to go, it’s encrypted, supports group chats, and bigger messages.
So does iMessage, to be fair. The problem is that Apple decided not build clients for alternative platforms, but the app itself is quite competent.
Hopefully Apple can convince the telco people to implement E2EE in RCS (though good luck getting that through with wiretap laws all around the world, lol) so there’s some kind of cross-platform standard here. Apple is going to implement RCS to save Americans from blurry videos at the very least, but it won’t add Google’s proprietary encryption standard.
Hopefully not RCS, but maybe Matrix or the Signal protocol, as RCS is entirely controlled by Google and there aren’t any FOSS clients.
RCS is controlled by GSMA, not Google. I’m sure they’ll welcome Google’s extensions, but Google doesn’t get to decide.
Google can try to do the same thing they did to XMPP, but then they get the same “Androids don’t receive our pictures” problem that’s driving teenagers to buy iOS in the USA in the first place.
Specification may be not controlled by Google, but the single available client implementation is controlled by Google and almost all carriers are delegating managing their RCS servers to Google.
While XMPP or Matrix server you can host even on your LAN network between two computers.
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.
deleted by creator
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.
Oh I’m well aware of that, I’m just complaining 😂