this post was submitted on 05 Dec 2023
79 points (100.0% liked)
Technology
37719 readers
423 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
I think this is the primary reason. Apple only announced working on RCS support very recently. Once that’s out, I don’t really see a place in the market for this.
And it isn’t just compressed images. MMS doesn’t support reactions, replies, typing indicators, or read receipts because it’s ancient. A proper, standardized replacement has been long overdue.
Granted, I’ve heard that RCS is currently heavily reliant on Google’s own servers, so it could be argued as to how “open” this really is.
RCS protocol is open. The apps... not so much.
I think the currently available apps not being free software is less important than the protocol being open, which is good. It allows for the possibility of FOSS clients in the future. My bigger concern at the moment is if most/all of the actual backend infrastructure is controlled by a single stakeholder.