Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.mobile.android > #109304 > unrolled thread
| Started by | Stan Brown <the_stan_brown@fastmail.fm> |
|---|---|
| First post | 2023-10-28 11:10 -0700 |
| Last post | 2023-11-01 09:54 +0100 |
| Articles | 15 on this page of 95 — 11 participants |
Back to article view | Back to comp.mobile.android
RCS chats Stan Brown <the_stan_brown@fastmail.fm> - 2023-10-28 11:10 -0700
Re: RCS chats Andy Burns <usenet@andyburns.uk> - 2023-10-28 19:22 +0100
Re: RCS chats Bob Henson <bob.henson@outlook.com> - 2023-10-28 19:50 +0100
Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-10-28 23:16 +0200
Re: RCS chats Andy Burns <usenet@andyburns.uk> - 2023-10-29 07:04 +0000
Re: RCS chats Jörg Lorenz <hugybear@gmx.net> - 2023-10-29 08:10 +0100
Re: RCS chats KenW <ken1943@invalid.net> - 2023-10-28 13:43 -0600
Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-10-28 23:11 +0200
Re: RCS chats Jörg Lorenz <hugybear@gmx.net> - 2023-10-29 08:00 +0100
Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-10-29 12:54 +0100
Re: RCS chats Jörg Lorenz <hugybear@gmx.net> - 2023-10-29 16:05 +0100
Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-10-29 20:09 +0100
Re: RCS chats Jörg Lorenz <hugybear@gmx.net> - 2023-10-29 21:34 +0100
Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-10-30 19:12 +0100
Re: RCS chats Dave Royal<dave@dave123royal.com> - 2023-10-30 18:34 +0000
Re: RCS chats Jörg Lorenz <hugybear@gmx.net> - 2023-10-31 09:59 +0100
Re: RCS chats Jörg Lorenz <hugybear@gmx.net> - 2023-10-31 02:51 +0100
Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-10-31 14:49 +0100
Re: RCS chats Jörg Lorenz <hugybear@gmx.net> - 2023-10-31 16:53 +0100
Re: RCS chats Frank Slootweg <this@ddress.is.invalid> - 2023-10-30 15:26 +0000
Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-10-30 19:18 +0100
Re: RCS chats Jörg Lorenz <hugybear@gmx.net> - 2023-11-01 09:52 +0100
Re: RCS chats Frank Slootweg <this@ddress.is.invalid> - 2023-11-01 16:27 +0000
Re: RCS chats Arno Welzel <usenet@arnowelzel.de> - 2023-11-01 08:40 +0100
Re: RCS chats Jörg Lorenz <hugybear@gmx.net> - 2023-11-01 09:48 +0100
Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-11-01 14:11 +0100
Re: RCS chats Arno Welzel <usenet@arnowelzel.de> - 2023-11-01 20:46 +0100
Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-11-01 20:53 +0100
Re: RCS chats Jörg Lorenz <hugybear@gmx.net> - 2023-11-02 07:47 +0100
Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-11-02 10:57 +0100
Re: RCS chats Adrian <bulleid@ku.gro.lioff> - 2023-11-02 14:33 +0000
Re: RCS chats Frank Slootweg <this@ddress.is.invalid> - 2023-11-02 16:08 +0000
Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-11-02 18:21 +0100
Re: RCS chats Bob Henson <bob.henson@outlook.com> - 2023-11-02 09:16 +0000
Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-11-02 11:04 +0100
Re: RCS chats Dave Royal<dave@dave123royal.com> - 2023-11-02 10:05 +0000
Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-11-02 11:25 +0100
Re: RCS chats Arno Welzel <usenet@arnowelzel.de> - 2023-11-03 19:18 +0100
Re: RCS chats Arno Welzel <usenet@arnowelzel.de> - 2023-11-02 14:15 +0100
Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-11-02 18:32 +0100
Re: RCS chats Arno Welzel <usenet@arnowelzel.de> - 2023-11-03 19:20 +0100
Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-11-03 22:58 +0100
Re: RCS chats Frank Slootweg <this@ddress.is.invalid> - 2023-11-02 13:21 +0000
Re: RCS chats Arno Welzel <usenet@arnowelzel.de> - 2023-11-02 17:21 +0100
Re: RCS chats Frank Slootweg <this@ddress.is.invalid> - 2023-11-02 16:44 +0000
Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-11-02 18:50 +0100
Re: RCS chats Arno Welzel <usenet@arnowelzel.de> - 2023-11-03 19:21 +0100
Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-11-02 18:45 +0100
Re: RCS chats Frank Slootweg <this@ddress.is.invalid> - 2023-11-02 18:18 +0000
Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-11-02 19:35 +0100
Re: RCS chats Frank Slootweg <this@ddress.is.invalid> - 2023-11-02 20:01 +0000
Re: RCS chats Jörg Lorenz <hugybear@gmx.net> - 2023-10-29 16:13 +0100
Re: RCS chats Jörg Lorenz <hugybear@gmx.net> - 2023-10-29 16:19 +0100
Re: RCS chats Arno Welzel <usenet@arnowelzel.de> - 2023-11-01 08:37 +0100
Re: RCS chats Jörg Lorenz <hugybear@gmx.net> - 2023-11-01 09:50 +0100
Re: RCS chats Arno Welzel <usenet@arnowelzel.de> - 2023-11-01 13:28 +0100
Re: RCS chats Stan Brown <the_stan_brown@fastmail.fm> - 2023-10-29 09:49 -0700
Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-10-29 20:14 +0100
Re: RCS chats Jörg Lorenz <hugybear@gmx.net> - 2023-10-29 21:37 +0100
Re: RCS chats Wally J <walterjones@invalid.nospam> - 2023-10-30 16:49 -0400
Re: RCS chats Stan Brown <the_stan_brown@fastmail.fm> - 2023-10-31 12:12 -0700
Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-10-31 21:44 +0100
Re: RCS chats Stan Brown <the_stan_brown@fastmail.fm> - 2023-11-01 01:22 -0700
Re: RCS chats Andy Burns <usenet@andyburns.uk> - 2023-11-01 08:42 +0000
Re: RCS chats Jörg Lorenz <hugybear@gmx.net> - 2023-11-01 10:01 +0100
Re: RCS chats Jörg Lorenz <hugybear@gmx.net> - 2023-11-01 09:58 +0100
Re: RCS chats Dave Royal<dave@dave123royal.com> - 2023-11-01 09:12 +0000
Re: RCS chats Frank Slootweg <this@ddress.is.invalid> - 2023-11-01 16:54 +0000
Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-11-01 19:11 +0100
Re: RCS chats Arno Welzel <usenet@arnowelzel.de> - 2023-11-01 21:04 +0100
Re: RCS chats Andy Burns <usenet@andyburns.uk> - 2023-11-01 20:30 +0000
Re: RCS chats Dave Royal<dave@dave123royal.com> - 2023-11-01 20:56 +0000
Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-11-01 23:09 +0100
Re: RCS chats Arno Welzel <usenet@arnowelzel.de> - 2023-11-02 17:30 +0100
Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-11-02 18:53 +0100
Re: RCS chats Arno Welzel <usenet@arnowelzel.de> - 2023-11-03 19:24 +0100
Re: RCS chats Andy Burns <usenet@andyburns.uk> - 2023-11-03 18:54 +0000
Re: RCS chats Arno Welzel <usenet@arnowelzel.de> - 2023-11-03 22:59 +0100
Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-11-03 23:01 +0100
Re: RCS chats Arno Welzel <usenet@arnowelzel.de> - 2023-11-05 19:21 +0100
Re: RCS chats Andy Burns <usenet@andyburns.uk> - 2023-11-02 18:14 +0000
Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-11-02 19:24 +0100
Re: RCS chats Arno Welzel <usenet@arnowelzel.de> - 2023-11-03 19:25 +0100
Re: RCS chats Frank Slootweg <this@ddress.is.invalid> - 2023-11-02 13:32 +0000
Re: RCS chats Andy Burns <usenet@andyburns.uk> - 2023-11-02 13:50 +0000
Re: RCS chats Frank Slootweg <this@ddress.is.invalid> - 2023-11-02 14:17 +0000
Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-11-02 18:56 +0100
Re: RCS chats Dave Royal<dave@dave123royal.com> - 2023-11-08 20:13 +0000
Re: RCS chats Andy Burns <usenet@andyburns.uk> - 2023-11-09 09:57 +0000
Re: RCS chats Dave Royal<dave@dave123royal.com> - 2023-11-09 15:48 +0000
Re: RCS chats Andy Burns <usenet@andyburns.uk> - 2023-11-09 16:59 +0000
Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-11-09 20:29 +0100
Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-11-01 14:16 +0100
Re: RCS chats Stan Brown <the_stan_brown@fastmail.fm> - 2023-11-01 10:52 -0700
Re: RCS chats Jörg Lorenz <hugybear@gmx.net> - 2023-11-01 09:54 +0100
Page 5 of 5 — ← Prev page 1 2 3 4 [5]
| From | Andy Burns <usenet@andyburns.uk> |
|---|---|
| Date | 2023-11-02 18:14 +0000 |
| Message-ID | <kqi77eFl7htU2@mid.individual.net> |
| In reply to | #109471 |
Arno Welzel wrote: > if a client does not have RCS it may just not be reachable this > way. At least a RCS server needs to confirm it a message can be > delivered or not. RCS server must have a yes/no lookup by phone number.
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Date | 2023-11-02 19:24 +0100 |
| Message-ID | <kqi7qcFdm1eU3@mid.individual.net> |
| In reply to | #109479 |
On 2023-11-02 19:14, Andy Burns wrote:
> Arno Welzel wrote:
>
>> if a client does not have RCS it may just not be reachable this
>> way. At least a RCS server needs to confirm it a message can be
>> delivered or not.
>
> RCS server must have a yes/no lookup by phone number.
I just disabled RCS on my second phone, then started typing a text to
send to it on my first phone. Instantly it said it was going to use SMS.
Then I activated RCS again. In the first phone, I had to close the
editing an go back to the list of chats, then try to post a new text,
and it then said it was going to use RCS. It took more time to recognize
the change, but not more than 30 seconds.
If it is a database, it is pretty fast.
Both phones are on the same provider (and same WiFi).
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
| From | Arno Welzel <usenet@arnowelzel.de> |
|---|---|
| Date | 2023-11-03 19:25 +0100 |
| Message-ID | <kqks7vF6hhkU5@mid.individual.net> |
| In reply to | #109481 |
Carlos E. R., 2023-11-02 19:24: > On 2023-11-02 19:14, Andy Burns wrote: >> Arno Welzel wrote: >> >>> if a client does not have RCS it may just not be reachable this >>> way. At least a RCS server needs to confirm it a message can be >>> delivered or not. >> >> RCS server must have a yes/no lookup by phone number. > > I just disabled RCS on my second phone, then started typing a text to > send to it on my first phone. Instantly it said it was going to use SMS. > > Then I activated RCS again. In the first phone, I had to close the > editing an go back to the list of chats, then try to post a new text, > and it then said it was going to use RCS. It took more time to recognize > the change, but not more than 30 seconds. > > If it is a database, it is pretty fast. Well - the RCS client has to connect to the server to be able to recieve messages. As soon as the connection is lost, the server of course knows immediately that the client is offline. -- Arno Welzel https://arnowelzel.de
[toc] | [prev] | [next] | [standalone]
| From | Frank Slootweg <this@ddress.is.invalid> |
|---|---|
| Date | 2023-11-02 13:32 +0000 |
| Message-ID | <ui0bu0.604.1@ID-201911.user.individual.net> |
| In reply to | #109445 |
Arno Welzel <usenet@arnowelzel.de> wrote: > Frank Slootweg, 2023-11-01 17:54: > > > Dave Royal <dave@dave123royal.com> wrote: > [...]>> There is also the reasonable goal of replacing the ancient SMS > facility > >> with a more capable and reliable IP-based one. > > > > Exactly! With all its limitations, RCS provides some additional > > functionality compared to the ancient SMS/MMS system, while maintaining > > compatibility with it. That's all. Nothing to get worked up about. > > Is RCS really compatible in the way, the SMS can use the same protocol? > Or is it just the messaging apps which support both SMS as well as RCS? If a messaging app supports RCS, it will use RCS if the other side also supports RCS. If not, it will fallback to SMS/MMS (and can/will give a warning before doing so). > Having a universal standard for end-to-end-encrypted messaging which is > not controlled by a single company and which defines a minimum set of > features like groups or sending text with formatting and attachments > like images, audio and video, would be much more useful. Yes, that would be nice, but is outside the scope of this thread and neither SMS/MMS nor RCS have end-to-end-encryption. Those who need/want end-to-end-encryption have to use some other IM platform, until a standard comes along. I don't know if the upcoming EU legislation for IM interoperation between IM platforms will include end-to-end-encryption as a requirement. [...]
[toc] | [prev] | [next] | [standalone]
| From | Andy Burns <usenet@andyburns.uk> |
|---|---|
| Date | 2023-11-02 13:50 +0000 |
| Message-ID | <kqhnocFfs2gU3@mid.individual.net> |
| In reply to | #109463 |
Frank Slootweg wrote: > neither SMS/MMS nor RCS have end-to-end-encryption. RCS does have E2EE for private chats (I'm not sure about group chats) <http://andyburns.uk/misc/rcs-e2ee.png>
[toc] | [prev] | [next] | [standalone]
| From | Frank Slootweg <this@ddress.is.invalid> |
|---|---|
| Date | 2023-11-02 14:17 +0000 |
| Message-ID | <ui0ehs.16f0.1@ID-201911.user.individual.net> |
| In reply to | #109464 |
Andy Burns <usenet@andyburns.uk> wrote: > Frank Slootweg wrote: > > > neither SMS/MMS nor RCS have end-to-end-encryption. > > RCS does have E2EE for private chats (I'm not sure about group chats) > > <http://andyburns.uk/misc/rcs-e2ee.png> Thanks! I didn't know/realize that. Shows that I/we should pay even less attention to our Swiss 'friend'! :-)
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Date | 2023-11-02 18:56 +0100 |
| Message-ID | <kqi65sFdm1dU9@mid.individual.net> |
| In reply to | #109463 |
On 2023-11-02 14:32, Frank Slootweg wrote:
> Arno Welzel <usenet@arnowelzel.de> wrote:
>> Frank Slootweg, 2023-11-01 17:54:
>>
>>> Dave Royal <dave@dave123royal.com> wrote:
>> [...]>> There is also the reasonable goal of replacing the ancient SMS
>> facility
>>>> with a more capable and reliable IP-based one.
>>>
>>> Exactly! With all its limitations, RCS provides some additional
>>> functionality compared to the ancient SMS/MMS system, while maintaining
>>> compatibility with it. That's all. Nothing to get worked up about.
>>
>> Is RCS really compatible in the way, the SMS can use the same protocol?
>> Or is it just the messaging apps which support both SMS as well as RCS?
>
> If a messaging app supports RCS, it will use RCS if the other side
> also supports RCS. If not, it will fallback to SMS/MMS (and can/will
> give a warning before doing so).
>
>> Having a universal standard for end-to-end-encrypted messaging which is
>> not controlled by a single company and which defines a minimum set of
>> features like groups or sending text with formatting and attachments
>> like images, audio and video, would be much more useful.
>
> Yes, that would be nice, but is outside the scope of this thread and
> neither SMS/MMS nor RCS have end-to-end-encryption.
RCS has end to end encryption.
<https://support.google.com/messages/thread/229405182/your-rcs-conversations-are-now-fully-end-to-end-encrypted?hl=en>
RCS is the modern industry standard for dynamic and secure messaging.
And now, all of your RCS conversations in Messages by Google are
end-to-end encrypted, including group chats, which keeps them private
between you and the people you're messaging.Aug 8, 2023
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
| From | Dave Royal<dave@dave123royal.com> |
|---|---|
| Date | 2023-11-08 20:13 +0000 |
| Message-ID | <uigq4v$1p145$1@dont-email.me> |
| In reply to | #109432 |
On 1 Nov 2023 09:12:02 -0000 (UTC) Dave Royal wrote: > >The unavailability of iMessages on Android prevents iOS users switching to >Android devices. Peer pressure among children makes Android phones less >attractive - search for 'iphone blue bubbles' if you don't know about >that. > >Google want to persuade, if posible, or force - using anti-monolopy >legislation - Apple to allow iMessage to interwork with Android devices. >They therefore need to establish a similar messaging facility among >Android users so that Apple's refusal to cooperate is seen as >anti-competitive. > Google Turns To Regulators To Make Apple Open Up iMessage: <https://m.slashdot.org/story/421201> Among the usual ill-informed and US-centric comments under that /. piece are some interesting ones about (a) e2ee (b) the difference between RCS as standardised by GSMA and RCS as promoted by Google. -- (Remove numerics from email address)
[toc] | [prev] | [next] | [standalone]
| From | Andy Burns <usenet@andyburns.uk> |
|---|---|
| Date | 2023-11-09 09:57 +0000 |
| Message-ID | <kr3op4Fr94bU2@mid.individual.net> |
| In reply to | #109824 |
Dave Royal wrote: > Google Turns To Regulators To Make Apple Open Up iMessage: The EU has already decided that WhatsApp and Messenger will have to play ball ...
[toc] | [prev] | [next] | [standalone]
| From | Dave Royal<dave@dave123royal.com> |
|---|---|
| Date | 2023-11-09 15:48 +0000 |
| Message-ID | <uiiv0d$28u2o$1@dont-email.me> |
| In reply to | #109832 |
On 9 Nov 2023 09:57:56 +0000 Andy Burns wrote: >Dave Royal wrote: > >> Google Turns To Regulators To Make Apple Open Up iMessage: > >The EU has already decided that WhatsApp and Messenger will have to play >ball ... The DMA - Digital Markets Act - is in force, yes, but the details are yet to be agreed. Hence Google's latest initiative to get Europarl to interpret it the way Google want. There isn't an agreed message protocol yet, or even agreement of what features will be 'core': presence/status? encryption (& backdoors)? colour of message bubbles? ... See "What changes will it make for interoperability of messenger services?" in the link. <https://ec.europa.eu/commission/presscorner/detail/en/QANDA_20_2349> -- (Remove numerics from email address)
[toc] | [prev] | [next] | [standalone]
| From | Andy Burns <usenet@andyburns.uk> |
|---|---|
| Date | 2023-11-09 16:59 +0000 |
| Message-ID | <kr4hg9F32ioU1@mid.individual.net> |
| In reply to | #109854 |
Dave Royal wrote: > On 9 Nov 2023 09:57:56 +0000 Andy Burns wrote: >> Dave Royal wrote: >> >>> Google Turns To Regulators To Make Apple Open Up iMessage: >> >> The EU has already decided that WhatsApp and Messenger will have to play >> ball ... > > The DMA - Digital Markets Act - is in force, yes, but the details are yet > to be agreed. Hence Google's latest initiative to get Europarl to > interpret it the way Google want. The way I read it, Meta has already been determined to be a "gatekeeper" regarding instant messaging, apple are claiming they shouldn't be? But that's only from a quick read of this ... <https://ec.europa.eu/commission/presscorner/detail/en/ip_23_4328> > There isn't an agreed message protocol > yet There's a proposal that seems feasible and has all sorts of "relevant" names attached <https://datatracker.ietf.org/doc/rfc9420/> > or even agreement of what features will be 'core': presence/status? > encryption (& backdoors)? colour of message bubbles? ... > > See "What changes will it make for interoperability of messenger > services?" in the link. > <https://ec.europa.eu/commission/presscorner/detail/en/QANDA_20_2349> I'll have a read, I though there were some defined features (cross-platform text within 6 months, group chats within 2 years, 4 years for voice/video calling)
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Date | 2023-11-09 20:29 +0100 |
| Message-ID | <kr4q9mFsdr5U9@mid.individual.net> |
| In reply to | #109854 |
On 2023-11-09 16:48, Dave Royal wrote:
> On 9 Nov 2023 09:57:56 +0000 Andy Burns wrote:
>> Dave Royal wrote:
>>
>>> Google Turns To Regulators To Make Apple Open Up iMessage:
>>
>> The EU has already decided that WhatsApp and Messenger will have to play
>> ball ...
>
> The DMA - Digital Markets Act - is in force, yes, but the details are yet
> to be agreed. Hence Google's latest initiative to get Europarl to
> interpret it the way Google want. There isn't an agreed message protocol
> yet, or even agreement of what features will be 'core': presence/status?
> encryption (& backdoors)? colour of message bubbles? ...
>
> See "What changes will it make for interoperability of messenger
> services?" in the link.
> <https://ec.europa.eu/commission/presscorner/detail/en/QANDA_20_2349>
<https://www.xataka.com/aplicaciones/google-lleva-anos-esperando-a-que-imessage-llegue-a-android-apple-no-quiere-solucion-tiene-europa>
Automated translation by DeepL.
Google tired of waiting for Apple: asks Europe to force iMessage to come
to Android
* Google and major European operators send letter to the European
Commission to designate iMessage as a "core" service.
* This would force Apple to extend the interoperability of its
messaging service.
Enrique Perez
8 November 2023Updated 8 November 2023, 15:46
Apple even considered having iMessage on Android a decade ago, but
decided to keep it exclusive to the iPhone in order to retain users.
It's not a technical problem, as iMessage could work on Google's
operating system and all other manufacturers without any problems. It is
simply another strategy in the long-running battle between the big tech
companies.
Google asks Europe for help. Tired of waiting for Apple to take the
plunge, Google has asked Brussels to help it act. A letter to which the
Financial Times has had access states that Google has asked the European
Commission to designate iMessage as a "core" service under the Digital
Markets Act (DMA).
It is not alone in this request, as representatives from Vodafone,
Deutsche Telekom, Telefónica and Orange have also signed the petition.
The major European operators also believe that the expansion of Apple's
messaging service would be beneficial.
The inclusion of iMessage is up in the air. Last September the
Commission designated the 22 services that were covered by the DMA. In
total six "gatekeepers" and their respective systems. Apple is one of
them, but the chosen services include the App Store, Safari and iOS. But
iMessage was not included in principle.
But the door was left open. The Commission gave itself five months to
decide on iMessage.
The argument is that almost nobody uses iMessage here. Apple's
justification is that the use of iMessage in Europe is residual, unlike
in the United States. Because of these low numbers, they justify not
including it as a "core" service and therefore avoid the obligation to
open up their ecosystem.
Another argument put forward by Apple is that of privacy and security,
which would supposedly be affected if it were forced to make iMessage
compatible with Android phones.
Tightening the rope for Europe to be more forceful. The letter sent by
Google and the operators is a move to pressure the European Commission
to act more forcefully.
"Consumers using an Apple iPhone should be able to benefit from
competitive services from a variety of providers," explained Thierry
Breton, the European Internal Market Commissioner. A declaration of
intent that remains to be seen to what extent it materialises into
obligations.
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Date | 2023-11-01 14:16 +0100 |
| Message-ID | <kqf1dbFqf11U3@mid.individual.net> |
| In reply to | #109422 |
On 2023-11-01 09:22, Stan Brown wrote:
> On Tue, 31 Oct 2023 21:44:47 +0100, Carlos E. R. wrote:
>>
>> On 2023-10-31 20:12, Stan Brown wrote:
>>> On Mon, 30 Oct 2023 16:49:33 -0400, Wally J wrote:
>>>> Stan Brown <the_stan_brown@fastmail.fm> wrote
>>>>
>>>>> Thanks to all who responded. It sounds like RCS Chats has advantages
>>>>> for some people, but those don't apply to how I use messaging. I'm in
>>>>> the US and only message people in the US, and both data and messaging
>>>>> are free and unlimited with my plan.
>>>>
>>>> Hi Stan,
>>>>
>>>> This is an FYI to let you know of another possible similar solution...
>>>> <https://home.pulsesms.app/overview/>
>>>>
>>>
>>> Thank you for the information. But since nobody has mentioned any
>>> feature of RCS Chats that I would actually use, I don't think I need
>>> to try out alternative ways of getting similar functionality. :-)
>>
>> I understand that new Android phones ship with RCS activated by default.
>
> Not just new phones. After I dismissed Google's nag to
> enable RCS chats, I got a notification that RCS Chats
> enabled is now the default. Fortunately the
> notification linked to the appropriate setting, so I
> was able to turn it off.
Why? It will not hurt leaving it on.
> Out of curiosity, does anyone know why Google is being
> so aggressive about promoting RCS Chats? How will they
> make money off of it?
Because it improves "the android experience".
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
| From | Stan Brown <the_stan_brown@fastmail.fm> |
|---|---|
| Date | 2023-11-01 10:52 -0700 |
| Message-ID | <MPG.3fac3054170155aa99020e@news.individual.net> |
| In reply to | #109422 |
On Wed, 1 Nov 2023 01:22:18 -0700, Stan Brown wrote: > Out of curiosity, does anyone know why Google is being > so aggressive about promoting RCS Chats? How will they > make money off of it? Thanks to those who gave various reasons or possible reasons, and satisfied my curiosity! -- Stan Brown, Tehachapi, California, USA https://BrownMath.com/ Shikata ga nai...
[toc] | [prev] | [next] | [standalone]
| From | Jörg Lorenz <hugybear@gmx.net> |
|---|---|
| Date | 2023-11-01 09:54 +0100 |
| Message-ID | <uht3ns$v9f1$2@solani.org> |
| In reply to | #109412 |
Am 31.10.23 um 21:44 schrieb Carlos E. R.: > On 2023-10-31 20:12, Stan Brown wrote: >> On Mon, 30 Oct 2023 16:49:33 -0400, Wally J wrote: >>> Stan Brown <the_stan_brown@fastmail.fm> wrote >>> >>>> Thanks to all who responded. It sounds like RCS Chats has advantages >>>> for some people, but those don't apply to how I use messaging. I'm in >>>> the US and only message people in the US, and both data and messaging >>>> are free and unlimited with my plan. >>> >>> Hi Stan, >>> >>> This is an FYI to let you know of another possible similar solution... >>> <https://home.pulsesms.app/overview/> >>> >> >> Thank you for the information. But since nobody has mentioned any >> feature of RCS Chats that I would actually use, I don't think I need >> to try out alternative ways of getting similar functionality. :-) > > I understand that new Android phones ship with RCS activated by default. So what! That does not change anything. -- Alea icacta est
[toc] | [prev] | [standalone]
Page 5 of 5 — ← Prev page 1 2 3 4 [5]
Back to top | Article view | comp.mobile.android
csiph-web