Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.mobile.android > #109870
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Newsgroups | comp.mobile.android |
| Subject | Re: RCS chats |
| Date | 2023-11-09 20:29 +0100 |
| Message-ID | <kr4q9mFsdr5U9@mid.individual.net> (permalink) |
| References | (5 earlier) <MPG.3fabaa943b8a760b99020c@news.individual.net> <uht4p2$1hppg$1@dont-email.me> <uigq4v$1p145$1@dont-email.me> <kr3op4Fr94bU2@mid.individual.net> <uiiv0d$28u2o$1@dont-email.me> |
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.
Back to comp.mobile.android | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
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
csiph-web