Astonish iPhone Spill Uncovers iOS 18’s Basic Lost Feature
Google isn’t normal the source of modern iPhone and iOS leaks—but it is this time. And it might fair be that this undermines all the benefits we would something else see. Apple has a problem—and truant a colossal shock that issue is not getting settled anytime before long, as Google over all will know. Since Apple can’t do this alone—it needs Google’s help.
The landing page has been changed with that reference evacuated, “more or less” conceding it was coincidental. TechCrunch “has affirmed that the content related to Apple supporting RCS on iOS is still in the source code of the page.”
However, it’s a reference advance down Google’s landing page, one still obvious, that is basic: “For discussions between Google Messages clients, end-to-end encryption is presently empowered on your Android phone by default.”
This is the common misconception with both RCS in common and Apple’s upgrade in specific. RCS is not end-to-end scrambled. So not at all like iMessaging between iPhone clients or Google Informing between Android clients, or more vitally WhatsApping between iPhone and Android clients, RCS between iPhone and Android will not have that level of security.
This is basic since it’s the issue the DOJ highlighted in its claim: “Apple is willing to make the iPhone less secure and less private… Content messages sent from iPhones to Android phones are decoded as a result of Apple’s conduct. If Apple needed to, Apple seem permit iPhone clients to send scrambled messages to Android clients whereas still utilizing iMessage on their iPhone, which would right away move forward the protection and security of iPhone and other smartphone users.”
