As an Android user, it'd be nice if replying "No" to "Do you want RCS?" meant "Never ask me again" and wasn't just interpreted as "ask me again in next week and every week thereafter".
why don't you want RCS?
Apple announces that RCS support is coming to iPhone next year
301–310 of 729 posts
Re: Apple announces that RCS support is coming to iPhone next year
#302Please let users be able to disable RCS support. One nice thing about iMessage is that lacks spam. It is the only platform where i don't get spammed by bots.
I still get plenty of iMessage spam. From this morning:
"Your USPS package could not be delivered. please check this link for more information: https://...."
Re: Apple announces that RCS support is coming to iPhone next year
#303It's funny that everyone says "green bubble shame". Green bubble never meant "Android". It just meant SMS. I get green bubbles with iPhones sometimes when my data isn't working but SMS is. The whole point was to tell you that you may be charged for the message because some carries charge per SMS.
Re: Apple announces that RCS support is coming to iPhone next year
#304Earlier quoted context omitted.
> the only messaging app on Android that fully supports RCS is Messages by Google Plus, unless they fixed it, if you enable RCS and then regret it and disable it again, anybody who texted with you via RCS will no longer be able to text you at all. Things won't revert to SMS. This bit me pretty hard, but I finally fixed it by changing my phone number.
> Plus, unless they fixed it, if you enable RCS and then regret it and disable it again, anybody who texted with you via RCS will no longer be able to text you at all. On a relative's phone, the messages app simply enabled RCS automatically without asking (and displayed a screen proudly saying it did so). Does that means that this phone will never receive SMS again from RCS users, even though we have carefully always…
For me, it only affected phone numbers that I had exchanged texts with that also had RCS enabled. Phones that didn't have it enabled, or numbers I had not exchanged texts with, were unaffected.
This was quite a while ago. They may very well have fixed the issue since then.
And yes, I noticed they enable RCS by default. Since then, the first thing I have done with new phones is to disable RCS. If you do that before sending/receiving any texts, then there is no issue.
Re: Apple announces that RCS support is coming to iPhone next year
#305Earlier quoted context omitted.
The telcos don’t actually provide E2EE. That layer is offered by Google itself, and RCS carries encrypted data, last I checked. Not sure if Apple is going to interoperate with it.
> That layer is offered by Google itself > Not sure if Apple is going to interoperate with it. Only if both users in a 1:1 chat are using Google Messages. E2EE is not possible even with Samsung Messages, so I highly doubt it.
Google finished rolling out RCS group chat E2EE in August.
Re: Apple announces that RCS support is coming to iPhone next year
#306Excellent. The next step is for Google to release a free and open source way for Android developers to build apps that send RCS messages. Currently, the only messaging app on Android that fully supports RCS is Messages by Google, which is closed source and requires Google Play Services to activate RCS features. Also, end-to-end encryption is not part of the RCS specification, but is a proprietary extension to RCS tha…
> the only messaging app on Android that fully supports RCS is Messages by Google Plus, unless they fixed it, if you enable RCS and then regret it and disable it again, anybody who texted with you via RCS will no longer be able to text you at all. Things won't revert to SMS. This bit me pretty hard, but I finally fixed it by changing my phone number.
You can deregister your phone number from Messages by Google here:
https://messages.google.com/disable-chat
This is similar to Apple's iMessage deregistration page.[1]
Google has been funneling RCS messages through its own servers to bypass wireless carriers, which were slow or unwilling to directly support RCS.[2] Unfortunately, this has centralized RCS communications through Google and allowed Google to make end-to-end encryption available to RCS users as a proprietary extension that Google never contributed back to the RCS Universal Profile specification.[3]
For RCS on Android to be decentralized again, your wireless carrier would need to support RCS on the network level and Android would also need to implement RCS in a way that does not require interaction with Google servers. This would make deregistration unnecessary.
[1] https://selfsolve.apple.com/deregister-imessage/
[2] https://www.extremetech.com/mobile/302020-google-will-bypass...
[3] https://appleinsider.com/articles/23/11/16/apples-flavor-of-...
Re: Apple announces that RCS support is coming to iPhone next year
#307Earlier quoted context omitted.
Very much not a trope. I personally know multiple people who refuse to text green bubbles, to the point of refusing dates from people who have Android.
> I personally know multiple people who refuse to text green bubbles, to the point of refusing dates from people who have Android. Those people don't sound like people worth knowing. Ignorant and judgy to say the least.
Life isn't so simple. What if that person is your boss or your client, or someone you love?
Re: Apple announces that RCS support is coming to iPhone next year
#308Earlier quoted context omitted.
Bingo. The cartel was so focused on trying to save their existing money printing machine they took their eye off the ball and refused to disrupt themselves. The cable television industry did the exact same thing. If they’d been willing to go OTT a decade ago and not force agreements based on geolocation, a lot of the streaming services that exist wouldn’t even need to exist today.
> The cable industry did the exact same thing. Kinda but not really. The cable providers were and continue to be hamstrung by the networks who force the cable providers to buy channel packages. Cable never had the leverage to, say, tell Disney that they only want to offer ESPN but not the 10 other Disney branded networks being offered. It was often all or nothing.
That was true until the cable companies themselves bought networks. Comcast owning NBC Universal, the various cable associations with the artists formerly known as Time Warner, the various local station and sports station roll ups for the various providers, all make them entwined.
And the networks were already offering online access to their content via TV Everywhere. They didn’t want to do the geolocation thing, that was all requirements of the cable companies (the issues with the network broadcasters like ABC, CBS, NBC and Fox are much more complex).
In fact, you could (and I would) argue that it was the cable companies insistence on maintaining their defacto monopolies on who could get what service where (because there was never consumer choice in who your cable provider is, unless you count satellite, which I do not) that pushed the networks hands into creating their own competing OTT services based on the content they owned. Because as people cut the cord, the networks weren’t going to watch their businesses completely go up in flames. Now, should they have done that sooner and more aggressively (HBO did it best and earliest with HBO Now as a companion to HBO Go — a move that earned them the ire of the cable industry, the same industry who often refused to let HBO Go subscribers who paid the cable companies directly for HBO, do things like access the service on an Xbox b.c they didn’t like the idea of people not paying a $5 a month fee for an extra box), yes. 1000%
But let’s not pretend like the cable companies were without leverage. If they’d acted decisively and disrupted themselves early enough, they were the ones with the direct relationship with the customer, not the networks. They were the ones who could have created their own bundles of OTT content. But no, they refused until it was too late and got to see the whole industry bleed itself and for live content to essentially die.
Re: Apple announces that RCS support is coming to iPhone next year
#309Earlier quoted context omitted.
> what you can do is different Can you talk a bit more about how iMessage is fundamentally diferent than SMS on the functionality level? Is it like "Signal" different or is it like "different" different? Edit: bonus points if you can offer why iMessage is able to be the skeleton key into your iPhone, as often it and WebKit seem to be behind most of the serious 0-days...
> Can you talk a bit more about how iMessage is fundamentally diferent than SMS on the functionality level It's different in the same way every messaging app is different from SMS: * Group chats, with custom group names and icons * High quality images/videos * Reactions * Stickers * Rich link previews * Threads * etc. etc. > why iMessage is able to be the skeleton key into your iPhone I don't think a lot (any?) of th…
Isnt that the reason sandboxes exist? I just feel like these thins happen way less often with Signal and [shudder] Whatsapp...
Re: Apple announces that RCS support is coming to iPhone next year
#310Earlier quoted context omitted.
I'm mostly just talking about the noxious white-on-green color they chose for cross-platform chat bubbles. It's a great example of hostile architecture. RCS fixes the cost / reliability problems of SMS, so that annoying color choice will be the only thing they have left to make imessage users feel superior.
> RCS fixes the cost / reliability problems of SMS, It doesn’t fix the end to end encryption problem unless google opens up their system.
https://appleinsider.com/articles/23/11/16/apples-flavor-of-...
Huh, pleasantly surprised Apple is taking up the mantle on something cross-platform. Nice.