this post was submitted on 07 Mar 2024
265 points (100.0% liked)
Technology
37799 readers
85 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
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.