anonymouse

soundsinmotion said:

Actually this is a very common trick you can do in photography, this isn’t possible when taking a picture on the iPhone unless you know how to do it. You’re either using an app or photoshop to stitch the 3 images together. I’ve done images like this for years. Nothing new and it’s an intentional trick not something the iPhone did by mistake. It says she’s a comedian and her instagram is wheatpraylove. Yeah this was an intentional joke not something the iPhone mistakenly did.

gatorguy said:

anonymouse said:

Spencer314 said:

This is as it should be. The Apple-to-Apple features are just going to continue being more advanced and predictable than Apple-to-RCS, and the color coding helps know what doesn't work. Better, though, might be a third color to represent RCS or end-to-end encryption (when that is supported with a new RCS standard), though perhaps that would be going too far. 

I think it needs to be a third color (pink, and purple for E2EE RCS if and when that actually comes) and, until they actually release it with green bubbles, I still believe Apple will see the utility in distinguishing RCS from SMS, as well as from iMessage.

Apple says nope. Blue and green just like before, only distinguishing iMessages from not. 

Spencer314 said:

This is as it should be. The Apple-to-Apple features are just going to continue being more advanced and predictable than Apple-to-RCS, and the color coding helps know what doesn't work. Better, though, might be a third color to represent RCS or end-to-end encryption (when that is supported with a new RCS standard), though perhaps that would be going too far. 

gatorguy said:

anonymouse said:

gatorguy said:

davidw said:

gatorguy said:

chasm said:

Anilu_777 said:

I still wonder why Google even cares about this and then why it’s pushing so hard. I don’t trust Google. 

Oh, let me clarify that for you. Google wants to a) collect data from messages, and b) push rich advertising into messages, which of course they would benefit from.

I didn’t make this up — it’s been referred to in previous articles talking about Google’s version of RCS. Apple would never allow crap like that, so Google was never going to get Apple to adopt their version of RCS.

I am actually starting to feel bad for Android users, because if Google gets its way their experience in messaging is about to get a lot crappier.

Google cannot collect user data from Google Messages RCS. End of story. So yeah, you made that part up.

Can RCS be used for delivering rich media which could include advertising? Yup, but that's not a Google exclusive.

You're the one making things up. We went through this once before and you are still so blindly loyal to Google that you don't want to see what is plainly clear for everyone else.

Google E2EE with their version of RCS, can only exist if both the sender and receiver are using Google Messages. All Google Messages uses Google servers and this is what allows Google version of RCS to have E2EE. Much like how all iMessage users are all using Apple servers and WhatsApp users are all using WhatsApp servers. If either the sender or receiver are not using Google Messages, the message is no longer E2EE. Even Google Messages will default to SMS, so the receiver can still get the text message. And this will most likely happen in a group chat where if one of the person in the chat is not using Google Messages, the whole chat is no longer E2EE for anyone in it. So to say that Google can not collect users data from Google Messages is making things up. You can't possibly believe that Google can not collect users data from unencrypted messages, that they are hosting on their own servers.   

This is why when Apple adopts RCS, there will still be no E2EE between iMessage and Google Messager. They exist on two different companies servers and uses different protocol. Google RCS E2EE is not a standard. And neither is Apple iMessage E2EE. However, when Apple adopts RCS, both iMessage users and Google Messages user will be able to text each other using the standard RCS. Much like how they can text each other using SMS now. And both Apple and Google can collect users data. But it's mainly Google collecting users data that is the concern for most. And you can bet that if the telecoms adopts a standard E2EE protocol, Google will not be all too happy, as once that happens as Android users no longer be locked into using Google Messages to receive RCS messages that are E2EE. Once E2EE protocol is a standard, it will be avialable for every messaging service to use. Which is what Apple is waiting for.  

To repeat. Google cannot access user data or message contents in a Google RCS chat.  A fact the first time I said it. 

Sure, and I know you like to try to shout down bad news, but you keep harping on that very narrow point to distract from the facts that if the chat becomes unencrypted they can and that they still know who the users are and can use that information to map the connections between them. Sometimes the meta data is more valuable than the actual data.

Of course it does and it doesn't matter whose messaging you use. Once the chat is no longer encrypted, maybe inadequate cross-compatibilty or an old leaky standard in use, then the provider can see who the users are even if encryption is the default. It's funny if you don't think that applies to your Apple messaging services just as surely as Google Messsages.