Nostr Web Client

#android #google #apple

Yey look! Google is promoting open standard that is used for intercorponation communication!

https://www.android.com/get-the-message/

RCS is supposed to be implemented by each network operator so presumably it won't be another iMessage situation... but!

Also google:

> RCS, though, can enable end-to-end encryption – and RCS conversations are end-to-end encrypted between Messages by Google users.

Just wait till **not** E2E messages will be marked dangerous AND SCARY by android **default** Messages (by Google but it doesnt say it in the name) application.

That is not all! Guess what:

> [... ]T-Mobile announced today that its RCS offering is now powered by Google’s Jibe platform.

> Carriers can either have Google power the RCS backend/servers or use their own infrastructure. T-Mobile did both depending on the Android device:

https://9to5google.com/2023/09/21/t-mobile-rcs-google-jibe/

Just... I can't... #destroygoogle anyone?

Reply to this note

Please Login to reply.

Discussion

The Beave 2y ago

Uh, no. They are causing an issue since they (goog) want to host all messages through their servers, and the cell carriers are not having that. It's also horrible for privacy to do that. E2EE is good, but, it's nearly useless if you can data mine all the Metadata of messaging like FB does with whatsapp. So, I see the push to RCS as a net negative, as it is an attempt to centralize all messaging through servers that will profile you via even more of your messaging since the Metadata is often more important than the content.