Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Andy Burns Newsgroups: comp.mobile.android,misc.phone.mobile.iphone Subject: Re: Apple announces that RCS support is coming to iPhones in 2024 Date: Thu, 16 Nov 2023 19:56:20 +0000 Lines: 39 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net o0lXOlBtXxIwCgOuoQAbSgFhv4JYJ3YIGxLvfpbu7RV+yGqqZ8 Cancel-Lock: sha1:W9vyHRyGmCqUpg3YdsY/KpTRjmQ= sha256:ohMRxP/3fxiVolK/4+ePu8e23e6ynPV0kNFyWWSHT8A= User-Agent: Mozilla Thunderbird Content-Language: en-GB In-Reply-To: Xref: csiph.com comp.mobile.android:110254 misc.phone.mobile.iphone:182557 Andrew wrote: > Andy Burns wrote: > >>> Apple announces that RCS support is coming to iPhone next year >>> https://9to5mac.com/2023/11/16/apple-rcs-coming-to-iphone/ >> >> A good thing from Android users PoV, and hopefully from Apple users PoV >> too. Difficult to see any downside once it's up and running? > > The downside is to iMessage but it seems Apple has already planned for that > given the article provided this direct-from-Apple cautionary warning. > > "RCS will simply supplant SMS and MMS and exist separately from iMessage > when available." So apple to apple will continue to use imessage, doesn't affect or bother me. > Later on the article reiterates "This is not Apple opening up iMessage to > other platforms. Instead, it's the company adopting RCS separately from > iMessage." > > What do those cautionary warnings from Apple tell you about implementation? Not much, until the dog gets to see the rabbit. One thing I noticed in TechRadar's reporting of the RCS news "There is, naturally, a wrinkle here. The RCS standard still doesn't support end-to-end encryption." My Pixel5a reports E2EE when using RCS to a fellow android user So is google RCS using a proprietary encryption method, or are TechRadar wrong?