Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

People are just eating what Google says raw. Apple will just need to implement RCS and everything will be better.

Don't worry that the only universally available RCS relay is operated by Google and encryption is a part of a non-standard Google extension. So Google wants Apple to hand all messages over to Google.

For fun, Apple should propose to implement RCS but only if Google agrees to use the Apple relay. No chance it would ever be accepted.



> Apple will just need to implement RCS and everything will be better.

I used it for a bit, but learned that RCS is not something I want even a little.


And the included encryption is beyond useless if it is instantly dropped when sent to a device that doesn’t understand the new protocol. That’s such a huge security vulnerability that it is just security theater to encrypt in the first place. Though I’m sure it has to do something with all those messages going through google’s servers.


That's also true for iMessage?

If you actually care about e2ee you'd use Signal.


Actually it’s not true for iMessage. Messages switches to SMS/MMS if the phone doesn’t support iMessage or has it disabled, but if it’s an iMessage it’s an iMessage—encryption and all—and you can see in advance if that is the case.

That said I don’t know what Google’s messenger actually does when it drops the encryption on RCS messages. Is there a visual distinction between encrypted RCS and unencrypted RCS on the sender end if it is just dropping the encryption on the receiving end as a fallback?


Yes, the send icon changes.


Amen. Plus, the whole reason RCS was built was to allow carriers to keep charging for messages.


Yeah, I'm on android and RCS is not enabled.




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: