Rocksolid Light

News from da outaworlds

mail  files  register  groups  login

Message-ID:  

You shall be rewarded for a dastardly deed.


comp / comp.mobile.android / Re: Google is preparing to replace RCS with MLS

SubjectAuthor
* Google is preparing to replace RCS with MLSCarlos E. R.
+* Re: Google is preparing to replace RCS with MLSAndrew
|`* Re: Google is preparing to replace RCS with MLSAndy Burns
| `* Re: Google is preparing to replace RCS with MLSAndrew
|  `* Re: Google is preparing to replace RCS with MLSCarlos E. R.
|   `* Re: Google is preparing to replace RCS with MLSAndrew
|    +* Re: Google is preparing to replace RCS with MLSAlan
|    |`* Re: Google is preparing to replace RCS with MLSs|b
|    | +- Re: Google is preparing to replace RCS with MLSAlan
|    | +* Re: Google is preparing to replace RCS with MLSAndrew
|    | |`- Re: Google is preparing to replace RCS with MLSAlan
|    | `* Re: Google is preparing to replace RCS with MLSCarlos E. R.
|    |  +- Re: Google is preparing to replace RCS with MLSAlan
|    |  `* Re: Google is preparing to replace RCS with MLSAndrew
|    |   +* Re: Google is preparing to replace RCS with MLSCarlos E. R.
|    |   |+- Re: Google is preparing to replace RCS with MLSAlan
|    |   |`* Re: Google is preparing to replace RCS with MLSAndrew
|    |   | +* Re: Google is preparing to replace RCS with MLSCarlos E. R.
|    |   | |`* Re: Google is preparing to replace RCS with MLSAndrew
|    |   | | `* Re: Google is preparing to replace RCS with MLSCarlos E.R.
|    |   | |  `* Re: Google is preparing to replace RCS with MLSAndrew
|    |   | |   +- Re: Google is preparing to replace RCS with MLSAlan
|    |   | |   `* Re: Google is preparing to replace RCS with MLSArno Welzel
|    |   | |    `* Re: Google is preparing to replace RCS with MLSAndrew
|    |   | |     +- Re: Google is preparing to replace RCS with MLSAlan
|    |   | |     `* Re: Google is preparing to replace RCS with MLSArno Welzel
|    |   | |      +* Re: Google is preparing to replace RCS with MLSAndrew
|    |   | |      |+- Re: Google is preparing to replace RCS with MLSAlan
|    |   | |      |`* Re: Google is preparing to replace RCS with MLSArno Welzel
|    |   | |      | `* Re: Google is preparing to replace RCS with MLSAndrew
|    |   | |      |  `* Re: Google is preparing to replace RCS with MLSArno Welzel
|    |   | |      |   `* Re: Google is preparing to replace RCS with MLSAndrew
|    |   | |      |    `* Re: Google is preparing to replace RCS with MLSArno Welzel
|    |   | |      |     `* Re: Google is preparing to replace RCS with MLSAlan
|    |   | |      |      `* Re: Google is preparing to replace RCS with MLSArno Welzel
|    |   | |      |       `* Re: Google is preparing to replace RCS with MLSAndrew
|    |   | |      |        +* Re: Google is preparing to replace RCS with MLSArno Welzel
|    |   | |      |        |+- Re: Google is preparing to replace RCS with MLSAlan
|    |   | |      |        |`* Re: Google is preparing to replace RCS with MLSAndrew
|    |   | |      |        | +* Re: Google is preparing to replace RCS with MLSAlan
|    |   | |      |        | |`* Re: Google is preparing to replace RCS with MLSThe Real Bev
|    |   | |      |        | | +* Re: Google is preparing to replace RCS with MLSAlan
|    |   | |      |        | | |`* Re: Google is preparing to replace RCS with MLSThe Real Bev
|    |   | |      |        | | | +* Re: Google is preparing to replace RCS with MLSAlan
|    |   | |      |        | | | |`* Re: Google is preparing to replace RCS with MLSThe Real Bev
|    |   | |      |        | | | | +* Re: Google is preparing to replace RCS with MLSAJL
|    |   | |      |        | | | | |`* Re: Google is preparing to replace RCS with MLSThe Real Bev
|    |   | |      |        | | | | | `* Re: Google is preparing to replace RCS with MLSAJL
|    |   | |      |        | | | | |  `- Re: Google is preparing to replace RCS with MLSThe Real Bev
|    |   | |      |        | | | | `* Re: Google is preparing to replace RCS with MLSAlan
|    |   | |      |        | | | |  `* Re: Google is preparing to replace RCS with MLSThe Real Bev
|    |   | |      |        | | | |   `* Re: Google is preparing to replace RCS with MLSAlan
|    |   | |      |        | | | |    `* Re: Google is preparing to replace RCS with MLSThe Real Bev
|    |   | |      |        | | | |     `- Re: Google is preparing to replace RCS with MLSAlan
|    |   | |      |        | | | `* Re: Google is preparing to replace RCS with MLSArno Welzel
|    |   | |      |        | | |  `* Re: Google is preparing to replace RCS with MLSAlan
|    |   | |      |        | | |   +* Re: Google is preparing to replace RCS with MLSArno Welzel
|    |   | |      |        | | |   |+* Re: Google is preparing to replace RCS with MLSAndy Burns
|    |   | |      |        | | |   ||+- Re: Google is preparing to replace RCS with MLSAlan
|    |   | |      |        | | |   ||`* Re: Google is preparing to replace RCS with MLSAndrew
|    |   | |      |        | | |   || +* Re: Google is preparing to replace RCS with MLSAndy Burns
|    |   | |      |        | | |   || |+* Re: Google is preparing to replace RCS with MLSAndrew
|    |   | |      |        | | |   || ||+- Re: Google is preparing to replace RCS with MLSAndy Burns
|    |   | |      |        | | |   || ||`- Re: Google is preparing to replace RCS with MLSAndy Burns
|    |   | |      |        | | |   || |`* Re: Google is preparing to replace RCS with MLSArno Welzel
|    |   | |      |        | | |   || | `* Re: Google is preparing to replace RCS with MLSAndy Burns
|    |   | |      |        | | |   || |  `* Re: Google is preparing to replace RCS with MLSArno Welzel
|    |   | |      |        | | |   || |   `* Re: Google is preparing to replace RCS with MLSAndrew
|    |   | |      |        | | |   || |    `* Re: Google is preparing to replace RCS with MLSArno Welzel
|    |   | |      |        | | |   || |     `* Re: Google is preparing to replace RCS with MLSAndrew
|    |   | |      |        | | |   || |      `* Re: Google is preparing to replace RCS with MLSArno Welzel
|    |   | |      |        | | |   || |       `* Re: Google is preparing to replace RCS with MLSAndrew
|    |   | |      |        | | |   || |        `- Re: Google is preparing to replace RCS with MLSArno Welzel
|    |   | |      |        | | |   || `- Re: Google is preparing to replace RCS with MLSArno Welzel
|    |   | |      |        | | |   |`- Re: Google is preparing to replace RCS with MLSAlan
|    |   | |      |        | | |   `* Re: Google is preparing to replace RCS with MLSCarlos E.R.
|    |   | |      |        | | |    `- Re: Google is preparing to replace RCS with MLSAndrew
|    |   | |      |        | | +* Re: Google is preparing to replace RCS with MLSAndy Burns
|    |   | |      |        | | |`* Re: Google is preparing to replace RCS with MLSAndrew
|    |   | |      |        | | | `- Re: Google is preparing to replace RCS with MLSAndy Burns
|    |   | |      |        | | `- Re: Google is preparing to replace RCS with MLSArno Welzel
|    |   | |      |        | `* Re: Google is preparing to replace RCS with MLSArno Welzel
|    |   | |      |        |  `- Re: Google is preparing to replace RCS with MLSCarlos E.R.
|    |   | |      |        `- Re: Google is preparing to replace RCS with MLSAlan
|    |   | |      `* Re: Google is preparing to replace RCS with MLSs|b
|    |   | |       +* Re: Google is preparing to replace RCS with MLSAndrew
|    |   | |       |+- Re: Google is preparing to replace RCS with MLSAlan
|    |   | |       |`- Re: Google is preparing to replace RCS with MLSArno Welzel
|    |   | |       `- Re: Google is preparing to replace RCS with MLSArno Welzel
|    |   | `- Re: Google is preparing to replace RCS with MLSAlan
|    |   `* Re: Google is preparing to replace RCS with MLSAlan
|    |    `* Re: Google is preparing to replace RCS with MLSCarlos E. R.
|    |     +- Re: Google is preparing to replace RCS with MLSAlan
|    |     `* Re: Google is preparing to replace RCS with MLSAndrew
|    |      +- Re: Google is preparing to replace RCS with MLSAlan
|    |      `* Re: Google is preparing to replace RCS with MLSCarlos E. R.
|    |       `* Re: Google is preparing to replace RCS with MLSAndrew
|    |        +* Re: Google is preparing to replace RCS with MLSAlan
|    |        |`* Re: Google is preparing to replace RCS with MLSBill Powell
|    |        | +* Re: Google is preparing to replace RCS with MLSAndy Burns
|    |        | |`* Re: Google is preparing to replace RCS with MLSBill Powell
|    |        | `* Re: Google is preparing to replace RCS with MLSAlan
|    |        `* Re: Google is preparing to replace RCS with MLSCarlos E. R.
|    `* Re: Google is preparing to replace RCS with MLSCarlos E. R.
`* Re: Google is preparing to replace RCS with MLSs|b

Pages:123456
Subject: Google is preparing to replace RCS with MLS
From: Carlos E. R.
Newsgroups: comp.mobile.android
Date: Sat, 6 Jul 2024 20:35 UTC
Path: eternal-september.org!news.eternal-september.org!feeder3.eternal-september.org!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: robin_listas@es.invalid (Carlos E. R.)
Newsgroups: comp.mobile.android
Subject: Google is preparing to replace RCS with MLS
Date: Sat, 6 Jul 2024 22:35:26 +0200
Lines: 51
Message-ID: <leto4eFasrbU6@mid.individual.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: individual.net rfGxGv2PmcS6p4MdRDuMGAAsK4Z70rN1ORgTnWGwbVjNnf2gFg
Cancel-Lock: sha1:1qODTcJrBDkA+zJm6YtIj1sSzBw= sha256:4XekWYgLt0N6aucpkbc+UW8G+92lfhsWQtLhxvjgps8=
User-Agent: Mozilla Thunderbird
Content-Language: en-CA, es-ANY
View all headers

The information I have is from a Spanish paper, which you can read with
google translate, or find an English language source.

<https://www.elespanol.com/elandroidelibre/noticias-y-novedades/20240705/google-messages-cambia-siempre-nuevo-protocolo-mensajeria-proteger-mensajes/868163289_0.html>

Google and the RCS protocol have been part of the discourse with which
they have been attacking Apple on numerous occasions , and now the
technology giant intends to replace it with a more advanced one with
some important functions. SMS, although they are not used as much in
Spain as in the United States, will now be much more secure with the new
protocol .

The RCS protocol became essential for the Android text messaging
platform in 2019, and Apple recently added support for it with the
update to iOS 18 . The only drawback it has is that it requires both
mobiles or devices to have the same platform to ensure end-to-end
encryption of messages; an essential measure for privacy.

To cover this gap, Google announced last year support for the MLS
(Messaging Layer Security) protocol that brings end-to-end encryption to
Android devices. MLS is an enhanced protocol developed by the Internet
Engineering Task Force (IETF). Its objective is to ensure communication
between apps and platforms always with the maxim that individual and
group chats are effectively encrypted.

.... continues at the link.

Further info:

<https://www.androidpolice.com/google-messages-messaging-layer-security/>

Google Messages is preparing to implement its new messaging protocol

Summary

* Evidence suggests Google Messages will soon add Messaging Layer
Security (MLS) support for end-to-end encryption.
* After Google pledged support for the standard last year, MLS is
set to become the default security layer for encryption once fully
implemented in Messages.
* Adoption outside of Google Messages remains to be seen, but MLS
looks to unify encrypted messaging across platforms and services by
implementing an encryption standard that all messaging apps can share.

--
Cheers,
Carlos E.R.

Subject: Re: Google is preparing to replace RCS with MLS
From: Andrew
Newsgroups: comp.mobile.android
Organization: BWH Usenet Archive (https://usenet.blueworldhosting.com)
Date: Sat, 6 Jul 2024 21:40 UTC
References: 1
Path: eternal-september.org!news.eternal-september.org!feeder3.eternal-september.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!nnrp.usenet.blueworldhosting.com!.POSTED!not-for-mail
From: andrew@spam.net (Andrew)
Newsgroups: comp.mobile.android
Subject: Re: Google is preparing to replace RCS with MLS
Date: Sat, 6 Jul 2024 21:40:16 -0000 (UTC)
Organization: BWH Usenet Archive (https://usenet.blueworldhosting.com)
Message-ID: <v6cdk0$qnp$1@nnrp.usenet.blueworldhosting.com>
References: <leto4eFasrbU6@mid.individual.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Sat, 6 Jul 2024 21:40:16 -0000 (UTC)
Injection-Info: nnrp.usenet.blueworldhosting.com;
logging-data="27385"; mail-complaints-to="usenet@blueworldhosting.com"
User-Agent: NewsTap/5.5 (iPad)
Cancel-Lock: sha1:zrZS2EjumYCWvX4GMzMf/TtldC8= sha256:ngejSCZYAPt68MXyIOIkEwuPu45XkJRghKWmxw1NKgQ=
sha1:kIyaU3SoIRHa69vCkFTsHrz0rdg= sha256:pE+6twcCTIQpe/cz+/ggfmA+G06xNOzYNl7aBK4KPmM=
X-Face: VQ}*Ueh[4uTOa]Md([|$jb%rw~ksq}bzqA;z-.*8JM`4+zL[`N\ORHCI80}]}$]$e5]/i#v qdYsE`yh@ZL3L{H:So{yN)b=AZJtpaP98ch_4W}
View all headers

Carlos E. R. wrote on Sat, 6 Jul 2024 22:35:26 +0200 :

> To cover this gap, Google announced last year support for the MLS
> (Messaging Layer Security) protocol that brings end-to-end encryption to
> Android devices.

Thanks Carlos for that timely information as Lord knows, the last thing
Apple wants is to play nicely with Android messaging (which isn't even a
guess on my part because I read the internal emails published during the
Epic court case deposition where that's essentially what Apple execs said).

Looking up MLS:
<https://messaginglayersecurity.rocks/>
"Messaging Layer Security (MLS) is an IETF working group building
a modern, efficient, secure group messaging protocol."

Q: Should I use this right now?
A: Yes! The protocol has been approved by the IESG and has been
published as RFC9420. There are several implementations,
of which some are open source.
<https://github.com/mlswg/mls-implementations>

I looked for an Android messaging app which supports MLS but it might take
a while as the Skyica App Finder isn't working lately for some reason.

Subject: Re: Google is preparing to replace RCS with MLS
From: Andy Burns
Newsgroups: comp.mobile.android
Date: Sat, 6 Jul 2024 22:47 UTC
References: 1 2
Path: eternal-september.org!news.eternal-september.org!feeder3.eternal-september.org!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: usenet@andyburns.uk (Andy Burns)
Newsgroups: comp.mobile.android
Subject: Re: Google is preparing to replace RCS with MLS
Date: Sat, 6 Jul 2024 23:47:37 +0100
Lines: 10
Message-ID: <letvsdFh2f2U1@mid.individual.net>
References: <leto4eFasrbU6@mid.individual.net>
<v6cdk0$qnp$1@nnrp.usenet.blueworldhosting.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: individual.net A+1HI9UUCrIvr/0KhvYxrAuYM22ymCZJLgYHv358QJRArvpCNU
Cancel-Lock: sha1:Z0rQBBFfKs6tO9qBB+TDAuGfhvY= sha256:CluQVqSawYT07aAU72Z+5LmnKw5jcfGPd+m6KlVhH/s=
User-Agent: Mozilla Thunderbird
Content-Language: en-GB
In-Reply-To: <v6cdk0$qnp$1@nnrp.usenet.blueworldhosting.com>
View all headers

Andrew wrote:

> Looking up MLS:
> <https://messaginglayersecurity.rocks/>
> "Messaging Layer Security (MLS) is an IETF working group building
> a modern, efficient, secure group messaging protocol."

We discussed MLS nearly a year ago

<https://groups.google.com/g/comp.mobile.android/c/6iWXKyYJ-UY/m/4cd8hNuIAQAJ>

Subject: Re: Google is preparing to replace RCS with MLS
From: Andrew
Newsgroups: comp.mobile.android
Organization: BWH Usenet Archive (https://usenet.blueworldhosting.com)
Date: Sat, 6 Jul 2024 23:34 UTC
References: 1 2 3
Path: eternal-september.org!news.eternal-september.org!feeder3.eternal-september.org!tncsrv06.tnetconsulting.net!newsfeed.endofthelinebbs.com!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!nnrp.usenet.blueworldhosting.com!.POSTED!not-for-mail
From: andrew@spam.net (Andrew)
Newsgroups: comp.mobile.android
Subject: Re: Google is preparing to replace RCS with MLS
Date: Sat, 6 Jul 2024 23:34:17 -0000 (UTC)
Organization: BWH Usenet Archive (https://usenet.blueworldhosting.com)
Message-ID: <v6ck9o$2o45$1@nnrp.usenet.blueworldhosting.com>
References: <leto4eFasrbU6@mid.individual.net> <v6cdk0$qnp$1@nnrp.usenet.blueworldhosting.com> <letvsdFh2f2U1@mid.individual.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Sat, 6 Jul 2024 23:34:17 -0000 (UTC)
Injection-Info: nnrp.usenet.blueworldhosting.com;
logging-data="90245"; mail-complaints-to="usenet@blueworldhosting.com"
User-Agent: NewsTap/5.5 (iPad)
Cancel-Lock: sha1:bBJjFf6kBZylPuSCuChHYJc1QJg= sha256:fsdMEPgUgzDRmZiXbgNrl0CXE4z3/b1/1ZRwnIwRupQ=
sha1:L8sJRY4Qvq053kcUOekqGkpFdRY= sha256:2robAZtSUEmZrA4CWscoSyVqbOsRrOFYULZJphg6FTI=
X-Face: VQ}*Ueh[4uTOa]Md([|$jb%rw~ksq}bzqA;z-.*8JM`4+zL[`N\ORHCI80}]}$]$e5]/i#v qdYsE`yh@ZL3L{H:So{yN)b=AZJtpaP98ch_4W}
View all headers

Andy Burns wrote on Sat, 6 Jul 2024 23:47:37 +0100 :

> We discussed MLS nearly a year ago
>
> <https://groups.google.com/g/comp.mobile.android/c/6iWXKyYJ-UY/m/4cd8hNuIAQAJ>

Thank God for people who use search engines. Thanks. Much appreciated.

Whew! That's a long thread. I am not on it. I don't remember reading it.

Generally my memory is excellent, so I probably didn't even read it as I
never cared for end-to-end encryption because it inherently has always
required both people using the exact same server and both people having
login accounts on that server (where I don't need to say more why that's
anathema for privacy).

Does this "new" MLS stuff require both those privacy-destroying things?

BTW, a new easy-to-remember Usenet search URI is this (which I made today).
https://tinyurl.com/nova-comp-mobile-android

Which complements the old easy-to-remember search URI I made long ago:
https://tinyurl.com/comp-mobile-android

Subject: Re: Google is preparing to replace RCS with MLS
From: Carlos E. R.
Newsgroups: comp.mobile.android
Date: Sun, 7 Jul 2024 11:02 UTC
References: 1 2 3 4
Path: eternal-september.org!news.eternal-september.org!feeder3.eternal-september.org!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: robin_listas@es.invalid (Carlos E. R.)
Newsgroups: comp.mobile.android
Subject: Re: Google is preparing to replace RCS with MLS
Date: Sun, 7 Jul 2024 13:02:50 +0200
Lines: 35
Message-ID: <levauqFmm0pU1@mid.individual.net>
References: <leto4eFasrbU6@mid.individual.net>
<v6cdk0$qnp$1@nnrp.usenet.blueworldhosting.com>
<letvsdFh2f2U1@mid.individual.net>
<v6ck9o$2o45$1@nnrp.usenet.blueworldhosting.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: individual.net uxfMOFgFCGHOq5o17M8F0AONBGFtKQp9oS+LVUeJ1pZNiVUvY7
Cancel-Lock: sha1:w4SpZg2MPjsrkyvzC8f8gM6RdIQ= sha256:tDu/Gpb+/K2Zc9xPwQvKk0XqeDn1wgJ/BmeLXgMOgoM=
User-Agent: Mozilla Thunderbird
Content-Language: en-CA, es-ANY
In-Reply-To: <v6ck9o$2o45$1@nnrp.usenet.blueworldhosting.com>
View all headers

On 2024-07-07 01:34, Andrew wrote:
> Andy Burns wrote on Sat, 6 Jul 2024 23:47:37 +0100 :
>
>> We discussed MLS nearly a year ago
>>
>> <https://groups.google.com/g/comp.mobile.android/c/6iWXKyYJ-UY/m/4cd8hNuIAQAJ>
>
> Thank God for people who use search engines. Thanks. Much appreciated.
>
> Whew! That's a long thread. I am not on it. I don't remember reading it.
>
> Generally my memory is excellent, so I probably didn't even read it as I
> never cared for end-to-end encryption because it inherently has always
> required both people using the exact same server and both people having
> login accounts on that server (where I don't need to say more why that's
> anathema for privacy).
>
> Does this "new" MLS stuff require both those privacy-destroying things?

In the google implementation, it will require the same as the current
Google Messages app requires. This is just an (educated) guess.

> BTW, a new easy-to-remember Usenet search URI is this (which I made today).
> https://tinyurl.com/nova-comp-mobile-android
>
> Which complements the old easy-to-remember search URI I made long ago:
> https://tinyurl.com/comp-mobile-android

I never use shorted links.

--
Cheers,
Carlos E.R.

Subject: Re: Google is preparing to replace RCS with MLS
From: Andrew
Newsgroups: comp.mobile.android
Organization: BWH Usenet Archive (https://usenet.blueworldhosting.com)
Date: Sun, 7 Jul 2024 13:43 UTC
References: 1 2 3 4 5
Path: eternal-september.org!news.eternal-september.org!feeder3.eternal-september.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!nnrp.usenet.blueworldhosting.com!.POSTED!not-for-mail
From: andrew@spam.net (Andrew)
Newsgroups: comp.mobile.android
Subject: Re: Google is preparing to replace RCS with MLS
Date: Sun, 7 Jul 2024 13:43:35 -0000 (UTC)
Organization: BWH Usenet Archive (https://usenet.blueworldhosting.com)
Message-ID: <v6e626$15id$1@nnrp.usenet.blueworldhosting.com>
References: <leto4eFasrbU6@mid.individual.net> <v6cdk0$qnp$1@nnrp.usenet.blueworldhosting.com> <letvsdFh2f2U1@mid.individual.net> <v6ck9o$2o45$1@nnrp.usenet.blueworldhosting.com> <levauqFmm0pU1@mid.individual.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Sun, 7 Jul 2024 13:43:35 -0000 (UTC)
Injection-Info: nnrp.usenet.blueworldhosting.com;
logging-data="38477"; mail-complaints-to="usenet@blueworldhosting.com"
User-Agent: NewsTap/5.5 (iPad)
Cancel-Lock: sha1:Q1ZhL8/vCNwHWxxyoflhvzwtPVU= sha256:JlJMtmgxW3dJj49Vi2P7Xkw3z1R0mXl4tgAz5nHGAdE=
sha1:tT5vRy27ZdkNlGlXvnEC9ofm5ks= sha256:LbHhfVitBZbnxneLLDIBuZcby0dbpirBuYqNhAXp22k=
X-Face: VQ}*Ueh[4uTOa]Md([|$jb%rw~ksq}bzqA;z-.*8JM`4+zL[`N\ORHCI80}]}$]$e5]/i#v qdYsE`yh@ZL3L{H:So{yN)b=AZJtpaP98ch_4W}
View all headers

Carlos E. R. wrote on Sun, 7 Jul 2024 13:02:50 +0200 :

>> Does this "new" MLS stuff require both those privacy-destroying things?
>
> In the google implementation, it will require the same as the current
> Google Messages app requires. This is just an (educated) guess.

Hi Carlos,
Well then, since I don't use Google apps, may I ask the team if the Google
Messages app with RCS also requires those two privacy destroying things?

Q: Does Google Messages with RCS require a login account for both users
who wish to communicate on an end-to-end encrypted chat?
A: Yes or no.

If so, there's a privacy issue there...

>> BTW, a new easy-to-remember Usenet search URI is this (which I made today).
>> https://tinyurl.com/nova-comp-mobile-android
>>
>> Which complements the old easy-to-remember search URI I made long ago:
>> https://tinyurl.com/comp-mobile-android
>
> I never use shorted links.

The long link is hard to remember:
This short url https://tinyurl.com/nova-comp-mobile-android expands to
https://www.novabbs.com/computers/search.php?group=comp.mobile.android

This short url https://tinyurl.com/comp-mobile-android expands to
https://groups.google.com/forum/#!forum/comp.mobile.android which is
https://groups.google.com/g/comp.mobile.android

Subject: Re: Google is preparing to replace RCS with MLS
From: Alan
Newsgroups: comp.mobile.android
Organization: A noiseless patient Spider
Date: Sun, 7 Jul 2024 16:23 UTC
References: 1 2 3 4 5 6
Path: eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: nuh-uh@nope.com (Alan)
Newsgroups: comp.mobile.android
Subject: Re: Google is preparing to replace RCS with MLS
Date: Sun, 7 Jul 2024 09:23:50 -0700
Organization: A noiseless patient Spider
Lines: 26
Message-ID: <v6efem$d3v6$2@dont-email.me>
References: <leto4eFasrbU6@mid.individual.net>
<v6cdk0$qnp$1@nnrp.usenet.blueworldhosting.com>
<letvsdFh2f2U1@mid.individual.net>
<v6ck9o$2o45$1@nnrp.usenet.blueworldhosting.com>
<levauqFmm0pU1@mid.individual.net>
<v6e626$15id$1@nnrp.usenet.blueworldhosting.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Sun, 07 Jul 2024 18:23:51 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="790cd3862da191afc565528a27af80b4";
logging-data="430054"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX196eJoRwx584pS2ZrkI96x+EApJTdyeXQM="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:d0XaL6Cl2RdHBpHt6ZIq6jcawMs=
Content-Language: en-CA
In-Reply-To: <v6e626$15id$1@nnrp.usenet.blueworldhosting.com>
View all headers

On 2024-07-07 06:43, Andrew wrote:
> Carlos E. R. wrote on Sun, 7 Jul 2024 13:02:50 +0200 :
>
>>> Does this "new" MLS stuff require both those privacy-destroying things?
>>
>> In the google implementation, it will require the same as the current
>> Google Messages app requires. This is just an (educated) guess.
>
> Hi Carlos,
> Well then, since I don't use Google apps, may I ask the team if the Google
> Messages app with RCS also requires those two privacy destroying things?
>
> Q: Does Google Messages with RCS require a login account for both users
> who wish to communicate on an end-to-end encrypted chat?
> A: Yes or no.

ANY MESSAGING APP is going to require some kind of login, Arlen.

How else can it possibly know which messages are going to go to which
recipient.

>
> If so, there's a privacy issue there...

No. There is not. Not as long as you can create an account with no
personally identifying information.

Subject: Re: Google is preparing to replace RCS with MLS
From: Carlos E. R.
Newsgroups: comp.mobile.android
Date: Sun, 7 Jul 2024 18:09 UTC
References: 1 2 3 4 5 6
Path: eternal-september.org!news.eternal-september.org!feeder3.eternal-september.org!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: robin_listas@es.invalid (Carlos E. R.)
Newsgroups: comp.mobile.android
Subject: Re: Google is preparing to replace RCS with MLS
Date: Sun, 7 Jul 2024 20:09:23 +0200
Lines: 45
Message-ID: <lf03ujFmm0pU3@mid.individual.net>
References: <leto4eFasrbU6@mid.individual.net>
<v6cdk0$qnp$1@nnrp.usenet.blueworldhosting.com>
<letvsdFh2f2U1@mid.individual.net>
<v6ck9o$2o45$1@nnrp.usenet.blueworldhosting.com>
<levauqFmm0pU1@mid.individual.net>
<v6e626$15id$1@nnrp.usenet.blueworldhosting.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: individual.net YFCH4NEBouGdZfgKnYea+AdSZes/ZFnsNqqJTT1orEQXNzm/H0
Cancel-Lock: sha1:mZSa0zDNkoUXsl8KLZbpmNqUyjA= sha256:Uo8cLxxlXsdXGrdg2Ck95A4y98hzT7lQX5V3YtBHL+A=
User-Agent: Mozilla Thunderbird
Content-Language: en-CA, es-ANY
In-Reply-To: <v6e626$15id$1@nnrp.usenet.blueworldhosting.com>
View all headers

On 2024-07-07 15:43, Andrew wrote:
> Carlos E. R. wrote on Sun, 7 Jul 2024 13:02:50 +0200 :
>
>>> Does this "new" MLS stuff require both those privacy-destroying things?
>>
>> In the google implementation, it will require the same as the current
>> Google Messages app requires. This is just an (educated) guess.
>
> Hi Carlos,
> Well then, since I don't use Google apps, may I ask the team if the Google
> Messages app with RCS also requires those two privacy destroying things?
>
> Q: Does Google Messages with RCS require a login account for both users
> who wish to communicate on an end-to-end encrypted chat?
> A: Yes or no.
>
> If so, there's a privacy issue there...

I assume that you have to login to the phone with the provider pin, to
power up the phone. And then requires the phone entry auth, which
normally these days it is a pattern with the finger. And normally this
assumes you logged in to Android/google.

I am not going to test without that login. You try that yourself.

>
>>> BTW, a new easy-to-remember Usenet search URI is this (which I made today).
>>> https://tinyurl.com/nova-comp-mobile-android
>>>
>>> Which complements the old easy-to-remember search URI I made long ago:
>>> https://tinyurl.com/comp-mobile-android
>>
>> I never use shorted links.
>
> The long link is hard to remember:

I don't care. Short links are a security issue. It means blindly
clicking on to an unknown site. And they can stop working in the future
for any reason.

--
Cheers,
Carlos E.R.

Subject: Re: Google is preparing to replace RCS with MLS
From: Andy Burns
Newsgroups: comp.mobile.android
Date: Sun, 7 Jul 2024 18:12 UTC
References: 1 2 3 4 5 6 7
Path: eternal-september.org!news.eternal-september.org!feeder3.eternal-september.org!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: usenet@andyburns.uk (Andy Burns)
Newsgroups: comp.mobile.android
Subject: Re: Google is preparing to replace RCS with MLS
Date: Sun, 7 Jul 2024 19:12:04 +0100
Lines: 12
Message-ID: <lf043nFqc3dU1@mid.individual.net>
References: <leto4eFasrbU6@mid.individual.net>
<v6cdk0$qnp$1@nnrp.usenet.blueworldhosting.com>
<letvsdFh2f2U1@mid.individual.net>
<v6ck9o$2o45$1@nnrp.usenet.blueworldhosting.com>
<levauqFmm0pU1@mid.individual.net>
<v6e626$15id$1@nnrp.usenet.blueworldhosting.com>
<lf03ujFmm0pU3@mid.individual.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: individual.net Kz4Ez5rTM0lImKCwGb+0OQLZAdRxnnrDJZ3Htgk9OiZ7UHSVEv
Cancel-Lock: sha1:k9uVPYElZK57/2tOfotyhga+GNo= sha256:EuQPgELutFqKUeBLtYW/OubQN1N/pm7hFT9hQ091WHg=
User-Agent: Mozilla Thunderbird
Content-Language: en-GB
In-Reply-To: <lf03ujFmm0pU3@mid.individual.net>
View all headers

Carlos E. R. wrote:

> I assume that you have to login to the phone with the provider pin, to
> power up the phone. And then requires the phone entry auth, which
> normally these days it is a pattern with the finger. And normally this
> assumes you logged in to Android/google.
>
> I am not going to test without that login. You try that yourself.

We know it's not compulsory to associate a google account with an
android phone, any guesses what percentage *do* have one?
Kind of pointless game as we have no way of finding out.

Subject: Re: Google is preparing to replace RCS with MLS
From: s|b
Newsgroups: comp.mobile.android
Organization: XXII
Date: Sun, 7 Jul 2024 18:51 UTC
References: 1 2 3 4 5 6 7
Path: eternal-september.org!news.eternal-september.org!feeder3.eternal-september.org!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: me@privacy.invalid (s|b)
Newsgroups: comp.mobile.android
Subject: Re: Google is preparing to replace RCS with MLS
Date: Sun, 07 Jul 2024 20:51:50 +0200
Organization: XXII
Lines: 13
Message-ID: <lf06e6Fr6k6U2@mid.individual.net>
References: <leto4eFasrbU6@mid.individual.net> <v6cdk0$qnp$1@nnrp.usenet.blueworldhosting.com> <letvsdFh2f2U1@mid.individual.net> <v6ck9o$2o45$1@nnrp.usenet.blueworldhosting.com> <levauqFmm0pU1@mid.individual.net> <v6e626$15id$1@nnrp.usenet.blueworldhosting.com> <v6efem$d3v6$2@dont-email.me>
Reply-To: sb.nospam@belgacom.net
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: individual.net ndJimDp9RH3vc/6MHPA3WwwjW10s6N6RUoJ6xX9aXhTJSnGxBW
Cancel-Lock: sha1:Qdnso1S5fdlNVdYMgaTh2KgHVy8= sha256:4sOE4ctLHXZ893qJjCuUvYPlDTlanHsobpEb27RiG9A=
User-Agent: ForteAgent/8.00.32.1272
X-Face: j0\WO?Dcjo^V#d7Q,H$9^8N{Z|fy50vxQkToel)jNR3hmCMV8kai(fMVJ:Yk}q?t<:xHu2D )?CJ[c|zu]%I!fKb7-4~$&Mx|GT=>ux^*,A:5Cdek,y4A(DSX=oXRv7-)/AcgHiWf
View all headers

On Sun, 7 Jul 2024 09:23:50 -0700, Alan wrote:

> ANY MESSAGING APP is going to require some kind of login, Arlen.
>
> How else can it possibly know which messages are going to go to which
> recipient.

How about telephone number. RCS can be used in the default Android SMS
(text) app, but both recipients need to support it. I tried it once with
my brother. No login needed.

--
s|b

Subject: Re: Google is preparing to replace RCS with MLS
From: Andrew
Newsgroups: comp.mobile.android
Organization: BWH Usenet Archive (https://usenet.blueworldhosting.com)
Date: Sun, 7 Jul 2024 18:51 UTC
References: 1 2 3 4 5 6 7 8
Path: eternal-september.org!news.eternal-september.org!feeder3.eternal-september.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!nnrp.usenet.blueworldhosting.com!.POSTED!not-for-mail
From: andrew@spam.net (Andrew)
Newsgroups: comp.mobile.android
Subject: Re: Google is preparing to replace RCS with MLS
Date: Sun, 7 Jul 2024 18:51:52 -0000 (UTC)
Organization: BWH Usenet Archive (https://usenet.blueworldhosting.com)
Message-ID: <v6eo47$2ltv$1@nnrp.usenet.blueworldhosting.com>
References: <leto4eFasrbU6@mid.individual.net> <v6cdk0$qnp$1@nnrp.usenet.blueworldhosting.com> <letvsdFh2f2U1@mid.individual.net> <v6ck9o$2o45$1@nnrp.usenet.blueworldhosting.com> <levauqFmm0pU1@mid.individual.net> <v6e626$15id$1@nnrp.usenet.blueworldhosting.com> <lf03ujFmm0pU3@mid.individual.net> <lf043nFqc3dU1@mid.individual.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Sun, 7 Jul 2024 18:51:52 -0000 (UTC)
Injection-Info: nnrp.usenet.blueworldhosting.com;
logging-data="87999"; mail-complaints-to="usenet@blueworldhosting.com"
User-Agent: NewsTap/5.5 (iPad)
Cancel-Lock: sha1:EgJaxihvXAXr2J81Dj5gdbndRJ0= sha256:w11nP9zLHRBISFayac2Xfn9fgzhDsNVH+/nRigKMUHM=
sha1:+8RD7wli1fWQR7Pt2otSLY0syns= sha256:UETbOwPtqElivxe4Ng+XS9o0IC0a1capo4fLXY2D10A=
X-Face: VQ}*Ueh[4uTOa]Md([|$jb%rw~ksq}bzqA;z-.*8JM`4+zL[`N\ORHCI80}]}$]$e5]/i#v qdYsE`yh@ZL3L{H:So{yN)b=AZJtpaP98ch_4W}
View all headers

Andy Burns wrote on Sun, 7 Jul 2024 19:12:04 +0100 :

>> I assume that you have to login to the phone with the provider pin, to
>> power up the phone. And then requires the phone entry auth, which
>> normally these days it is a pattern with the finger. And normally this
>> assumes you logged in to Android/google.
>>
>> I am not going to test without that login. You try that yourself.
>
> We know it's not compulsory to associate a google account with an
> android phone, any guesses what percentage *do* have one?
> Kind of pointless game as we have no way of finding out.

To Andy's quite valid pragmatically sensible observation...

1. We all know I don't have a Google Account set up on my phone, and
we all know I can likely do more than most people, right?

So we know the Google Account isn't required just to do things
like messaging (which I do all day, every day, with iOS & Android
users despite the moronic Apple users not understanding that).

You just have to be intelligent about using the phone w/o Google.
That's all.

2. However.... we also know that ~99.99% of people do exactly
what the phone tells them to do - which - of course - is to
set up a Google Account on that phone - which means - to Andy's
question - I'd guess the percentage is ~99.99% (give or take)
who, like the idiotic iPhone users, blindly log into Google
servers every moment of every day of the rest of their lives.

3. So I get Andy's point that, if MLS requires a login account,
and, in fact, if MLS requires both participants to have a
login account on the same Google server, then it's not such
a privacy flaw as I make it out to be (as they're already dead).

However, that doesn't change the question nor the answer to it, right?

Q: Does RCS require both participants to log into a server or not?
Q: Does ENCRYPTED RCS require both to log into a server or not?
Q: Does MLS require both participants to log into the same server?

Any idea?

Subject: Re: Google is preparing to replace RCS with MLS
From: Alan
Newsgroups: comp.mobile.android
Organization: A noiseless patient Spider
Date: Sun, 7 Jul 2024 18:55 UTC
References: 1 2 3 4 5 6 7 8
Path: eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: nuh-uh@nope.com (Alan)
Newsgroups: comp.mobile.android
Subject: Re: Google is preparing to replace RCS with MLS
Date: Sun, 7 Jul 2024 11:55:13 -0700
Organization: A noiseless patient Spider
Lines: 14
Message-ID: <v6eoah$ethv$1@dont-email.me>
References: <leto4eFasrbU6@mid.individual.net>
<v6cdk0$qnp$1@nnrp.usenet.blueworldhosting.com>
<letvsdFh2f2U1@mid.individual.net>
<v6ck9o$2o45$1@nnrp.usenet.blueworldhosting.com>
<levauqFmm0pU1@mid.individual.net>
<v6e626$15id$1@nnrp.usenet.blueworldhosting.com>
<v6efem$d3v6$2@dont-email.me> <lf06e6Fr6k6U2@mid.individual.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Sun, 07 Jul 2024 20:55:13 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="790cd3862da191afc565528a27af80b4";
logging-data="489023"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX199XW9SindX4TPgeGapdhUCrDLvFR7dnoo="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:R3AMoDkNpwVFY7T4JZ+i9273FFE=
In-Reply-To: <lf06e6Fr6k6U2@mid.individual.net>
Content-Language: en-CA
View all headers

On 2024-07-07 11:51, s|b wrote:
> On Sun, 7 Jul 2024 09:23:50 -0700, Alan wrote:
>
>> ANY MESSAGING APP is going to require some kind of login, Arlen.
>>
>> How else can it possibly know which messages are going to go to which
>> recipient.
>
> How about telephone number. RCS can be used in the default Android SMS
> (text) app, but both recipients need to support it. I tried it once with
> my brother. No login needed.
>

You think a telephone number isn't equivalent to a login?

Subject: Re: Google is preparing to replace RCS with MLS
From: Alan
Newsgroups: comp.mobile.android
Organization: A noiseless patient Spider
Date: Sun, 7 Jul 2024 18:56 UTC
References: 1 2 3 4 5 6 7 8 9
Path: eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: nuh-uh@nope.com (Alan)
Newsgroups: comp.mobile.android
Subject: Re: Google is preparing to replace RCS with MLS
Date: Sun, 7 Jul 2024 11:56:57 -0700
Organization: A noiseless patient Spider
Lines: 56
Message-ID: <v6eodp$ethv$2@dont-email.me>
References: <leto4eFasrbU6@mid.individual.net>
<v6cdk0$qnp$1@nnrp.usenet.blueworldhosting.com>
<letvsdFh2f2U1@mid.individual.net>
<v6ck9o$2o45$1@nnrp.usenet.blueworldhosting.com>
<levauqFmm0pU1@mid.individual.net>
<v6e626$15id$1@nnrp.usenet.blueworldhosting.com>
<lf03ujFmm0pU3@mid.individual.net> <lf043nFqc3dU1@mid.individual.net>
<v6eo47$2ltv$1@nnrp.usenet.blueworldhosting.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Sun, 07 Jul 2024 20:56:58 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="790cd3862da191afc565528a27af80b4";
logging-data="489023"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19E2luWvUsK+A+dMLuqdoHJT/rEgSOlTU0="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:XbDFQ4QuTt40/FrEOuG6bdzqwHo=
Content-Language: en-CA
In-Reply-To: <v6eo47$2ltv$1@nnrp.usenet.blueworldhosting.com>
View all headers

On 2024-07-07 11:51, Andrew wrote:
> Andy Burns wrote on Sun, 7 Jul 2024 19:12:04 +0100 :
>
>>> I assume that you have to login to the phone with the provider pin, to
>>> power up the phone. And then requires the phone entry auth, which
>>> normally these days it is a pattern with the finger. And normally this
>>> assumes you logged in to Android/google.
>>>
>>> I am not going to test without that login. You try that yourself.
>>
>> We know it's not compulsory to associate a google account with an
>> android phone, any guesses what percentage *do* have one?
>> Kind of pointless game as we have no way of finding out.
>
> To Andy's quite valid pragmatically sensible observation...
>
> 1. We all know I don't have a Google Account set up on my phone, and
> we all know I can likely do more than most people, right?

No one here knows either of those things for a fact.

We know you CLAIM both of those things.

>
> So we know the Google Account isn't required just to do things
> like messaging (which I do all day, every day, with iOS & Android
> users despite the moronic Apple users not understanding that).

An account doesn't have to be a Google account.

>
> You just have to be intelligent about using the phone w/o Google.
> That's all.
>
> 2. However.... we also know that ~99.99% of people do exactly
> what the phone tells them to do - which - of course - is to
> set up a Google Account on that phone - which means - to Andy's
> question - I'd guess the percentage is ~99.99% (give or take)
> who, like the idiotic iPhone users, blindly log into Google
> servers every moment of every day of the rest of their lives.
>
> 3. So I get Andy's point that, if MLS requires a login account,
> and, in fact, if MLS requires both participants to have a
> login account on the same Google server, then it's not such
> a privacy flaw as I make it out to be (as they're already dead).
>
> However, that doesn't change the question nor the answer to it, right?
>
> Q: Does RCS require both participants to log into a server or not?
> Q: Does ENCRYPTED RCS require both to log into a server or not?
> Q: Does MLS require both participants to log into the same server?
>
> Any idea?

How do you imagine messages get from your phone to someone else's
without going through a server, you idiot?

Subject: Re: Google is preparing to replace RCS with MLS
From: Andrew
Newsgroups: comp.mobile.android
Organization: BWH Usenet Archive (https://usenet.blueworldhosting.com)
Date: Sun, 7 Jul 2024 18:58 UTC
References: 1 2 3 4 5 6 7 8
Path: eternal-september.org!news.eternal-september.org!feeder3.eternal-september.org!panix!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!nnrp.usenet.blueworldhosting.com!.POSTED!not-for-mail
From: andrew@spam.net (Andrew)
Newsgroups: comp.mobile.android
Subject: Re: Google is preparing to replace RCS with MLS
Date: Sun, 7 Jul 2024 18:58:01 -0000 (UTC)
Organization: BWH Usenet Archive (https://usenet.blueworldhosting.com)
Message-ID: <v6eofp$dod$1@nnrp.usenet.blueworldhosting.com>
References: <leto4eFasrbU6@mid.individual.net> <v6cdk0$qnp$1@nnrp.usenet.blueworldhosting.com> <letvsdFh2f2U1@mid.individual.net> <v6ck9o$2o45$1@nnrp.usenet.blueworldhosting.com> <levauqFmm0pU1@mid.individual.net> <v6e626$15id$1@nnrp.usenet.blueworldhosting.com> <v6efem$d3v6$2@dont-email.me> <lf06e6Fr6k6U2@mid.individual.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Sun, 7 Jul 2024 18:58:01 -0000 (UTC)
Injection-Info: nnrp.usenet.blueworldhosting.com;
logging-data="14093"; mail-complaints-to="usenet@blueworldhosting.com"
User-Agent: NewsTap/5.5 (iPad)
Cancel-Lock: sha1:+oLNdwZuj//ObjZmm/vxvgFSGHs= sha256:wdS+AQn5OWr/csEYlfN3T6ugzOoK0pUH1HRtR1oSKjQ=
sha1:OrUl4U/nrLW7FZb+df0qSfKwb7M= sha256:l7xi+tyocj4wsZX/JWE7ZcbCM1y4UeBTbyxTkJqVFHo=
X-Face: VQ}*Ueh[4uTOa]Md([|$jb%rw~ksq}bzqA;z-.*8JM`4+zL[`N\ORHCI80}]}$]$e5]/i#v qdYsE`yh@ZL3L{H:So{yN)b=AZJtpaP98ch_4W}
View all headers

s|b wrote on Sun, 07 Jul 2024 20:51:50 +0200 :

>> ANY MESSAGING APP is going to require some kind of login, Arlen.
>>
>> How else can it possibly know which messages are going to go to which
>> recipient.
>
> How about telephone number. RCS can be used in the default Android SMS
> (text) app, but both recipients need to support it. I tried it once with
> my brother. No login needed.

Oh God. The Apple religious zealot Alan Baker has infested this thread.

I've been on Usenet for decades, and he is one of only a handful of people
I've plonked - as there's nothing from him that ever adds any value.

Based on what SorB quoted, Alan Baker (who is an Apple moron, by the way),
thinks that we actually "log into" an account to send/receive messages.

It won't matter that none of us do that - he does it - so he thinks
everyone else does - because Apple literally requires the privacy-robbing
login account to be used every day for the rest of your living life.

Anyway, every time Alan Baker posts, he subtracts value, but the point of
my question is only whether or not RCS and MLS require that login account.

Subject: Re: Google is preparing to replace RCS with MLS
From: Alan
Newsgroups: comp.mobile.android
Organization: A noiseless patient Spider
Date: Sun, 7 Jul 2024 19:02 UTC
References: 1 2 3 4 5 6 7 8 9
Path: eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: nuh-uh@nope.com (Alan)
Newsgroups: comp.mobile.android
Subject: Re: Google is preparing to replace RCS with MLS
Date: Sun, 7 Jul 2024 12:02:57 -0700
Organization: A noiseless patient Spider
Lines: 42
Message-ID: <v6eop1$ethv$3@dont-email.me>
References: <leto4eFasrbU6@mid.individual.net>
<v6cdk0$qnp$1@nnrp.usenet.blueworldhosting.com>
<letvsdFh2f2U1@mid.individual.net>
<v6ck9o$2o45$1@nnrp.usenet.blueworldhosting.com>
<levauqFmm0pU1@mid.individual.net>
<v6e626$15id$1@nnrp.usenet.blueworldhosting.com>
<v6efem$d3v6$2@dont-email.me> <lf06e6Fr6k6U2@mid.individual.net>
<v6eofp$dod$1@nnrp.usenet.blueworldhosting.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Sun, 07 Jul 2024 21:02:58 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="790cd3862da191afc565528a27af80b4";
logging-data="489023"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19LTZJ3Cfl78CUX327Z1OQUmFYUcUXSVOs="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:BetXuG0DRBifWHKhQT8HmEZeyfM=
In-Reply-To: <v6eofp$dod$1@nnrp.usenet.blueworldhosting.com>
Content-Language: en-CA
View all headers

On 2024-07-07 11:58, Andrew wrote:
> s|b wrote on Sun, 07 Jul 2024 20:51:50 +0200 :
>
>>> ANY MESSAGING APP is going to require some kind of login, Arlen.
>>>
>>> How else can it possibly know which messages are going to go to which
>>> recipient.
>>
>> How about telephone number. RCS can be used in the default Android SMS
>> (text) app, but both recipients need to support it. I tried it once with
>> my brother. No login needed.
>
> Oh God. The Apple religious zealot Alan Baker has infested this thread.
>
> I've been on Usenet for decades, and he is one of only a handful of people
> I've plonked - as there's nothing from him that ever adds any value.
>
> Based on what SorB quoted, Alan Baker (who is an Apple moron, by the way),
> thinks that we actually "log into" an account to send/receive messages.

You do "log into" an account, you simpleton.

It might be with a SIM card, but it's the same thing.

>
> It won't matter that none of us do that - he does it - so he thinks
> everyone else does - because Apple literally requires the privacy-robbing
> login account to be used every day for the rest of your living life.
>
> Anyway, every time Alan Baker posts, he subtracts value, but the point of
> my question is only whether or not RCS and MLS require that login account.

RCS and MLS are PROTOCOLS, doofus.

Services that USE those protocols will require some kind of
identification (i.e. a "login") in order to route a message from one
user of such a service to another.

For the low IQ here (that's you, Arlen):

Any service that needs to deliver messages to a recipient is going to
need that recipient to "log in" in some fashion.

Subject: Re: Google is preparing to replace RCS with MLS
From: s|b
Newsgroups: comp.mobile.android
Organization: XXII
Date: Sun, 7 Jul 2024 19:04 UTC
References: 1
Path: eternal-september.org!news.eternal-september.org!feeder3.eternal-september.org!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: me@privacy.invalid (s|b)
Newsgroups: comp.mobile.android
Subject: Re: Google is preparing to replace RCS with MLS
Date: Sun, 07 Jul 2024 21:04:22 +0200
Organization: XXII
Lines: 17
Message-ID: <lf075mFraujU1@mid.individual.net>
References: <leto4eFasrbU6@mid.individual.net>
Reply-To: sb.nospam@belgacom.net
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: individual.net 7vrYD31KoSYElMjrdNp1mAD1V4/IBcENjRxxKAdIHsF+gMWo7C
Cancel-Lock: sha1:PXNEnHJGLqxSe7i8gpb5mR7XHHg= sha256:kGdjkPypkKBSiQQxlsUekd8vUpEVMa2UHawKLrXJGEE=
User-Agent: ForteAgent/8.00.32.1272
X-Face: j0\WO?Dcjo^V#d7Q,H$9^8N{Z|fy50vxQkToel)jNR3hmCMV8kai(fMVJ:Yk}q?t<:xHu2D )?CJ[c|zu]%I!fKb7-4~$&Mx|GT=>ux^*,A:5Cdek,y4A(DSX=oXRv7-)/AcgHiWf
View all headers

On Sat, 6 Jul 2024 22:35:26 +0200, Carlos E. R. wrote:

> * Evidence suggests Google Messages will soon add Messaging Layer
> Security (MLS) support for end-to-end encryption.

It's all show. The European Union wants access to our encrypted
messages, supposedly in the fight against kiddie porn. A proposition was
called and they needed 65% for it to vote. 62,3% thought it was a good
idea, so no vote, not yet. They've been talking about this for years and
it's going to happen.

Signal already said they will leave Europe if this happens, because the
EU's software will break the end-to-end encryption. But Meta and Google?
They'll stay and collect you (meta)data.

--
s|b

Subject: Re: Google is preparing to replace RCS with MLS
From: Andrew
Newsgroups: comp.mobile.android
Organization: BWH Usenet Archive (https://usenet.blueworldhosting.com)
Date: Sun, 7 Jul 2024 20:31 UTC
References: 1 2
Path: eternal-september.org!news.eternal-september.org!feeder3.eternal-september.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!nnrp.usenet.blueworldhosting.com!.POSTED!not-for-mail
From: andrew@spam.net (Andrew)
Newsgroups: comp.mobile.android
Subject: Re: Google is preparing to replace RCS with MLS
Date: Sun, 7 Jul 2024 20:31:14 -0000 (UTC)
Organization: BWH Usenet Archive (https://usenet.blueworldhosting.com)
Message-ID: <v6etuh$2k3h$1@nnrp.usenet.blueworldhosting.com>
References: <leto4eFasrbU6@mid.individual.net> <lf075mFraujU1@mid.individual.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Sun, 7 Jul 2024 20:31:14 -0000 (UTC)
Injection-Info: nnrp.usenet.blueworldhosting.com;
logging-data="86129"; mail-complaints-to="usenet@blueworldhosting.com"
User-Agent: NewsTap/5.5 (iPad)
Cancel-Lock: sha1:ipH4mz/NOEy1Ev8SI0OaO8fRsrY= sha256:BnpbhILHEKYl9eUj3ghdkyOFJSFWuWZzRAfmcoRuSkE=
sha1:BhdixhcAhtoEQaGF5kkYKzswbvc= sha256:+KEzRvn0yOTVQqUojXqNUSJ7sA16EOMLEprRddyL4GE=
X-Face: VQ}*Ueh[4uTOa]Md([|$jb%rw~ksq}bzqA;z-.*8JM`4+zL[`N\ORHCI80}]}$]$e5]/i#v qdYsE`yh@ZL3L{H:So{yN)b=AZJtpaP98ch_4W}
View all headers

s|b wrote on Sun, 07 Jul 2024 21:04:22 +0200 :

> It's all show. The European Union wants access to our encrypted
> messages, supposedly in the fight against kiddie porn. A proposition was
> called and they needed 65% for it to vote. 62,3% thought it was a good
> idea, so no vote, not yet. They've been talking about this for years and
> it's going to happen.
>
> Signal already said they will leave Europe if this happens, because the
> EU's software will break the end-to-end encryption. But Meta and Google?
> They'll stay and collect you (meta)data.

This is good to know 'cuz the instant you log into an account on Internet
servers, your metadata will throw your privacy under the bus.

Subject: Re: Google is preparing to replace RCS with MLS
From: Jörg Lorenz
Newsgroups: comp.mobile.android
Organization: Camembert Normand au Lait Cru
Date: Sun, 7 Jul 2024 20:43 UTC
References: 1 2
Path: eternal-september.org!news.eternal-september.org!feeder3.eternal-september.org!weretis.net!feeder8.news.weretis.net!reader5.news.weretis.net!news.solani.org!.POSTED!not-for-mail
From: hugybear@gmx.net (Jörg Lorenz)
Newsgroups: comp.mobile.android
Subject: Re: Google is preparing to replace RCS with MLS
Date: Sun, 7 Jul 2024 22:43:15 +0200
Organization: Camembert Normand au Lait Cru
Message-ID: <v6eul3$a8jf$1@solani.org>
References: <leto4eFasrbU6@mid.individual.net>
<lf075mFraujU1@mid.individual.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Injection-Date: Sun, 7 Jul 2024 20:43:16 -0000 (UTC)
Injection-Info: solani.org;
logging-data="336495"; mail-complaints-to="abuse@news.solani.org"
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:115.0)
Gecko/20100101 Thunderbird/115.12.1
Cancel-Lock: sha1:1T2GnWPT0Zuh6i+CVlfLPJAqF4k=
X-User-ID: eJwNycEBwCAIA8CVTIFIxqEo+4/Q3vfCCPZ2Bj0mBvmeGD/da3HfapeQqDE1ph5dG1EJaf2dHyUWERw=
In-Reply-To: <lf075mFraujU1@mid.individual.net>
Content-Language: de-CH
View all headers

Am 07.07.24 um 21:04 schrieb s|b:
> On Sat, 6 Jul 2024 22:35:26 +0200, Carlos E. R. wrote:
>
>> * Evidence suggests Google Messages will soon add Messaging Layer
>> Security (MLS) support for end-to-end encryption.
>
> It's all show. The European Union wants access to our encrypted
> messages, supposedly in the fight against kiddie porn. A proposition was
> called and they needed 65% for it to vote. 62,3% thought it was a good
> idea, so no vote, not yet. They've been talking about this for years and
> it's going to happen.
>
> Signal already said they will leave Europe if this happens, because the
> EU's software will break the end-to-end encryption. But Meta and Google?
> They'll stay and collect you (meta)data.

*Everything* utter nonsense.

--
"Manus manum lavat."

Subject: Re: Google is preparing to replace RCS with MLS
From: Alan
Newsgroups: comp.mobile.android
Organization: A noiseless patient Spider
Date: Sun, 7 Jul 2024 21:17 UTC
References: 1 2 3
Path: eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: nuh-uh@nope.com (Alan)
Newsgroups: comp.mobile.android
Subject: Re: Google is preparing to replace RCS with MLS
Date: Sun, 7 Jul 2024 14:17:11 -0700
Organization: A noiseless patient Spider
Lines: 17
Message-ID: <v6f0kn$gac2$1@dont-email.me>
References: <leto4eFasrbU6@mid.individual.net>
<lf075mFraujU1@mid.individual.net>
<v6etuh$2k3h$1@nnrp.usenet.blueworldhosting.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Sun, 07 Jul 2024 23:17:12 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="790cd3862da191afc565528a27af80b4";
logging-data="534914"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+7yeLLa6XWkEGZdQf+IGmVqZq4EapIQ88="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:ktgTAWb9QS0Y0jzdCvN+BeLPFu4=
Content-Language: en-CA
In-Reply-To: <v6etuh$2k3h$1@nnrp.usenet.blueworldhosting.com>
View all headers

On 2024-07-07 13:31, Andrew wrote:
> s|b wrote on Sun, 07 Jul 2024 21:04:22 +0200 :
>
>> It's all show. The European Union wants access to our encrypted
>> messages, supposedly in the fight against kiddie porn. A proposition was
>> called and they needed 65% for it to vote. 62,3% thought it was a good
>> idea, so no vote, not yet. They've been talking about this for years and
>> it's going to happen.
>>
>> Signal already said they will leave Europe if this happens, because the
>> EU's software will break the end-to-end encryption. But Meta and Google?
>> They'll stay and collect you (meta)data.
>
> This is good to know 'cuz the instant you log into an account on Internet
> servers, your metadata will throw your privacy under the bus.

That would depend on what data the account has about you.

Subject: Re: Google is preparing to replace RCS with MLS
From: Carlos E. R.
Newsgroups: comp.mobile.android
Date: Mon, 8 Jul 2024 00:58 UTC
References: 1 2 3 4 5 6 7 8
Path: eternal-september.org!news.eternal-september.org!feeder3.eternal-september.org!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: robin_listas@es.invalid (Carlos E. R.)
Newsgroups: comp.mobile.android
Subject: Re: Google is preparing to replace RCS with MLS
Date: Mon, 8 Jul 2024 02:58:15 +0200
Lines: 18
Message-ID: <lf0rt7Fmm0pU8@mid.individual.net>
References: <leto4eFasrbU6@mid.individual.net>
<v6cdk0$qnp$1@nnrp.usenet.blueworldhosting.com>
<letvsdFh2f2U1@mid.individual.net>
<v6ck9o$2o45$1@nnrp.usenet.blueworldhosting.com>
<levauqFmm0pU1@mid.individual.net>
<v6e626$15id$1@nnrp.usenet.blueworldhosting.com>
<v6efem$d3v6$2@dont-email.me> <lf06e6Fr6k6U2@mid.individual.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: individual.net QEsa92MvlXORedeTeAy8SgcNbntMBAnbMPfTi9v3dEB4xLinGA
Cancel-Lock: sha1:oFRNUXz3YcnGosug53+TTamTfpQ= sha256:EV4oYTpxa8qZ2bpqPHRIAtvnobUUxiOPBEkRl9C3uKk=
User-Agent: Mozilla Thunderbird
Content-Language: en-CA, es-ANY
In-Reply-To: <lf06e6Fr6k6U2@mid.individual.net>
View all headers

On 2024-07-07 20:51, s|b wrote:
> On Sun, 7 Jul 2024 09:23:50 -0700, Alan wrote:
>
>> ANY MESSAGING APP is going to require some kind of login, Arlen.
>>
>> How else can it possibly know which messages are going to go to which
>> recipient.
>
> How about telephone number. RCS can be used in the default Android SMS
> (text) app, but both recipients need to support it. I tried it once with
> my brother. No login needed.

You are mistaken. There is a login to the phone when you power it up.

--
Cheers,
Carlos E.R.

Subject: Re: Google is preparing to replace RCS with MLS
From: Alan
Newsgroups: comp.mobile.android
Organization: A noiseless patient Spider
Date: Mon, 8 Jul 2024 01:02 UTC
References: 1 2 3 4 5 6 7 8 9
Path: eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: nuh-uh@nope.com (Alan)
Newsgroups: comp.mobile.android
Subject: Re: Google is preparing to replace RCS with MLS
Date: Sun, 7 Jul 2024 18:02:36 -0700
Organization: A noiseless patient Spider
Lines: 20
Message-ID: <v6fdrc$ico8$2@dont-email.me>
References: <leto4eFasrbU6@mid.individual.net>
<v6cdk0$qnp$1@nnrp.usenet.blueworldhosting.com>
<letvsdFh2f2U1@mid.individual.net>
<v6ck9o$2o45$1@nnrp.usenet.blueworldhosting.com>
<levauqFmm0pU1@mid.individual.net>
<v6e626$15id$1@nnrp.usenet.blueworldhosting.com>
<v6efem$d3v6$2@dont-email.me> <lf06e6Fr6k6U2@mid.individual.net>
<lf0rt7Fmm0pU8@mid.individual.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Mon, 08 Jul 2024 03:02:37 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="5d2197d93767afcb41668b32eec1d61b";
logging-data="602888"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+EWmHTHiXrrT5+Azx3IScsyKS8iWcZW6s="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:iwGQyFoBnGPjX9ckBgJADW5O+zA=
Content-Language: en-CA
In-Reply-To: <lf0rt7Fmm0pU8@mid.individual.net>
View all headers

On 2024-07-07 17:58, Carlos E. R. wrote:
> On 2024-07-07 20:51, s|b wrote:
>> On Sun, 7 Jul 2024 09:23:50 -0700, Alan wrote:
>>
>>> ANY MESSAGING APP is going to require some kind of login, Arlen.
>>>
>>> How else can it possibly know which messages are going to go to which
>>> recipient.
>>
>> How about telephone number. RCS can be used in the default Android SMS
>> (text) app, but both recipients need to support it. I tried it once with
>> my brother. No login needed.
>
> You are mistaken. There is a login to the phone when you power it up.
>

Yup.

And the SIM card that does the "logging in" is connected to your
account, which is most definitely connected to your personal data.

Subject: Re: Google is preparing to replace RCS with MLS
From: Andrew
Newsgroups: comp.mobile.android
Organization: BWH Usenet Archive (https://usenet.blueworldhosting.com)
Date: Mon, 8 Jul 2024 02:08 UTC
References: 1 2 3 4 5 6 7 8 9
Path: eternal-september.org!news.eternal-september.org!feeder3.eternal-september.org!news.swapon.de!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!nnrp.usenet.blueworldhosting.com!.POSTED!not-for-mail
From: andrew@spam.net (Andrew)
Newsgroups: comp.mobile.android
Subject: Re: Google is preparing to replace RCS with MLS
Date: Mon, 8 Jul 2024 02:08:24 -0000 (UTC)
Organization: BWH Usenet Archive (https://usenet.blueworldhosting.com)
Message-ID: <v6fhmo$2t3q$1@nnrp.usenet.blueworldhosting.com>
References: <leto4eFasrbU6@mid.individual.net> <v6cdk0$qnp$1@nnrp.usenet.blueworldhosting.com> <letvsdFh2f2U1@mid.individual.net> <v6ck9o$2o45$1@nnrp.usenet.blueworldhosting.com> <levauqFmm0pU1@mid.individual.net> <v6e626$15id$1@nnrp.usenet.blueworldhosting.com> <v6efem$d3v6$2@dont-email.me> <lf06e6Fr6k6U2@mid.individual.net> <lf0rt7Fmm0pU8@mid.individual.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Mon, 8 Jul 2024 02:08:24 -0000 (UTC)
Injection-Info: nnrp.usenet.blueworldhosting.com;
logging-data="95354"; mail-complaints-to="usenet@blueworldhosting.com"
User-Agent: NewsTap/5.5 (iPad)
Cancel-Lock: sha1:HFcEFSxGG2CymnU5gvGB8XN+Iyg= sha256:MO8S8MNOajyPJEmJ6An8sQJYsPLA/PPsH4aYwYWmAjE=
sha1:iVxCfNLiPO87DHSzFXK4XeCB0lc= sha256:xrXU+nkGG6DiZxerwobK+moBRQrdIB8/OZbLrADuUEk=
X-Face: VQ}*Ueh[4uTOa]Md([|$jb%rw~ksq}bzqA;z-.*8JM`4+zL[`N\ORHCI80}]}$]$e5]/i#v qdYsE`yh@ZL3L{H:So{yN)b=AZJtpaP98ch_4W}
View all headers

Carlos E. R. wrote on Mon, 8 Jul 2024 02:58:15 +0200 :

>> How about telephone number. RCS can be used in the default Android SMS
>> (text) app, but both recipients need to support it. I tried it once with
>> my brother. No login needed.
>
> You are mistaken. There is a login to the phone when you power it up.

Hi Carlos,

Let's take the simplest case, which is I have a drawer full of Android
tablets in front of me, where I can easily connect them to the Internet,
and with that I can do everything but make cellular phone calls, right?

In that case, where is this login you speak of when I power them up?

Subject: Re: Google is preparing to replace RCS with MLS
From: Carlos E. R.
Newsgroups: comp.mobile.android
Date: Mon, 8 Jul 2024 10:42 UTC
References: 1 2 3 4 5 6 7 8 9 10
Path: eternal-september.org!news.eternal-september.org!feeder3.eternal-september.org!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: robin_listas@es.invalid (Carlos E. R.)
Newsgroups: comp.mobile.android
Subject: Re: Google is preparing to replace RCS with MLS
Date: Mon, 8 Jul 2024 12:42:05 +0200
Lines: 21
Message-ID: <lf1u3tF4e6pU1@mid.individual.net>
References: <leto4eFasrbU6@mid.individual.net>
<v6cdk0$qnp$1@nnrp.usenet.blueworldhosting.com>
<letvsdFh2f2U1@mid.individual.net>
<v6ck9o$2o45$1@nnrp.usenet.blueworldhosting.com>
<levauqFmm0pU1@mid.individual.net>
<v6e626$15id$1@nnrp.usenet.blueworldhosting.com>
<v6efem$d3v6$2@dont-email.me> <lf06e6Fr6k6U2@mid.individual.net>
<lf0rt7Fmm0pU8@mid.individual.net>
<v6fhmo$2t3q$1@nnrp.usenet.blueworldhosting.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: individual.net dOz8bI+032Zg+InlBW7ACgJ4/ChOH5xSE/fhkqAWVHahlQR3H+
Cancel-Lock: sha1:pO/GfP8eExIZNdAUlXyzmDIJ2x4= sha256:vjC0Pn9TbJ3H+F+iqkc0vgh/06CutkwpKrkh+jgF6+0=
User-Agent: Mozilla Thunderbird
Content-Language: en-CA, es-ANY
In-Reply-To: <v6fhmo$2t3q$1@nnrp.usenet.blueworldhosting.com>
View all headers

On 2024-07-08 04:08, Andrew wrote:
> Carlos E. R. wrote on Mon, 8 Jul 2024 02:58:15 +0200 :
>
>>> How about telephone number. RCS can be used in the default Android SMS
>>> (text) app, but both recipients need to support it. I tried it once with
>>> my brother. No login needed.
>>
>> You are mistaken. There is a login to the phone when you power it up.
>
> Hi Carlos,
>
> Let's take the simplest case, which is I have a drawer full of Android
> tablets in front of me, where I can easily connect them to the Internet,
> and with that I can do everything but make cellular phone calls, right?

Thus you can not make messages.

--
Cheers,
Carlos E.R.

Subject: Re: Google is preparing to replace RCS with MLS
From: s|b
Newsgroups: comp.mobile.android
Organization: XXII
Date: Mon, 8 Jul 2024 14:33 UTC
References: 1 2 3
Path: eternal-september.org!news.eternal-september.org!feeder3.eternal-september.org!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: me@privacy.invalid (s|b)
Newsgroups: comp.mobile.android
Subject: Re: Google is preparing to replace RCS with MLS
Date: Mon, 08 Jul 2024 16:33:15 +0200
Organization: XXII
Lines: 11
Message-ID: <lf2blbF6mslU1@mid.individual.net>
References: <leto4eFasrbU6@mid.individual.net> <lf075mFraujU1@mid.individual.net> <v6eul3$a8jf$1@solani.org>
Reply-To: sb.nospam@belgacom.net
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: individual.net CcAjLarLTSeiU9SmoaE/WgmNX1fknZSTCWNs3gEucKk1NPBrrn
Cancel-Lock: sha1:gNPxskDZZdBDhZYxjvwjYPuJ5GU= sha256:+QtYZRJ3/HRJ/cSN5Qp68RKfsRDTfDH5bqg+qBAnx/A=
User-Agent: ForteAgent/8.00.32.1272
X-Face: j0\WO?Dcjo^V#d7Q,H$9^8N{Z|fy50vxQkToel)jNR3hmCMV8kai(fMVJ:Yk}q?t<:xHu2D )?CJ[c|zu]%I!fKb7-4~$&Mx|GT=>ux^*,A:5Cdek,y4A(DSX=oXRv7-)/AcgHiWf
View all headers

On Sun, 7 Jul 2024 22:43:15 +0200, Jörg Lorenz wrote:

> *Everything* utter nonsense.

Don't just throw a one liner at it, debunk it.

<https://netzpolitik.org/2024/etappensieg-belgien-scheitert-mit-abstimmung-zur-chatkontrolle/>
<https://www.security.nl/posting/846765/EU-voorzitter+Belgi%C3%AB+schrapt+stemming+chatcontrole+wegens+te+weinig+steun>

--
s|b

Subject: Re: Google is preparing to replace RCS with MLS
From: Jörg Lorenz
Newsgroups: comp.mobile.android
Organization: Camembert Normand au Lait Cru
Date: Mon, 8 Jul 2024 14:49 UTC
References: 1 2 3 4
Path: eternal-september.org!news.eternal-september.org!feeder3.eternal-september.org!weretis.net!feeder8.news.weretis.net!reader5.news.weretis.net!news.solani.org!.POSTED!not-for-mail
From: hugybear@gmx.net (Jörg Lorenz)
Newsgroups: comp.mobile.android
Subject: Re: Google is preparing to replace RCS with MLS
Date: Mon, 8 Jul 2024 16:49:12 +0200
Organization: Camembert Normand au Lait Cru
Message-ID: <v6gu99$bdf3$1@solani.org>
References: <leto4eFasrbU6@mid.individual.net>
<lf075mFraujU1@mid.individual.net> <v6eul3$a8jf$1@solani.org>
<lf2blbF6mslU1@mid.individual.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Mon, 8 Jul 2024 14:49:13 -0000 (UTC)
Injection-Info: solani.org;
logging-data="374243"; mail-complaints-to="abuse@news.solani.org"
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:115.0)
Gecko/20100101 Thunderbird/115.12.1
Cancel-Lock: sha1:OwDrJkR9lzUB8JGWFqH3CazFJqw=
Content-Language: de-CH, en-GB
In-Reply-To: <lf2blbF6mslU1@mid.individual.net>
X-User-ID: eJwFwYEBgDAIA7CXxEIZ5wyw/59gEqBx0hn0UMjUBO829+aDk67Dqe2ulNHxjkf1JyENph8kuhFB
View all headers

Am 08.07.24 um 16:33 schrieb s|b:
> On Sun, 7 Jul 2024 22:43:15 +0200, Jörg Lorenz wrote:
>
>> *Everything* utter nonsense.
>
> Don't just throw a one liner at it, debunk it.
>
> <https://netzpolitik.org/2024/etappensieg-belgien-scheitert-mit-abstimmung-zur-chatkontrolle/>
> <https://www.security.nl/posting/846765/EU-voorzitter+Belgi%C3%AB+schrapt+stemming+chatcontrole+wegens+te+weinig+steun>

France killed it: They made clear that they only support the legislation
as long as it does not brake the E2E-encryption. But exactly this would
happen if the "Chatkontrolle" would be passed. Belgium did not dare to
hold a vote. It would have killed the legislation forever. And the
Germans make/made it clear that they will not and cannot for
constitutional reasons support such a law.

And more important: This vote if passed had only started the legislation
process.

--
"Manus manum lavat."

Pages:123456

rocksolid light 0.9.8
clearnet tor