Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.mobile.android > #110241 > unrolled thread
| Started by | Wally J <walterjones@invalid.nospam> |
|---|---|
| First post | 2023-11-16 14:47 -0400 |
| Last post | 2023-11-19 11:53 +0000 |
| Articles | 20 on this page of 59 — 12 participants |
Back to article view | Back to comp.mobile.android
Apple announces that RCS support is coming to iPhones in 2024 Wally J <walterjones@invalid.nospam> - 2023-11-16 14:47 -0400
Re: Apple announces that RCS support is coming to iPhones in 2024 Andy Burns <usenet@andyburns.uk> - 2023-11-16 18:57 +0000
Re: Apple announces that RCS support is coming to iPhones in 2024 Andrew <andrew@spam.net> - 2023-11-16 19:39 +0000
Re: Apple announces that RCS support is coming to iPhones in 2024 Andy Burns <usenet@andyburns.uk> - 2023-11-16 19:56 +0000
Re: Apple announces that RCS support is coming to iPhones in 2024 Dave Royal<dave@dave123royal.com> - 2023-11-16 20:16 +0000
Re: Apple announces that RCS support is coming to iPhones in 2024 "Carlos E. R." <robin_listas@es.invalid> - 2023-11-16 22:23 +0100
Re: Apple announces that RCS support is coming to iPhones in 2024 "Carlos E. R." <robin_listas@es.invalid> - 2023-11-16 22:22 +0100
Re: Apple announces that RCS support is coming to iPhones in 2024 Your Name <YourName@YourISP.com> - 2023-11-17 11:07 +1300
Re: Apple announces that RCS support is coming to iPhones in 2024 "Carlos E. R." <robin_listas@es.invalid> - 2023-11-16 23:23 +0100
Re: Apple announces that RCS support is coming to iPhones in 2024 Dave Royal<dave@dave123royal.com> - 2023-11-16 22:53 +0000
Re: Apple announces that RCS support is coming to iPhones in 2024 Patrick <patrick@oleary.com> - 2023-11-16 22:29 -0600
Re: Apple announces that RCS support is coming to iPhones in 2024 Andrew <andrew@spam.net> - 2023-11-17 05:06 +0000
Re: Apple announces that RCS support is coming to iPhones in 2024 Andy Burns <usenet@andyburns.uk> - 2023-11-17 07:12 +0000
Re: Apple announces that RCS support is coming to iPhones in 2024 Andrew <andrew@spam.net> - 2023-11-17 08:01 +0000
Re: Apple announces that RCS support is coming to iPhones in 2024 Jolly Roger <jollyroger@pobox.com> - 2023-11-17 16:45 +0000
Re: Apple announces that RCS support is coming to iPhones in 2024 "Carlos E. R." <robin_listas@es.invalid> - 2023-11-17 13:43 +0100
Re: Apple announces that RCS support is coming to iPhones in 2024 Andrew <andrew@spam.net> - 2023-11-17 18:01 +0000
Re: Apple announces that RCS support is coming to iPhones in 2024 "Carlos E. R." <robin_listas@es.invalid> - 2023-11-17 19:14 +0100
Re: Apple announces that RCS support is coming to iPhones in 2024 Alan Browne <bitbucket@blackhole.com> - 2023-11-17 08:49 -0500
Re: Apple announces that RCS support is coming to iPhones in 2024 Patrick <patrick@oleary.com> - 2023-11-17 10:00 -0600
Re: Apple announces that RCS support is coming to iPhones in 2024 Jolly Roger <jollyroger@pobox.com> - 2023-11-17 17:00 +0000
Re: Apple announces that RCS support is coming to iPhones in 2024 Alan Browne <bitbucket@blackhole.com> - 2023-11-17 14:19 -0500
Re: Apple announces that RCS support is coming to iPhones in 2024 Patrick <patrick@oleary.com> - 2023-11-17 13:32 -0600
Re: Apple announces that RCS support is coming to iPhones in 2024 Alan Browne <bitbucket@blackhole.com> - 2023-11-17 15:06 -0500
Re: Apple announces that RCS support is coming to iPhones in 2024 Patrick <patrick@oleary.com> - 2023-11-17 18:01 -0600
Re: Apple announces that RCS support is coming to iPhones in 2024 Jolly Roger <jollyroger@pobox.com> - 2023-11-18 01:14 +0000
Re: Apple announces that RCS support is coming to iPhones in 2024 Alan Browne <bitbucket@blackhole.com> - 2023-11-18 09:51 -0500
Re: Apple announces that RCS support is coming to iPhones in 2024 Jolly Roger <jollyroger@pobox.com> - 2023-11-17 16:43 +0000
Re: Apple announces that RCS support is coming to iPhones in 2024 Andrew <andrew@spam.net> - 2023-11-17 17:24 +0000
Re: Apple announces that RCS support is coming to iPhones in 2024 Jolly Roger <jollyroger@pobox.com> - 2023-11-17 23:57 +0000
Re: Apple announces that RCS support is coming to iPhones in 2024 Jolly Roger <jollyroger@pobox.com> - 2023-11-17 04:01 +0000
Re: Apple announces that RCS support is coming to iPhones in 2024 Andrew <andrew@spam.net> - 2023-11-17 05:11 +0000
Re: Apple announces that RCS support is coming to iPhones in 2024 Alan Browne <bitbucket@blackhole.com> - 2023-11-17 08:45 -0500
Re: Apple announces that RCS support is coming to iPhones in 2024 Jolly Roger <jollyroger@pobox.com> - 2023-11-17 16:36 +0000
Re: Apple announces that RCS support is coming to iPhones in 2024 Andrew <andrew@spam.net> - 2023-11-17 17:10 +0000
Re: Apple announces that RCS support is coming to iPhones in 2024 Alan Browne <bitbucket@blackhole.com> - 2023-11-17 14:29 -0500
Re: Apple announces that RCS support is coming to iPhones in 2024 Andrew <andrew@spam.net> - 2023-11-17 20:36 +0000
Re: Apple announces that RCS support is coming to iPhones in 2024 Alan Browne <bitbucket@blackhole.com> - 2023-11-17 18:22 -0500
Re: Apple announces that RCS support is coming to iPhones in 2024 Andrew <andrew@spam.net> - 2023-11-18 09:58 +0000
Re: Apple announces that RCS support is coming to iPhones in 2024 Alan Browne <bitbucket@blackhole.com> - 2023-11-18 10:05 -0500
Re: Apple announces that RCS support is coming to iPhones in 2024 Jolly Roger <jollyroger@pobox.com> - 2023-11-17 23:49 +0000
Re: Apple announces that RCS support is coming to iPhones in 2024 Jolly Roger <jollyroger@pobox.com> - 2023-11-17 23:48 +0000
Re: Apple announces that RCS support is coming to iPhones in 2024 Alan Browne <bitbucket@blackhole.com> - 2023-11-18 09:43 -0500
Re: Apple announces that RCS support is coming to iPhones in 2024 Jolly Roger <jollyroger@pobox.com> - 2023-11-17 23:47 +0000
Re: Apple announces that RCS support is coming to iPhones in 2024 "Carlos E. R." <robin_listas@es.invalid> - 2023-11-18 00:59 +0100
Re: Apple announces that RCS support is coming to iPhones in 2024 Jolly Roger <jollyroger@pobox.com> - 2023-11-18 01:09 +0000
Re: Apple announces that RCS support is coming to iPhones in 2024 "Carlos E. R." <robin_listas@es.invalid> - 2023-11-17 18:51 +0100
Re: Apple announces that RCS support is coming to iPhones in 2024 Andrew <andrew@spam.net> - 2023-11-17 18:12 +0000
Re: Apple announces that RCS support is coming to iPhones in 2024 Jolly Roger <jollyroger@pobox.com> - 2023-11-18 00:00 +0000
Re: Apple announces that RCS support is coming to iPhones in 2024 Jolly Roger <jollyroger@pobox.com> - 2023-11-17 23:58 +0000
Re: Apple announces that RCS support is coming to iPhones in 2024 Andy Burns <usenet@andyburns.uk> - 2023-11-18 08:30 +0000
Re: Apple announces that RCS support is coming to iPhones in 2024 sms <scharf.steven@geemail.com> - 2023-11-17 15:50 -0800
Re: Apple announces that RCS support is coming to iPhones in 2024 Jolly Roger <jollyroger@pobox.com> - 2023-11-18 01:10 +0000
Re: Apple announces that RCS support is coming to iPhones in 2024 "Carlos E. R." <robin_listas@es.invalid> - 2023-11-16 22:24 +0100
Re: Apple announces that RCS support is coming to iPhones in 2024 Jörg Lorenz <hugybear@gmx.net> - 2023-11-17 07:20 +0100
Re: Apple announces that RCS support is coming to iPhones in 2024 Jörg Lorenz <hugybear@gmx.net> - 2023-11-17 07:24 +0100
Re: Apple announces that RCS support is coming to iPhones in 2024 Theo <theom+news@chiark.greenend.org.uk> - 2023-11-17 17:01 +0000
Re: Apple announces that RCS support is coming to iPhones in 2024 Alan Browne <bitbucket@blackhole.com> - 2023-11-17 14:33 -0500
Re: Apple announces that RCS support is coming to iPhones in 2024 Theo <theom+news@chiark.greenend.org.uk> - 2023-11-19 11:53 +0000
Page 1 of 3 [1] 2 3 Next page →
| From | Wally J <walterjones@invalid.nospam> |
|---|---|
| Date | 2023-11-16 14:47 -0400 |
| Subject | Apple announces that RCS support is coming to iPhones in 2024 |
| Message-ID | <uj5o3s$3uve4$1@paganini.bofh.team> |
Apple announces that RCS support is coming to iPhone next year https://9to5mac.com/2023/11/16/apple-rcs-coming-to-iphone/ "Apple has announced today that it will adopt the RCS (Rich Communication Services) messaging standard. The feature will launch via a software update "later next year" and bring a wide range of iMessage-style features to messaging between iPhone and Android users. Apple's decision comes amid pressure from regulators and competitors like Google and Samsung. It also comes as RCS has continued to develop and become a more mature platform than it once was." -- Unlike most people, I base my assessments on the facts. It's how intelligent people are taught to think properly.
[toc] | [next] | [standalone]
| From | Andy Burns <usenet@andyburns.uk> |
|---|---|
| Date | 2023-11-16 18:57 +0000 |
| Message-ID | <krn713Fpfe4U1@mid.individual.net> |
| In reply to | #110241 |
Wally J 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?
[toc] | [prev] | [next] | [standalone]
| From | Andrew <andrew@spam.net> |
|---|---|
| Date | 2023-11-16 19:39 +0000 |
| Message-ID | <uj5r4n$2g4e$1@nnrp.usenet.blueworldhosting.com> |
| In reply to | #110244 |
Andy Burns wrote on Thu, 16 Nov 2023 18:57:36 +0000 : >> 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." 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?
[toc] | [prev] | [next] | [standalone]
| From | Andy Burns <usenet@andyburns.uk> |
|---|---|
| Date | 2023-11-16 19:56 +0000 |
| Message-ID | <krnaf8Fpfe4U2@mid.individual.net> |
| In reply to | #110250 |
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 <http://andyburns.uk/misc/rcs-e2ee.png> So is google RCS using a proprietary encryption method, or are TechRadar wrong?
[toc] | [prev] | [next] | [standalone]
| From | Dave Royal<dave@dave123royal.com> |
|---|---|
| Date | 2023-11-16 20:16 +0000 |
| Message-ID | <uj5tak$2dmaq$1@dont-email.me> |
| In reply to | #110254 |
On 16 Nov 2023 19:56:20 +0000 Andy Burns wrote: > > > >So apple to apple will continue to use imessage, doesn't affect or >bother me. > > >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 > ><http://andyburns.uk/misc/rcs-e2ee.png> > >So is google RCS using a proprietary encryption method, or are TechRadar >wrong? Quote: "Apple says that RCS does not currently support encryption that is as strong as iMessage." From https://9to5mac.com/2023/11/16/apple-rcs-coming-to-iphone/ -- (Remove numerics from email address)
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Date | 2023-11-16 22:23 +0100 |
| Message-ID | <krnfj3Fotq4U8@mid.individual.net> |
| In reply to | #110255 |
On 2023-11-16 21:16, Dave Royal wrote:
> On 16 Nov 2023 19:56:20 +0000 Andy Burns wrote:
>>
>>
>>
>> So apple to apple will continue to use imessage, doesn't affect or
>> bother me.
>>
>>
>> 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
>>
>> <http://andyburns.uk/misc/rcs-e2ee.png>
>>
>> So is google RCS using a proprietary encryption method, or are TechRadar
>> wrong?
>
> Quote: "Apple says that RCS does not currently support encryption that is
> as strong as iMessage." From
> https://9to5mac.com/2023/11/16/apple-rcs-coming-to-iphone/
That's a different thing to say.
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Date | 2023-11-16 22:22 +0100 |
| Message-ID | <krnfhaFotq4U7@mid.individual.net> |
| In reply to | #110254 |
On 2023-11-16 20:56, Andy Burns wrote:
> Andrew wrote:
>> Andy Burns wrote:
>> 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."
This is simply not true.
That Apple will implement it or not, is another issue.
>
> My Pixel5a reports E2EE when using RCS to a fellow android user
>
> <http://andyburns.uk/misc/rcs-e2ee.png>
>
> So is google RCS using a proprietary encryption method, or are TechRadar
> wrong?
They are wrong.
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
| From | Your Name <YourName@YourISP.com> |
|---|---|
| Date | 2023-11-17 11:07 +1300 |
| Message-ID | <uj63qn$2en43$1@dont-email.me> |
| In reply to | #110257 |
On 2023-11-16 21:22:50 +0000, Carlos E. R. said: > On 2023-11-16 20:56, Andy Burns wrote: >> Andrew wrote: >>> Andy Burns wrote: > > > >>> 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." > > This is simply not true. The actual RCS Standard itself currently does *not* include end-to-end encryption. Google has added end-to-end encryption themselves in their own app, making it non-standard. We've already seen the problems that can occur when big companies try to make up the rules themselves as the "standard". Microsloth tried to do it with web standards in Internet Explorer, and caused lots of problems for web designers, web browser makers, and users. > That Apple will implement it or not, is another issue. Apple won't be implementing Google's non-standard end-to-end encryption. Apple might implement it's own non-standard encryption or might wait for ti to be officially included in the actual standard. Having competing non-standard methods would simply make it even messier with messaging apps not compatible with each other ... defeating the entire reason there are official standards in the first place! >> My Pixel5a reports E2EE when using RCS to a fellow android user >> >> <http://andyburns.uk/misc/rcs-e2ee.png> >> >> So is google RCS using a proprietary encryption method, or are TechRadar wrong? > > They are wrong.
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Date | 2023-11-16 23:23 +0100 |
| Message-ID | <krnj3cFotq4U12@mid.individual.net> |
| In reply to | #110267 |
On 2023-11-16 23:07, Your Name wrote:
> On 2023-11-16 21:22:50 +0000, Carlos E. R. said:
>
>> On 2023-11-16 20:56, Andy Burns wrote:
>>> Andrew wrote:
>>>> Andy Burns wrote:
>>
>>
>>
>>>> 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."
>>
>> This is simply not true.
>
> The actual RCS Standard itself currently does *not* include end-to-end
> encryption. Google has added end-to-end encryption themselves in their
> own app, making it non-standard.
>
> We've already seen the problems that can occur when big companies try to
> make up the rules themselves as the "standard". Microsloth tried to do
> it with web standards in Internet Explorer, and caused lots of problems
> for web designers, web browser makers, and users.
>
>
>
>> That Apple will implement it or not, is another issue.
>
> Apple won't be implementing Google's non-standard end-to-end encryption.
> Apple might implement it's own non-standard encryption or might wait for
> ti to be officially included in the actual standard. Having competing
> non-standard methods would simply make it even messier with messaging
> apps not compatible with each other ... defeating the entire reason
> there are official standards in the first place!
Ok then, not standard. Still I understand the google app will simply
drop encryption when talking to a correspondent that doesn't support it.
So not a propblem
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
| From | Dave Royal<dave@dave123royal.com> |
|---|---|
| Date | 2023-11-16 22:53 +0000 |
| Message-ID | <uj66hc$2f43q$1@dont-email.me> |
| In reply to | #110267 |
On 17 Nov 2023 11:07:19 +1300 Your Name wrote: >On 2023-11-16 21:22:50 +0000, Carlos E. R. said: > >> On 2023-11-16 20:56, Andy Burns wrote: >>> Andrew wrote: >>>> Andy Burns wrote: >> >> >> >>>> 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." >> >> This is simply not true. > >The actual RCS Standard itself currently does *not* include end-to-end >encryption. Google has added end-to-end encryption themselves in their >own app, making it non-standard. > >We've already seen the problems that can occur when big companies try >to make up the rules themselves as the "standard". Microsloth tried to >do it with web standards in Internet Explorer, and caused lots of >problems for web designers, web browser makers, and users. > > > >> That Apple will implement it or not, is another issue. > >Apple won't be implementing Google's non-standard end-to-end >encryption. Apple might implement it's own non-standard encryption or >might wait for ti to be officially included in the actual standard. >Having competing non-standard methods would simply make it even messier >with messaging apps not compatible with each other ... defeating the >entire reason there are official standards in the first place! Google use the Signal e2ee protocol according to this: <https://www.gstatic.com/messages/papers/messages_e2ee.pdf> <https://signal.org/docs/> -- (Remove numerics from email address)
[toc] | [prev] | [next] | [standalone]
| From | Patrick <patrick@oleary.com> |
|---|---|
| Date | 2023-11-16 22:29 -0600 |
| Message-ID | <uj6q7d$24kpj$1@novabbs.org> |
| In reply to | #110267 |
On Fri, 17 Nov 2023 11:07:19 +1300, Your Name wrote: > We've already seen the problems that can occur when big companies try > to make up the rules themselves as the "standard". Microsloth tried to > do it with web standards in Internet Explorer, and caused lots of > problems for web designers, web browser makers, and users. Standards work well when applied to all three. Microsoft. Google. Apple. Which of the three, especially considering almost all of Android is AOSP, do you think most "try to make up the rules themselves as the standard?" >> That Apple will implement it or not, is another issue. > > Apple won't be implementing Google's non-standard end-to-end > encryption. Apple might implement it's own non-standard encryption or > might wait for ti to be officially included in the actual standard. This seems to be the case given Google seems to have done it on their own. https://arstechnica.com/gadgets/2021/06/google-enables-end-to-end-encryption-for-androids-default-sms-rcs-app/ "Google has announced that end-to-end encryption is rolling out to users of Google Messages, Android's default SMS and RCS app." They improved it since that initial E2EE rollout a few years ago. https://www.theverge.com/2023/8/8/23824800/google-messages-rcs-end-to-end-encryption-default-group "RCS messages in Google's Messages app will now be fully end-to-end-encrypted by default" > Having competing non-standard methods would simply make it even messier > with messaging apps not compatible with each other ... defeating the > entire reason there are official standards in the first place! The unanswered question is what will Apple's implementation be? https://www.axios.com/2023/11/16/apple-messaging-imessage-rcs-iphone "This will work alongside iMessage, which will continue to be the best" "It's unclear exactly which RCS features Apple will support, and how it will do so. Apple declined to comment beyond its statement" For those who care about bubbles there's a tiny bit more about it here. https://edition.cnn.com/2023/11/16/tech/apple-adopt-new-messaging-standard/index.html "The move, however, doesn't necessarily mean the green bubbles (Android or other users) and blue bubbles (Apple users) that are displayed when messaging someone on the other platform will go away anytime soon. Chatterjee said that keeping the colors is an Apple marketing strategy that will likely continue, despite the shift to the RCS standard. 'The blue bubble is a badge of the Apple tribe, and this distinctive identity, as well as the company's iMessage platform, is not going anywhere anytime soon,' Chatterjee said." The unanswered question is how much of a Frankenstein will Apple make it as it seems to be more in Apple's interest to implement it as bad as they can.
[toc] | [prev] | [next] | [standalone]
| From | Andrew <andrew@spam.net> |
|---|---|
| Date | 2023-11-17 05:06 +0000 |
| Message-ID | <uj6scm$2i8r$1@nnrp.usenet.blueworldhosting.com> |
| In reply to | #110254 |
Andy Burns wrote on Thu, 16 Nov 2023 19:56:20 +0000 : >> "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. I think Apple will implement it but in a way that you might not like. Especially given they're being forced to adopt RCS standards by others. What if Apple allows 3rd-party RCS messaging apps but still only one default messenger (just as Android only allows one default messenger)? Will the user need to manually switch messengers to access RCS chats? If that's the implementation, do you think that will be an improvement?
[toc] | [prev] | [next] | [standalone]
| From | Andy Burns <usenet@andyburns.uk> |
|---|---|
| Date | 2023-11-17 07:12 +0000 |
| Message-ID | <kroi3bF40d3U1@mid.individual.net> |
| In reply to | #110276 |
Andrew wrote: > I think Apple will implement it but in a way that you might not like. > Especially given they're being forced to adopt RCS standards by others. > > What if Apple allows 3rd-party RCS messaging apps but still only one > default messenger (just as Android only allows one default messenger)? When I set Google Messages as my default messenger, it supports multiple types of message (RCS/SMS/MMS ... I just happen to mostly ignore the latter) > Will the user need to manually switch messengers to access RCS chats? > If that's the implementation, do you think that will be an improvement? I doubt they'll do that, at present an apple user doesn't have to choose a different app in order to send an SMS to me, their phone realises I'm not an imessage user, so it falls back to SMS. Next year I expect it will have two levels of fallback, firstly to RCS, and secondly to SMS, if someone else chooses to pay to send me an MMS I don't mind, but they'll have no need to pay once apple has RCS.
[toc] | [prev] | [next] | [standalone]
| From | Andrew <andrew@spam.net> |
|---|---|
| Date | 2023-11-17 08:01 +0000 |
| Message-ID | <uj76k7$q9k$1@nnrp.usenet.blueworldhosting.com> |
| In reply to | #110285 |
Andy Burns wrote on Fri, 17 Nov 2023 07:12:44 +0000 : >> I think Apple will implement it but in a way that you might not like. >> Especially given they're being forced to adopt RCS standards by others. >> >> What if Apple allows 3rd-party RCS messaging apps but still only one >> default messenger (just as Android only allows one default messenger)? > > When I set Google Messages as my default messenger, it supports multiple > types of message (RCS/SMS/MMS ... I just happen to mostly ignore the latter) > >> Will the user need to manually switch messengers to access RCS chats? >> If that's the implementation, do you think that will be an improvement? > > I doubt they'll do that, at present an apple user doesn't have to choose > a different app in order to send an SMS to me, their phone realises I'm > not an imessage user, so it falls back to SMS. Next year I expect it > will have two levels of fallback, firstly to RCS, and secondly to SMS, > if someone else chooses to pay to send me an MMS I don't mind, but > they'll have no need to pay once apple has RCS. What some foresee is what's already been predicted in the news that Apple will implement an unworkable solution that follows the letter of the law. "Apple has a tendency to follow the letter of the law... while also kicking and screaming about it. When similar EU legislation pushed it into offering repair services, it was an expensive process that required users to lug around bulky equipment. Apple was also reluctant to change the iPhone's charging ports to the widespread USB-C standard, only doing so this year once legislation forced its hand." https://www.wired.com/story/apple-adding-support-for-rcs-could-kill-sms/ My suspicion is Apple will either create their own separate iRCS messenger, or maybe open up the walled garden to a few compliant 3rd-party messenger apps which follow Apple's strict "letter of the law" rules but which the user has to also climb over glowing coals in order to switch to it (given there can only be one default text messenger on any mobile device). You have a more noble prediction of what Apple will implement in iOS 18 (since they said "later next year" & iOS 18 may likely be about then). I hope you are closer to what Apple will implement under duress than I am.
[toc] | [prev] | [next] | [standalone]
| From | Jolly Roger <jollyroger@pobox.com> |
|---|---|
| Date | 2023-11-17 16:45 +0000 |
| Message-ID | <krpjkrFc25iU4@mid.individual.net> |
| In reply to | #110286 |
On 2023-11-17, Andrew <andrew@spam.net> wrote: > Andy Burns wrote on Fri, 17 Nov 2023 07:12:44 +0000 : > >>> I think Apple will implement it but in a way that you might not >>> like. Especially given they're being forced to adopt RCS standards >>> by others. >>> >>> What if Apple allows 3rd-party RCS messaging apps but still only one >>> default messenger (just as Android only allows one default >>> messenger)? >> >> When I set Google Messages as my default messenger, it supports >> multiple types of message (RCS/SMS/MMS ... I just happen to mostly >> ignore the latter) >> >>> Will the user need to manually switch messengers to access RCS >>> chats? If that's the implementation, do you think that will be an >>> improvement? >> >> I doubt they'll do that, at present an apple user doesn't have to >> choose a different app in order to send an SMS to me, their phone >> realises I'm not an imessage user, so it falls back to SMS. Next >> year I expect it will have two levels of fallback, firstly to RCS, >> and secondly to SMS, if someone else chooses to pay to send me an MMS >> I don't mind, but they'll have no need to pay once apple has RCS. > > What some foresee is what's already been predicted in the news that > Apple will implement an unworkable solution that follows the letter of > the law. There is no RCS law. And Apple is on record saying RCS will be supported in the Apple Messages app. You're chock full of shit. -- E-mail sent to this address may be devoured by my ravenous SPAM filter. I often ignore posts from Google. Use a real news client instead. JR
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Date | 2023-11-17 13:43 +0100 |
| Message-ID | <krp5g9F7ddpU2@mid.individual.net> |
| In reply to | #110276 |
On 2023-11-17 06:06, Andrew wrote:
> Andy Burns wrote on Thu, 16 Nov 2023 19:56:20 +0000 :
>
>>> "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.
>
> I think Apple will implement it but in a way that you might not like.
> Especially given they're being forced to adopt RCS standards by others.
>
> What if Apple allows 3rd-party RCS messaging apps but still only one
> default messenger (just as Android only allows one default messenger)?
There is another item to consider: The EU will probably force all
message system to coordinate somehow and send/receive messages from/to
other message systems, somehow.
This includes the Apple imessage app. It will probably be forced to
interact with WhatsApp, for instance.
Will Apple restrict this to EU only?
>
> Will the user need to manually switch messengers to access RCS chats?
> If that's the implementation, do you think that will be an improvement?
See above.
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
| From | Andrew <andrew@spam.net> |
|---|---|
| Date | 2023-11-17 18:01 +0000 |
| Message-ID | <uj89p5$2vg2$1@nnrp.usenet.blueworldhosting.com> |
| In reply to | #110287 |
Carlos E. R. wrote on Fri, 17 Nov 2023 13:43:53 +0100 : >> What if Apple allows 3rd-party RCS messaging apps but still only one >> default messenger (just as Android only allows one default messenger)? > > There is another item to consider: The EU will probably force all > message system to coordinate somehow and send/receive messages from/to > other message systems, somehow. Thank you for bringing up that additional item to consider which is that this RCS letter of the law may affect not only Apple but Meta & others too. > This includes the Apple imessage app. It will probably be forced to > interact with WhatsApp, for instance. Based on the twenty or thirty articles I've read on this, it seems Apple may have decided not to explain yet how it will "interact" with other messengers - nor even how it will interact with iMessage other than every cite saying that Apple said RCS will "exist separately" from iMessage. You can be sure Apple executives know what "exists separately" means (even if the rest of us will just have to wait until iOS 18 to find out). > Will Apple restrict this to EU only? All we know is Apple said in every article I could find that RCS will "exist separately" from iMessage. They didn't say anything about the EU. What does it mean to "exist separately" & still follow the EU guidelines?
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Date | 2023-11-17 19:14 +0100 |
| Message-ID | <krposmFcc4uU2@mid.individual.net> |
| In reply to | #110310 |
On 2023-11-17 19:01, Andrew wrote:
> Carlos E. R. wrote on Fri, 17 Nov 2023 13:43:53 +0100 :
>
>>> What if Apple allows 3rd-party RCS messaging apps but still only one
>>> default messenger (just as Android only allows one default messenger)?
>>
>> There is another item to consider: The EU will probably force all
>> message system to coordinate somehow and send/receive messages from/to
>> other message systems, somehow.
>
> Thank you for bringing up that additional item to consider which is that
> this RCS letter of the law may affect not only Apple but Meta & others too.
>
>> This includes the Apple imessage app. It will probably be forced to
>> interact with WhatsApp, for instance.
>
> Based on the twenty or thirty articles I've read on this, it seems Apple
> may have decided not to explain yet how it will "interact" with other
> messengers - nor even how it will interact with iMessage other than every
> cite saying that Apple said RCS will "exist separately" from iMessage.
>
> You can be sure Apple executives know what "exists separately" means
> (even if the rest of us will just have to wait until iOS 18 to find out).
Maybe they will wait to see what the EU will say, and then decide what
to actually do. That way thy avoid saying something and then having to
double back depending on what the EU says. It is what I would do, but
hey, I do not work for Apple :-)
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
| From | Alan Browne <bitbucket@blackhole.com> |
|---|---|
| Date | 2023-11-17 08:49 -0500 |
| Message-ID | <7cK5N.29247$Wzw6.6519@fx13.iad> |
| In reply to | #110276 |
On 2023-11-17 00:06, Andrew wrote: > Andy Burns wrote on Thu, 16 Nov 2023 19:56:20 +0000 : > >>> "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. > > I think Apple will implement it but in a way that you might not like. > Especially given they're being forced to adopt RCS standards by others. > > What if Apple allows 3rd-party RCS messaging apps but still only one > default messenger (just as Android only allows one default messenger)? > > Will the user need to manually switch messengers to access RCS chats? > If that's the implementation, do you think that will be an improvement? RCS is still rooted in the phone system as the common communications element whereas iMessage (and other iCloud services) are internet based services. So if you're on an iPhone or Mac (or other Apple device) and want to send a text to an Android user, if the phone number isn't in someone's iCloud account it is assumed to be non-Apple and the call is routed as any SMS/MMS (and soon RCS) message: via the phone system - so a Mac would use the user's iPhone to send the message.[1] All this is transparent to the user as long as he has at least one phone device and account that can do SMS/MMS/RCS. Not sure if Apple could stop a 3rd party app from doing RCS - however that might not support the case of a user doing the RCS from a separate device (a Mac). Expect the Apple eco-system to continue to expand in capability and features all over, including in iMessage while also adding RCS. [1] Apple do this so well that: Once upon a time I left my iPhone at work (30 km away). From my Mac I could still send SMS/MMS to Android users. The Mac would delegate to my iPhone and conduct the exchange via the internet. (Won't do voice calls, alas). -- “Markets can remain irrational longer than your can remain solvent.” - John Maynard Keynes.
[toc] | [prev] | [next] | [standalone]
| From | Patrick <patrick@oleary.com> |
|---|---|
| Date | 2023-11-17 10:00 -0600 |
| Message-ID | <uj82nf$3do6v$1@novabbs.org> |
| In reply to | #110290 |
On Fri, 17 Nov 2023 08:49:54 -0500, Alan Browne wrote: > RCS is still rooted in the phone system as the common communications > element whereas iMessage (and other iCloud services) are internet based > services. > > So if you're on an iPhone or Mac (or other Apple device) and want to > send a text to an Android user, if the phone number isn't in someone's > iCloud account it is assumed to be non-Apple and the call is routed as > any SMS/MMS (and soon RCS) message: via the phone system - so a Mac > would use the user's iPhone to send the message.[1] > > All this is transparent to the user as long as he has at least one phone > device and account that can do SMS/MMS/RCS. Not sure if Apple could > stop a 3rd party app from doing RCS - however that might not support the > case of a user doing the RCS from a separate device (a Mac). > > Expect the Apple eco-system to continue to expand in capability and > features all over, including in iMessage while also adding RCS. > > [1] Apple do this so well that: Once upon a time I left my iPhone at > work (30 km away). From my Mac I could still send SMS/MMS to Android > users. The Mac would delegate to my iPhone and conduct the exchange via > the internet. (Won't do voice calls, alas). You say this as if it's a big deal when any Internet service can do that. It's not "Apple" doing it. Android does it too. So does Windows do it. Even Linux does it. You're all excited about logging into a server farm.
[toc] | [prev] | [next] | [standalone]
Page 1 of 3 [1] 2 3 Next page →
Back to top | Article view | comp.mobile.android
csiph-web