AT&T Breach Shows Why RCS Can't Be Trusted and the Cons of iOS 18 Adding Support
The article criticizes AT&T data breach, questions RCS lack of encryption, and Apple's support for RCS in iOS 18. It emphasizes the need for end-to-end encryption in messaging services for user privacy and security.
Read original articleThe article discusses the recent AT&T data breach and criticizes the RCS protocol for lacking end-to-end encryption, highlighting the risks associated with non-secure messaging platforms. It questions Apple's decision to support RCS in iOS 18, emphasizing the importance of encryption in messaging services like iMessage and FaceTime. The author argues that RCS should have been built exclusively around end-to-end encryption from the start to ensure user privacy and security. Additionally, the article points out the limitations of carrier-based messaging like RCS, which requires an active SIM card and lacks the ability for devices like iPads to send messages independently. The piece also touches on the debate surrounding the role of carrier-based messaging in the era of modern messaging platforms like iMessage, Signal, and WhatsApp, suggesting that efforts should focus on enhancing existing secure platforms rather than supporting non-encrypted protocols like RCS.