21–30 of 165 posts
phone are running android os isn't it? carriers still can roll their rcs on ios
Apple has shown no interest in supporting RCS, because the features it adds are basically akin to iMessage... which iPhones already have.
Earlier quoted context omitted.
Indeed, this seems to be needlessly kicking life back into SMS when it was already being replaced by better systems that respect privacy. Of course the decentralized nature of SMS is a good benefit but given how most telecoms are oligopolies disinterested in customers concerns about privacy (and plenty of other things like customer service) it pretty much defeats the value in it.
I wouldn't say needlessly. There's still something to be said for basic technologies that all devices can support.
Which will always be the biggest fundamental flaw with something like Signal or WhatsApp (the need for centralized servers, the requirement to install 3rd party software).
There may be a role for these telecom services to exist perpetually as a backup services, while everyone still uses apps as their primary communication method. But RCS seems to be trying to bring SMS to parity with messaging apps supporting emoticons and media-heavy content, the intention is the same "conversations with friends" use-case as the messaging apps.
There may even be an argument to keep SMS dumb and simple like phone lines. Especially if they aren't going to adopt encryption with the rest.
Is this basically an Android-only version of iMessages?
No, it's an industry agreed standard of an implementation similar to iMessage without end to end encryption. It was created by many of the carriers as an upgrade to SMS.
That effectively makes it into crappy iMessage for Android. Only works within one OS ecosystem, but it's unencrypted, managed by your carrier, and limited to the one cellular device itself instead of also working directly on your wifi-connected tablet and computer.
It would be nice of Apple to support this if it's an improvement over SMS/MMS, but Apple drags their feet on supporting any sort of standards that they didn't create. And even some that they did (pour one out for OpenCL).
Can anyone confirm the biggest issue (in my opinion) with RCS? It's not end-to-end encrypted. Update: Confirmed it myself [1]. End-to-end encryption is not even an option. Which is perfect for the data addicts like Google. But honestly I would never ever recommend this as an avenue for people to use over something like WhatsApp. [1]: https://www.theverge.com/2019/11/14/20964477/googles-rcs-cha...
The problem is: most people won’t care or know the difference. This is going to strong arm things away from the messaging app market and iMessage.
The blue bubbles in the GIF example look exactly like iMessage on iOS, coincidence?
I am very curious how carriers will respond to Google deciding to preempt them by pushing an app update to redirect all text messaging straight to Google servers versus the carriers. Google seemed like it was respecting the carriers' involvement, right up until carriers announced plans to build their own RCS system that didn't give Google the data. Suddenly, Google is turning on RCS? Presumably Google was hoping it c…
To be honest, I think they might find after it's turned on that the limitation to the Google Messages app (which is not the default on Samsung devices and hence represents very little in terms of market share) doesn't move the needle at all and makes very little difference. Certainly, the impact of turning it on on the UK market seems to have been zero. If Google follows through by enabling it system wide in future O…
Earlier quoted context omitted.
No, it's an industry agreed standard of an implementation similar to iMessage without end to end encryption. It was created by many of the carriers as an upgrade to SMS.
It's an industry standard, but if Apple doesn't implement it in iOS then it's only useable from one Android device to another. That effectively makes it into crappy iMessage for Android. Only works within one OS ecosystem, but it's unencrypted, managed by your carrier, and limited to the one cellular device itself instead of also working directly on your wifi-connected tablet and computer. It would be nice of Apple t…
I've only got a cursory understanding of RCS, but in what way is this good for consumers? I can understand how it's good for Google, but aside from Google it's unclear how anyone benefits.
Try `man rcs`. Heh.
I hate name collisions.
* To the extent RCS:
a) makes it easier for users to switch between mobile providers and keep advanced features that used to be offered for lock-in or more $$, or
b) makes it easier for users to switch between the old SMS network and wifi - then, it's not good for mobile telco provider's business models.
* To the extent RCS increases privacy for users (E2E encryption, etc) - then, it's not good for Google's business models.
* To the extent it allows feature-rich messaging to work across ALL major platforms (Android, Web & iOS)- then, it's not good for Apple's platform lock-in.
While I agree that an open, extensible, feature-rich, privacy-aware, cross-platform, cross-network messaging standard is highly desirable - is it correct that RCS (as currently formulated) is a non-starter and, from a strategic perspective, always was?