Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.mobile.android > #109487 > unrolled thread
| Started by | Jeff Layman <Jeff@invalid.invalid> |
|---|---|
| First post | 2023-11-02 20:23 +0000 |
| Last post | 2023-11-03 17:36 +0000 |
| Articles | 20 on this page of 108 — 17 participants |
Back to article view | Back to comp.mobile.android
Backups Jeff Layman <Jeff@invalid.invalid> - 2023-11-02 20:23 +0000
Re: Backups Ed Cryer <ed@somewhere.in.the.uk> - 2023-11-02 21:06 +0000
Re: Backups Wally J <walterjones@invalid.nospam> - 2023-11-02 17:50 -0400
Re: Backups Wally J <walterjones@invalid.nospam> - 2023-11-02 17:29 -0400
Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-03 06:34 +0100
Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-03 06:38 +0100
Re: Backups Jeff Layman <Jeff@invalid.invalid> - 2023-11-03 08:27 +0000
Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-03 10:13 +0100
Re: Backups Jeff Layman <Jeff@invalid.invalid> - 2023-11-04 08:46 +0000
Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-04 10:01 +0100
Re: Backups Jeff Layman <Jeff@invalid.invalid> - 2023-11-04 10:44 +0000
Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-04 11:53 +0100
Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-04 11:54 +0100
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-04 14:43 +0100
Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-04 16:13 +0100
Re: Backups Wally J <walterjones@invalid.nospam> - 2023-11-04 21:30 -0400
Re: Backups Theo <theom+news@chiark.greenend.org.uk> - 2023-11-05 14:24 +0000
Re: Backups Larry Wolff <larrywolff@larrywolff.net> - 2023-11-06 00:44 +0900
Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-05 18:25 +0100
Re: Backups Jeff Layman <Jeff@invalid.invalid> - 2023-11-05 15:57 +0000
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-06 01:53 +0100
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-06 11:25 +0000
Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-06 14:43 +0000
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-06 18:28 +0100
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-06 17:30 +0000
Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-07 15:15 +0000
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-07 21:24 +0100
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-06 18:29 +0100
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-06 17:35 +0000
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-06 18:43 +0100
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-06 19:57 +0000
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-06 21:38 +0100
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-06 21:08 +0000
Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-06 22:14 +0100
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-07 21:26 +0100
Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-07 21:35 +0100
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-07 20:49 +0000
Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-08 14:53 +0000
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-08 16:12 +0100
Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-08 16:33 +0000
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-08 19:54 +0100
Re: Backups Kenan ÇOT <kenancot34@gmail.com> - 2023-11-08 11:18 -0800
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-09 10:17 +0000
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-09 12:02 +0100
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-09 12:45 +0000
Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-09 13:17 +0000
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-09 14:05 +0000
Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-09 15:22 +0000
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-09 17:09 +0000
Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-09 19:04 +0000
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-09 20:44 +0000
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-09 21:49 +0100
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-09 21:35 +0000
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-09 23:21 +0100
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-10 00:06 +0000
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-10 15:08 +0100
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-10 14:44 +0000
Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-10 18:55 +0000
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-10 20:10 +0100
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-10 21:26 +0000
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-10 23:09 +0100
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-10 23:00 +0000
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-11 00:20 +0100
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-11 12:55 +0000
Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-11 15:29 +0000
Re: Backups Jim Jackson <jj@franjam.org.uk> - 2023-11-14 13:04 +0000
Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-14 15:44 +0000
Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-11 15:24 +0000
Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-10 13:51 +0000
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-10 14:40 +0000
Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-10 18:55 +0000
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-10 22:20 +0000
Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-11 14:59 +0000
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-09 20:44 +0100
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-09 21:17 +0000
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-09 22:38 +0100
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-09 23:41 +0000
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-10 15:06 +0100
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-10 14:45 +0000
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-09 15:22 +0100
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-09 17:11 +0000
Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-06 17:19 +0100
Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-06 17:18 +0100
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-06 01:54 +0100
Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-06 17:21 +0100
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-06 18:33 +0100
Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-06 19:06 +0100
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-06 19:13 +0100
Re: Backups Ed Cryer <ed@somewhere.in.the.uk> - 2023-11-06 18:49 +0000
Re: Backups Larry Wolff <larrywolff@larrywolff.net> - 2023-11-25 09:35 -0500
Re: Backups Joerg Lorenz <hugybear@gmx.net> - 2023-11-25 16:51 +0100
Re: Backups Arno Welzel <usenet@arnowelzel.de> - 2023-12-04 20:44 +0100
Re: Backups Wally J <walterjones@invalid.nospam> - 2023-11-04 21:29 -0400
Re: Backups Jeff Layman <Jeff@invalid.invalid> - 2023-11-05 16:03 +0000
Re: Backups AJL <noemail@none.com> - 2023-11-03 09:01 -0700
Re: Backups Theo <theom+news@chiark.greenend.org.uk> - 2023-11-03 13:31 +0000
Re: Backups Adrian <bulleid@ku.gro.lioff> - 2023-11-03 14:25 +0000
Re: Backups Andy Burns <usenet@andyburns.uk> - 2023-11-03 14:38 +0000
Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-03 16:38 +0000
Re: Backups Andy Burns <usenet@andyburns.uk> - 2023-11-03 17:34 +0000
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-04 02:52 +0100
Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-04 11:39 +0000
Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-03 16:43 +0000
Re: Backups Theo <theom+news@chiark.greenend.org.uk> - 2023-11-03 21:42 +0000
Re: Backups Dave Royal<dave@dave123royal.com> - 2023-11-03 22:53 +0000
Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-04 11:05 +0000
Re: Backups Wally J <walterjones@invalid.nospam> - 2023-11-04 14:24 -0400
Re: Backups Andy Burns <usenet@andyburns.uk> - 2023-11-03 17:36 +0000
Page 4 of 6 — ← Prev page 1 2 3 [4] 5 6 Next page →
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Date | 2023-11-10 23:09 +0100 |
| Message-ID | <kr7o1dFiavdU11@mid.individual.net> |
| In reply to | #109965 |
On 2023-11-10 22:26, Java Jive wrote:
> On 10/11/2023 19:10, Carlos E. R. wrote:
>> On 2023-11-10 19:55, Frank Slootweg wrote:
>>> Java Jive <java@evij.com.invalid> wrote:
>>>> On 10/11/2023 14:08, Carlos E. R. wrote:
>>>>>
>>>>> On 2023-11-10 01:06, Java Jive wrote:
>>>>>>
>>>>>> LOL! I'll just write you off as naive, and a bad loser.
>>>>>
>>>>> I didn't lose. You did. There are people reading that they know, they
>>>>> just left the discussion earlier.
>>>>>
>>>>> Bye. EOD.
>>>>
>>>> To clarify, like it or not, your statement that "no big company with a
>>>> modicum of sense would do that. Just collecting data, massively, to
>>>> analyze and target publicity?" has been proven to be false; it's
>>>> exactly
>>>> how Google makes 80% of its revenue.
>>>
>>> You keep harping on that, but your 'argument' is invalid, because
>>> Carlos' remark [1] was in the context of Google's RCS, i.e. E2EE. That
>>> you 'conveniently' snipped [2] the context from your response [3],
>>> doesn't change the context.
>>>
>>> Carlos and I have repeatedly reconfirmed that the context was and is
>>> E2EE.
>>>
>>> *In the context of E2EE*, your babbling about Gmail "snooping" and
>>> Google's revenues from ads, is totally irrelevant and just shows your
>>> agenda.
>>>
>>> Give it a rest! You're not fooling anybody, except yourself.
>>>
>>> I hope you enjoy the egg and pie.
>>>
>>> [1] Message-ID: <kqqrotF8ghsU4@mid.individual.net>
>>>
>>> [2] Snipped part *directly* above Carlos' text:
>>>
>>> <JL>
>>> I assume that if Google gets their success with RCS that would mean more
>>> data available for analysis by them, and more ads for us.
>>> </JL>
>>>
>>> See the "RCS" bit you pretend/wish wasn't there!?
>>>
>>> [3] Message-ID: <uiaiff$esio$1@dont-email.me>
>>
>> Agree to all.
>
> Your original quote in its *entirety* read ...
>
> On 06/11/2023 00:53, Carlos E. R. wrote:
> >
> > No, no big company with a modicum of sense would do that. Just
> > collecting data, massively, to analyze and target publicity? That
> > would get known, many people need to be in the know to make use of
> > that lot of data. Too risky. Thus, not likely.
> >
> > Now, a backdoor so that authorities can capture a few conversations
> > with a warrant? Maybe. Or so that a spy agency captures data from a
> > limited number of targets? Perhaps.
> >
> > By the way, this is normally done by placing a trojan at one of the
> > targets.
>
> ... and thus contained no such reservation that you are *only*
> discussing E2EE.
Wrong. You have omitted parts of the context:
+++---------------------------
> On 2023-11-05 16:57, Jeff Layman wrote:
>> On 05/11/2023 14:24, Theo wrote:
>>> Jeff Layman <Jeff@invalid.invalid> wrote:
>>>> I do wonder about End-to-End Encryption when the encrypted message goes
>>>> through Google. They could simply be the man-in-the-middle who is able
>>>> to read the message because they set up the encryption. It might also
>>>> answer another question raised as to "what's in RCS for Google?". Well,
>>>> if they are able to read those encrypted messages it's another source of
>>>> data for them to sell that others can't read and make use of.
>>>>
>>>> Or does that sound too much like another conspiracy theory? 😉
>>>
>>> Yes. E2EE means that Google in the middle can't intercept. That's what
>>> E2EE means - if they can, it's not E2EE.
...
>>> Google are doing this big US ad campaign to 'convince' Apple to add RCS
>>> support to iOS - they know Apple won't, but it just gets Google publicity
>>> for RCS.
>>
>> I assume that if Google gets their success with RCS that would mean more data available for analysis by them, and more ads for us.
>
> No, no big company with a modicum of sense would do that. Just collecting data, massively, to analyze and target publicity? That would get known, many people need to be in the know to make use of that lot of data. Too risky. Thus, not likely.
...
---------------------------++-
The context I quoted in my post included E2EE and RCS, with RCS being in
the previous paragraph directly above mine.
And if it was not clear we were talking of those, we repeatedly insisted
we were talking of E2EE and RCS several times later (an acronym, E2EE,
that is new to me, I normally prefer long words, so it may not occur in
my writings about it. I say this in case you grep for E2EE only).
Every post is part of a thread, a conversation, and you have to look at
more posts than one for context. And in my post I left enough material
of the ongoing conversation, so that everybody could know what we were
talking about.
And what I wrote in that post doesn't make sense unless read in the
context of RCS and E2EE.
You are intentionally perverting what we said.
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
| From | Java Jive <java@evij.com.invalid> |
|---|---|
| Date | 2023-11-10 23:00 +0000 |
| Message-ID | <uimclh$32a7c$1@dont-email.me> |
| In reply to | #109967 |
On 10/11/2023 22:09, Carlos E. R. wrote: > > On 2023-11-10 22:26, Java Jive wrote: >> >> Your original quote in its *entirety* read ... >> >> On 06/11/2023 00:53, Carlos E. R. wrote: >> > >> > No, no big company with a modicum of sense would do that. Just >> > collecting data, massively, to analyze and target publicity? That >> > would get known, many people need to be in the know to make use of >> > that lot of data. Too risky. Thus, not likely. >> > >> > Now, a backdoor so that authorities can capture a few conversations >> > with a warrant? Maybe. Or so that a spy agency captures data from a >> > limited number of targets? Perhaps. >> > >> > By the way, this is normally done by placing a trojan at one of the >> > targets. >> >> ... and thus contained no such reservation that you are *only* >> discussing E2EE. > > Wrong. You have omitted parts of the context: > > +++--------------------------- >> On 2023-11-05 16:57, Jeff Layman wrote: >>> On 05/11/2023 14:24, Theo wrote: >>>> Jeff Layman <Jeff@invalid.invalid> wrote: >>>>> I do wonder about End-to-End Encryption when the encrypted message >>>>> goes >>>>> through Google. They could simply be the man-in-the-middle who is able >>>>> to read the message because they set up the encryption. It might also >>>>> answer another question raised as to "what's in RCS for Google?". >>>>> Well, >>>>> if they are able to read those encrypted messages it's another >>>>> source of >>>>> data for them to sell that others can't read and make use of. >>>>> >>>>> Or does that sound too much like another conspiracy theory? 😉 >>>> >>>> Yes. E2EE means that Google in the middle can't intercept. That's >>>> what >>>> E2EE means - if they can, it's not E2EE. > > .... > >>>> Google are doing this big US ad campaign to 'convince' Apple to add RCS >>>> support to iOS - they know Apple won't, but it just gets Google >>>> publicity >>>> for RCS. >>> >>> I assume that if Google gets their success with RCS that would mean >>> more data available for analysis by them, and more ads for us. >> >> No, no big company with a modicum of sense would do that. Just >> collecting data, massively, to analyze and target publicity? That >> would get known, many people need to be in the know to make use of >> that lot of data. Too risky. Thus, not likely. > > .... > > ---------------------------++- > > The context I quoted in my post included E2EE and RCS, with RCS being in > the previous paragraph directly above mine. > > And if it was not clear we were talking of those, we repeatedly insisted > we were talking of E2EE and RCS several times later (an acronym, E2EE, > that is new to me, I normally prefer long words, so it may not occur in > my writings about it. I say this in case you grep for E2EE only). I have apologised for allowing myself to follow the moving goalposts, I note that you have not apologised for making the original misleading claim. > Every post is part of a thread, a conversation, and you have to look at > more posts than one for context. And in my post I left enough material > of the ongoing conversation, so that everybody could know what we were > talking about. > > And what I wrote in that post doesn't make sense unless read in the > context of RCS and E2EE. Which is the problem, you stated *explicitly* an absolutist but false claim in "no big company with a modicum of sense would do that. Just collecting data, massively, to analyze and target publicity?" but did not state equally *explicitly* the context that you wished to apply to it. > You are intentionally perverting what we said. No, I'm going by how I - and seemingly most or all others that have replied in this subthread, even initially Frank Slootweg judging by his first reply to me - initially read your original claim. -- Fake news kills! I may be contacted via the contact address given on my website: www.macfh.co.uk
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Date | 2023-11-11 00:20 +0100 |
| Message-ID | <kr7s55FiaveU6@mid.individual.net> |
| In reply to | #109970 |
On 2023-11-11 00:00, Java Jive wrote:
> On 10/11/2023 22:09, Carlos E. R. wrote:
>>
>> On 2023-11-10 22:26, Java Jive wrote:
>>>
>>> Your original quote in its *entirety* read ...
>>>
>>> On 06/11/2023 00:53, Carlos E. R. wrote:
>>> >
>>> > No, no big company with a modicum of sense would do that. Just
>>> > collecting data, massively, to analyze and target publicity? That
>>> > would get known, many people need to be in the know to make use of
>>> > that lot of data. Too risky. Thus, not likely.
>>> >
>>> > Now, a backdoor so that authorities can capture a few conversations
>>> > with a warrant? Maybe. Or so that a spy agency captures data from a
>>> > limited number of targets? Perhaps.
>>> >
>>> > By the way, this is normally done by placing a trojan at one of the
>>> > targets.
>>>
>>> ... and thus contained no such reservation that you are *only*
>>> discussing E2EE.
>>
>> Wrong. You have omitted parts of the context:
>>
>> +++---------------------------
>>> On 2023-11-05 16:57, Jeff Layman wrote:
>>>> On 05/11/2023 14:24, Theo wrote:
>>>>> Jeff Layman <Jeff@invalid.invalid> wrote:
>>>>>> I do wonder about End-to-End Encryption when the encrypted message
>>>>>> goes
>>>>>> through Google. They could simply be the man-in-the-middle who is
>>>>>> able
>>>>>> to read the message because they set up the encryption. It might also
>>>>>> answer another question raised as to "what's in RCS for Google?".
>>>>>> Well,
>>>>>> if they are able to read those encrypted messages it's another
>>>>>> source of
>>>>>> data for them to sell that others can't read and make use of.
>>>>>>
>>>>>> Or does that sound too much like another conspiracy theory? 😉
>>>>>
>>>>> Yes. E2EE means that Google in the middle can't intercept. That's
>>>>> what
>>>>> E2EE means - if they can, it's not E2EE.
>>
>> ....
>>
>>>>> Google are doing this big US ad campaign to 'convince' Apple to add
>>>>> RCS
>>>>> support to iOS - they know Apple won't, but it just gets Google
>>>>> publicity
>>>>> for RCS.
>>>>
>>>> I assume that if Google gets their success with RCS that would mean
>>>> more data available for analysis by them, and more ads for us.
>>>
>>> No, no big company with a modicum of sense would do that. Just
>>> collecting data, massively, to analyze and target publicity? That
>>> would get known, many people need to be in the know to make use of
>>> that lot of data. Too risky. Thus, not likely.
>>
>> ....
>>
>> ---------------------------++-
>>
>> The context I quoted in my post included E2EE and RCS, with RCS being
>> in the previous paragraph directly above mine.
>>
>> And if it was not clear we were talking of those, we repeatedly
>> insisted we were talking of E2EE and RCS several times later (an
>> acronym, E2EE, that is new to me, I normally prefer long words, so it
>> may not occur in my writings about it. I say this in case you grep for
>> E2EE only).
>
> I have apologised for allowing myself to follow the moving goalposts, I
> note that you have not apologised for making the original misleading claim.
WRONG. You have to apologize to me for manipulation of quotes and
perverting what I said.
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
| From | Java Jive <java@evij.com.invalid> |
|---|---|
| Date | 2023-11-11 12:55 +0000 |
| Message-ID | <uintkl$3eo3f$1@dont-email.me> |
| In reply to | #109972 |
On 10/11/2023 23:20, Carlos E. R. wrote: > > On 2023-11-11 00:00, Java Jive wrote: >> >> I have apologised for allowing myself to follow the moving goalposts, >> I note that you have not apologised for making the original misleading >> claim. > > WRONG. You have to apologize to me for manipulation of quotes and > perverting what I said. Bollocks to that, I merely quoted facts in reply to the false claim that you yourself wrote. And unlike you hypocrites, when I say EOD, I mean it. Subthread ignored. -- Fake news kills! I may be contacted via the contact address given on my website: www.macfh.co.uk
[toc] | [prev] | [next] | [standalone]
| From | Frank Slootweg <this@ddress.is.invalid> |
|---|---|
| Date | 2023-11-11 15:29 +0000 |
| Message-ID | <uioa59.16is.1@ID-201911.user.individual.net> |
| In reply to | #109988 |
Java Jive <java@evij.com.invalid> wrote: > On 10/11/2023 23:20, Carlos E. R. wrote: > > > > On 2023-11-11 00:00, Java Jive wrote: > >> > >> I have apologised for allowing myself to follow the moving goalposts, > >> I note that you have not apologised for making the original misleading > >> claim. > > > > WRONG. You have to apologize to me for manipulation of quotes and > > perverting what I said. > > Bollocks to that, I merely quoted facts in reply to the false claim that > you yourself wrote. > > And unlike you hypocrites, And that's another apology you owe. > when I say EOD, I mean it. > > Subthread ignored. > > -- > > Fake news kills! <firmly sitting on hands>
[toc] | [prev] | [next] | [standalone]
| From | Jim Jackson <jj@franjam.org.uk> |
|---|---|
| Date | 2023-11-14 13:04 +0000 |
| Message-ID | <slrnul6s33.24h.jj@iridium.wf32df> |
| In reply to | #109972 |
On 2023-11-10, Carlos E. R. <robin_listas@es.invalid> wrote: > On 2023-11-11 00:00, Java Jive wrote: I thought I'd seen an EOD ? Must be dreaming. Ok back to the tedium
[toc] | [prev] | [next] | [standalone]
| From | Frank Slootweg <this@ddress.is.invalid> |
|---|---|
| Date | 2023-11-14 15:44 +0000 |
| Message-ID | <uj0857.105s.1@ID-201911.user.individual.net> |
| In reply to | #110181 |
Jim Jackson <jj@franjam.org.uk> wrote: > On 2023-11-10, Carlos E. R. <robin_listas@es.invalid> wrote: > > On 2023-11-11 00:00, Java Jive wrote: > > I thought I'd seen an EOD ? Must be dreaming. Ok back to the tedium Yes, you're dreaming. The EOD was mine, not Carlos' and it was a conditional one, which gave another dispute all by itself. But things have died down now, so happy dreams!
[toc] | [prev] | [next] | [standalone]
| From | Frank Slootweg <this@ddress.is.invalid> |
|---|---|
| Date | 2023-11-11 15:24 +0000 |
| Message-ID | <uio9rq.16is.1@ID-201911.user.individual.net> |
| In reply to | #109970 |
Java Jive <java@evij.com.invalid> wrote: > On 10/11/2023 22:09, Carlos E. R. wrote: > > > > On 2023-11-10 22:26, Java Jive wrote: > >> > >> Your original quote in its *entirety* read ... > >> > >> On 06/11/2023 00:53, Carlos E. R. wrote: [...] > > Every post is part of a thread, a conversation, and you have to look at > > more posts than one for context. And in my post I left enough material > > of the ongoing conversation, so that everybody could know what we were > > talking about. > > > > And what I wrote in that post doesn't make sense unless read in the > > context of RCS and E2EE. > > Which is the problem, you stated *explicitly* an absolutist but false > claim in "no big company with a modicum of sense would do that. Just > collecting data, massively, to analyze and target publicity?" but did > not state equally *explicitly* the context that you wished to apply to it. Nonsense! He doesn't have to say the current context does still apply. For the umpteenth time: *You* have to say if you want to change/ignore/ <whatever> the context. That's how it works in real life and that's how it works on Usenet. If you think differently, *you* will have to get support for your outlandish stance. > > You are intentionally perverting what we said. > > No, I'm going by how I - and seemingly most or all others that have > replied in this subthread, even initially Frank Slootweg judging by his > first reply to me - initially read your original claim. Nope. (Of course,) I also assumed the current RCS E2EE context. As to "and seemingly most or all others": I think you mentioned Ed Cryer and Joerg Lorenz. IMO Ed's response was uncalled for and very few - if any - people take Joerg seriously, especially not on RCS (which he hates with a passion and on which he has been repeatedly proven wrong). Remain Theo and Jeff who were the lead-ins to this whole mess. Did I miss anybody? So it's quite the opposite, you were the odd one out.
[toc] | [prev] | [next] | [standalone]
| From | Frank Slootweg <this@ddress.is.invalid> |
|---|---|
| Date | 2023-11-10 13:51 +0000 |
| Message-ID | <uilg0h.19s4.1@ID-201911.user.individual.net> |
| In reply to | #109881 |
Java Jive <java@evij.com.invalid> wrote: > On 09/11/2023 19:04, Frank Slootweg wrote: > > Java Jive <java@evij.com.invalid> wrote: > >> On 09/11/2023 15:22, Frank Slootweg wrote: > >>> Java Jive <java@evij.com.invalid> wrote: > >>>> On 09/11/2023 13:17, Frank Slootweg wrote: > >>>>> Java Jive <java@evij.com.invalid> wrote: > >>>>>> On 09/11/2023 11:02, Carlos E. R. wrote: > >>>>>>> On 2023-11-09 11:17, Java Jive wrote: > >>>>>>>> On 08/11/2023 14:53, Frank Slootweg wrote: > >>>>>>>>> > >>>>>>>>> Java Jive <java@evij.com.invalid> wrote: > >>>>>>>>>> > >>>>>>>>>> On 07/11/2023 20:26, Carlos E. R. wrote: [Gmail scanning hoopla deleted. There's just no point.] > >>>>>>> Yes, we did. > >>>>>> > >>>>>> No, you didn't ... > >>>>>> > >>>>>>> Google can not read the messages, that's the whole point of E2EE. > >>>>>> > >>>>>> ... because Google is running the OS that is decrypting it for you. > >>>>> > >>>>> Nope, the OS is not doing the decrypting. > >>>>> > >>>>> But your -invalid - point seems to be that someone - i.e. also Google > >>>>> - could have a backdoor somewhere. > >>>>> > >>>>> Yes, that's theoretically possible, but in practice it's extremely > >>>>> unlikely, because that would get them in big, big trouble. > >>>> > >>>> No back-doors are needed when the front is wide-open. The results of > >>>> decryption are fed back through the OS to be given to the user. > >>> > >>> Nope. That's not how E2EE works. The OS does not see the decrypted > >>> data (unless there's a backdoor). > >> > >> So, for example, the encryption has its own routines to display a > >> message on the screen of the device? No, of course not, OS routines do it. > > > > Sigh! If you're implying that Google is intercepting user data which > > is written to the screen (or coming from the keyboard), then that's a > > backdoor, which 1) we've said would get them in big, big trouble and 2) > > I had specifically excluded. > > Sigh! You're trying to play with words again - most people would > think of a backdoor as means of seeing into the encryption system > itself. Are you really trying to claim that a screen-reader for a blind > person is a back-door? Nice try, but no cigar. Nope, it's anything *but* playing with words. The example you describe is *Google* deceitfully intercepting the user's (screen/keyboard) data without their knowledge or approval. *That* *is* a backdoor. The screen-reader for a blind person example is intentional behaviour with the user's approval. Two totally different and incomparable situations. [...] > > BTW, I assume you don't actually own or use any Android devices, > > Google services, etc.. > > On the contrary I do, I just accept that it's relatively insecure - > apart from anything else, it might be lost or stolen - and thus don't > use it for purposes where security is important. A case of sarchasm. [...] > > EOD. > > So you keep saying, but then keep replying, so rightly no-one takes any > notice of your attempt to make it look as though you've won an argument > when you haven't. Sigh! I keep replying because you keep coming up with more and even more weird stuff and I don't want to give anyone the impression that you might actually have a valid argument. And no, I haven't 'won' an argument, because there *is* no argument, just your opinion(s). But if you like this better: AFAIC, EOD.
[toc] | [prev] | [next] | [standalone]
| From | Java Jive <java@evij.com.invalid> |
|---|---|
| Date | 2023-11-10 14:40 +0000 |
| Message-ID | <uilfc5$2sc0r$1@dont-email.me> |
| In reply to | #109915 |
On 10/11/2023 13:51, Frank Slootweg wrote: > > Java Jive <java@evij.com.invalid> wrote: >> >> On 09/11/2023 19:04, Frank Slootweg wrote: >>> >>> Java Jive <java@evij.com.invalid> wrote: >>>> >>>> So, for example, the encryption has its own routines to display a >>>> message on the screen of the device? No, of course not, OS routines do it. >>> >>> Sigh! If you're implying that Google is intercepting user data which >>> is written to the screen (or coming from the keyboard), then that's a >>> backdoor, which 1) we've said would get them in big, big trouble and 2) >>> I had specifically excluded. >> >> Sigh! You're trying to play with words again - most people would >> think of a backdoor as means of seeing into the encryption system >> itself. Are you really trying to claim that a screen-reader for a blind >> person is a back-door? > > Nice try, but no cigar. > > Nope, it's anything *but* playing with words. The example you describe > is *Google* deceitfully intercepting the user's (screen/keyboard) data > without their knowledge or approval. *That* *is* a backdoor. This seems to support both of us ... https://en.wikipedia.org/wiki/Backdoor_(computing) ... for while the description in the first paragraph supports your meaning, all the subsequent examples support mine, so we'll just have to agree to differ on that. > The screen-reader for a blind person example is intentional behaviour > with the user's approval. > > Two totally different and incomparable situations. My point was and is that the software needed for such an attack is likely already there on the device as part of the OS, no-one has to install it, only to use it, and as such is not what in my experience is commonly thought of as a backdoor. >>> BTW, I assume you don't actually own or use any Android devices, >>> Google services, etc.. >> >> On the contrary I do, I just accept that it's relatively insecure - >> apart from anything else, it might be lost or stolen - and thus don't >> use it for purposes where security is important. > > A case of sarchasm. A case of of misspelling of allegedly the lowest form of wit. >> So you keep saying, but then keep replying, so rightly no-one takes any >> notice of your attempt to make it look as though you've won an argument >> when you haven't. > > Sigh! I keep replying because you keep coming up with more and even > more weird stuff and I don't want to give anyone the impression that you > might actually have a valid argument. > > And no, I haven't 'won' an argument, because there *is* no argument, > just your opinion(s). > > But if you like this better: > > AFAIC, EOD. Yet you replied again. -- Fake news kills! I may be contacted via the contact address given on my website: www.macfh.co.uk
[toc] | [prev] | [next] | [standalone]
| From | Frank Slootweg <this@ddress.is.invalid> |
|---|---|
| Date | 2023-11-10 18:55 +0000 |
| Message-ID | <uim1r8.imo.1@ID-201911.user.individual.net> |
| In reply to | #109921 |
Java Jive <java@evij.com.invalid> wrote: > On 10/11/2023 13:51, Frank Slootweg wrote: [...] > My point was and is that the software needed for such an attack is > likely already there on the device as part of the OS, no-one has to > install it, only to use it, and as such is not what in my experience is > commonly thought of as a backdoor. That's exactly what a backdoor is, something which is already there. From your Wikipedia reference: "A backdoor may take the form of a hidden part of a program". In this case, the alledged "program" is some part of the OS. The disagreement is that you say the backdoor is "likely", while Carlos and I say it's bloody unlikely, because of the exterme repercussions it would have for Google. > >>> BTW, I assume you don't actually own or use any Android devices, > >>> Google services, etc.. > >> > >> On the contrary I do, I just accept that it's relatively insecure - > >> apart from anything else, it might be lost or stolen - and thus don't > >> use it for purposes where security is important. > > > > A case of sarchasm. > > A case of of misspelling of allegedly the lowest form of wit. It's not a misspelling. Look it up. (Hint: 'define: <term>' in Google. Might as well give them a few dollars worth of your data.) As to "the lowest form": Can't do the time, ... > >> So you keep saying, but then keep replying, so rightly no-one takes any > >> notice of your attempt to make it look as though you've won an argument > >> when you haven't. > > > > Sigh! I keep replying because you keep coming up with more and even > > more weird stuff and I don't want to give anyone the impression that you > > might actually have a valid argument. > > > > And no, I haven't 'won' an argument, because there *is* no argument, > > just your opinion(s). > > > > But if you like this better: > > > > AFAIC, EOD. > > Yet you replied again. Exactly *which* part(s) of "because..." and "AFAIC" didn't you understand!?
[toc] | [prev] | [next] | [standalone]
| From | Java Jive <java@evij.com.invalid> |
|---|---|
| Date | 2023-11-10 22:20 +0000 |
| Message-ID | <uimabm$31t5k$1@dont-email.me> |
| In reply to | #109950 |
On 10/11/2023 18:55, Frank Slootweg wrote: > > Java Jive <java@evij.com.invalid> wrote: >> >> On 10/11/2023 13:51, Frank Slootweg wrote: > [...] > >> My point was and is that the software needed for such an attack is >> likely already there on the device as part of the OS, no-one has to >> install it, only to use it, and as such is not what in my experience is >> commonly thought of as a backdoor. > > That's exactly what a backdoor is, something which is already there. > > From your Wikipedia reference: "A backdoor may take the form of a > hidden part of a program". In this case, the alledged "program" is some > part of the OS. Yes, but, as I pointed out, all the examples they gave tended to support my stricter meaning of the phrase rather than yours, so we'll have to agree to differ on mere nomenclature. > The disagreement is that you say the backdoor is "likely", while > Carlos and I say it's bloody unlikely, because of the exterme > repercussions it would have for Google. I have never used the word "likely" until this very sentence, only you and Carlos have, but I did say ... On 09/11/2023 10:17, Java Jive wrote: > > No-one has answered my basic point that, if Google run the OS, and > Carlos can read the message, so can Google, and, given Google's track > record, most probably they will ... which, having now done the research outlined in a recent reply that Carlos apparently didn't bother to read, I would now accept is probably overstated, because they do seem to have made some attempts to clean up their act. Nevertheless, as that research indicated, their record for snooping is not good, is still pretty much the worst known of all such companies, and there is still plenty of legal wiggle-room for them to regress, so I still think, even accepting his originally unstated context of E2EE, that his faith is misplaced. >>>>> BTW, I assume you don't actually own or use any Android devices, >>>>> Google services, etc.. >>>> >>>> On the contrary I do, I just accept that it's relatively insecure - >>>> apart from anything else, it might be lost or stolen - and thus don't >>>> use it for purposes where security is important. >>> >>> A case of sarchasm. >> >> A case of of misspelling of allegedly the lowest form of wit. > > It's not a misspelling. Look it up. (Hint: 'define: <term>' in Google. > Might as well give them a few dollars worth of your data.) So to be sure I just did exactly as ordered, and found, as of course I have known for 65 or more years, there is no 'h' in 'sarcasm'. Only when I clicked on "Search instead for define: sarchasm" did I find the obscure coined word, which suggests that the term is of sufficient obscurity that its use might have been better avoided, particularly as any joke that has to be explained falls flat. By the way, something else I didn't need to know, it's also the name of a punk band, thus obscuring his intended meaning still further. >> Yet you replied again. > > Exactly *which* part(s) of "because..." and "AFAIC" didn't you > understand!? The fact that you both keep saying 'EOD' but then keep replying. -- Fake news kills! I may be contacted via the contact address given on my website: www.macfh.co.uk
[toc] | [prev] | [next] | [standalone]
| From | Frank Slootweg <this@ddress.is.invalid> |
|---|---|
| Date | 2023-11-11 14:59 +0000 |
| Message-ID | <uio8cq.16is.1@ID-201911.user.individual.net> |
| In reply to | #109969 |
Java Jive <java@evij.com.invalid> wrote: > On 10/11/2023 18:55, Frank Slootweg wrote: [...] > On 09/11/2023 10:17, Java Jive wrote: > > > > No-one has answered my basic point that, if Google run the OS, and > > Carlos can read the message, so can Google, and, given Google's track > > record, most probably they will > > ... which, having now done the research outlined in a recent reply that > Carlos apparently didn't bother to read, I would now accept is probably > overstated, because they do seem to have made some attempts to clean up > their act. Nevertheless, as that research indicated, their record for > snooping is not good, is still pretty much the worst known of all such > companies, and there is still plenty of legal wiggle-room for them to > regress, so I still think, even accepting his originally unstated > context of E2EE, that his faith is misplaced. Please do not falsify history! The context of E2EE was *not* "unstated"! The E2EE context was (quoted) in Carlos' response, full stop. As I said before, that *you* *snipped* (why?) that context, doesn't mean it no longer applies. If *you* want to change/ignore/<whatever> the context, *you* have to *say so*. You didn't, so the context did and does still apply. No wriggling about it. End of story. Anyway, for *your* 'argument' the context of E2EE is irrelevant, because you are talking about Google "snooping" the *decrypted* data, so it doesn't matter if encryption was used or not. N.B. This is 'reasoning' from *your* perspective, for everybody else, the context was and is E2EE. [...] > >> Yet you replied again. > > > > Exactly *which* part(s) of "because..." and "AFAIC" didn't you > > understand!? > > The fact that you both keep saying 'EOD' but then keep replying. I think it's rather clear: As far as *I*'m concerned, it's end of discussion. But that does not mean I can't/won't respond if *you* continue the discussion. Anyway, there has been some - albeit rather little - progress. On your main claim, you have backed down a bit "I would now accept is probably overstated, ...". OTOH, it's rather sad - to put it mildly - that you're still trying to blame us - and mainly Carlos - for *you* (supposedly) changing the context without saying so.
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Date | 2023-11-09 20:44 +0100 |
| Message-ID | <kr4r5hFsdr5U10@mid.individual.net> |
| In reply to | #109861 |
On 2023-11-09 18:09, Java Jive wrote:
> On 09/11/2023 15:22, Frank Slootweg wrote:
>> Java Jive <java@evij.com.invalid> wrote:
>>> On 09/11/2023 13:17, Frank Slootweg wrote:
>>>> Java Jive <java@evij.com.invalid> wrote:
>>>>> On 09/11/2023 11:02, Carlos E. R. wrote:
>>>>>> On 2023-11-09 11:17, Java Jive wrote:
>>>>>>> On 08/11/2023 14:53, Frank Slootweg wrote:
>>>>>>>>
>>>>>>>> Java Jive <java@evij.com.invalid> wrote:
>>>>>>>>>
>>>>>>>>> On 07/11/2023 20:26, Carlos E. R. wrote:
>>>>>>>>>>
>>>>>>>>>> Oh, I did reply. You are not ilustrate enough to understand.
>>>> [...]
>>>>>>>> Anyway, before criticizing others, first learn the
>>>>>>>> difference between
>>>>>>>> end-to-end-encryption and no encryption. That Joerg is siding
>>>>>>>> with you,
>>>>>>>> should be a red flag, a *big* one!
>>>>>>>
>>>>>>> No-one has answered my basic point that, if Google run the OS, and
>>>>>>> Carlos can read the message, so can Google,
>>>>
>>>> No they can't. See below.
>>>>
>>>>>>> and, given Google's
>>>>>>> track
>>>>>>> record, most probably they will.
>>>>
>>>> You're still misunderstanding/misrepresenting "Google's track
>>>> record".
>>>> Footstamping doesn't make a credible argument.
>>>
>>> Track record is all anyone has to judge a company. I can only suggest
>>> that you read Shoshana Zuboff's book "The Age Of Surveillance
>>> Capitalism" which goes into detail on their track record.
>>
>> Irrelevant. You misrepresent what Google is doing with Gmail and you
>> misunderstand how E2EE works / does not work.
>
> The book is totally relevant, long sections of it details the evidence
> of Google's snooping.
None on E2EE streams.
>
>>>>>> Yes, we did.
>>>>>
>>>>> No, you didn't ...
>>>>>
>>>>>> Google can not read the messages, that's the whole point of E2EE.
>>>>>
>>>>> ... because Google is running the OS that is decrypting it for you.
>>>>
>>>> Nope, the OS is not doing the decrypting.
>>>> But your -invalid - point seems to be that someone - i.e. also
>>>> Google
>>>> - could have a backdoor somewhere.
>>>>
>>>> Yes, that's theoretically possible, but in practice it's extremely
>>>> unlikely, because that would get them in big, big trouble.
>>>
>>> No back-doors are needed when the front is wide-open. The results of
>>> decryption are fed back through the OS to be given to the user.
>>
>> Nope. That's not how E2EE works. The OS does not see the decrypted
>> data (unless there's a backdoor).
>
> So, for example, the encryption has its own routines to display a
> message on the screen of the device? No, of course not, OS routines do it.
That would be known eventually, and the culprit would get smeared in big
shit and court suits.
It is simply not done.
>
>> Example: WhatsApp and other IM platforms.
>>
>>>> But even if you accept that premise, it also holds for any other
>>>> company which provides end-to-end-encryption, so you haven't any real
>>>> argument whatsoever.
>>>>
>>>> So let's turn this around: What *proof* do *you* have that some
>>>> other
>>>> company can *not* read your end-to-en-encrypted messages?
>>>
>>> This argument is exactly about Google, so why try to omit them from the
>>> argument?
>>
>> I don't omit them, you single them out.
>
> On account of their known record of monetising what should be customers'
> private data.
I'm sure that it is mentioned in their terms and conditions, and that
data is not E2EE.
>
>>> The point of principle is that *any* company, *including*
>>> Google, that provides an OS can read the results of a decryption after
>>> it has taken place within that OS,
>>
>> But that's your false premise, the decryption does *not* "take place
>> within that OS".
>
> Well, that's trying to bend what I'm saying to suit your own argument,
> but doesn't make it any less true. How exactly do you want me to say
> it? The OS controls the memory space within the device; it controls the
> time sharing between applications; in response to user input it launches
> the programs that use the encryption; finally and most importantly, OS
> routines output the decrypted data on the screen or whereever. I think
> it's reasonable to describe that process as I did above.
No, it isn't.
>
>>> so all the general public have to go
>>> on in deciding whether to trust such a company is track-record, and
>>> Google's does not encourage such trust.
>>
>> Well, on *this* (note emphasis) aspect (RCS E2EE), I trust Google more
>> than some Usenet poster
>
> Fine, but, from the sound of it, you would still be very well advised to
> read Shoshana Zuboff's book to understand what is really going on with
> Google and other like companies.
>
>> who 'compares' totally different subject
>> matters.
>
> Eh? Let me remind how this whole subthread began, which was as follows:
>
> On 05/11/2023 15:57, Jeff Layman wrote:
> >
> > I assume that if Google gets their success with RCS that would mean
> > more data available for analysis by them, and more ads for us.
>
> [Note: I've already pointed out that he should have said "more targetted
> ads for us."]
>
> To which Carlos replied:
>
> On 06/11/2023 00:53, Carlos E. R. wrote:
> >
> > No, no big company with a modicum of sense would do that. Just
> > collecting data, massively, to analyze and target publicity? That
> > would get known, many people need to be in the know to make use of
> > that lot of data. Too risky. Thus, not likely.
>
> But Google are already known to do just that, viz: "Just collecting
> data, massively, to analyze and target publicity", so I replied:
No, they are not known to do just that with E2EE streams.
>
> On 06/11/2023 11:25, Java Jive wrote:
> >
> > Except Google are already known to be doing this - by their own
> > admission they already scan all emails on gmail, etc. I don't
> > knowingly use cloud services, and therefore haven't read any of the
> > T&C of any cloud service, but I wouldn't be at all surprised to find
> > somewhere in there some phrase such as:
> >
> > "I agree that <Google|whoever> scans my data for malware and the
> > purpose of improving their services to me."
>
> So ISTM that I've been entirely consistent in what I've said.
Consistently paranoid without justification.
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
| From | Java Jive <java@evij.com.invalid> |
|---|---|
| Date | 2023-11-09 21:17 +0000 |
| Message-ID | <uiji9a$2d2mp$1@dont-email.me> |
| In reply to | #109873 |
On 09/11/2023 19:44, Carlos E. R. wrote: > On 2023-11-09 18:09, Java Jive wrote: >> On 09/11/2023 15:22, Frank Slootweg wrote: >>> Java Jive <java@evij.com.invalid> wrote: >>>> On 09/11/2023 13:17, Frank Slootweg wrote: >>>>> Java Jive <java@evij.com.invalid> wrote: >>>>>> On 09/11/2023 11:02, Carlos E. R. wrote: >>>>>>> On 2023-11-09 11:17, Java Jive wrote: >>>>>>>> On 08/11/2023 14:53, Frank Slootweg wrote: >>>>>>>>> >>>>>>>>> Java Jive <java@evij.com.invalid> wrote: >>>>>>>>>> >>>>>>>>>> On 07/11/2023 20:26, Carlos E. R. wrote: >>>>>>>>>>> >>>>>>>>>>> Oh, I did reply. You are not ilustrate enough to understand. >>>>> [...] >>>>>>>>> Anyway, before criticizing others, first learn the >>>>>>>>> difference between >>>>>>>>> end-to-end-encryption and no encryption. That Joerg is siding >>>>>>>>> with you, >>>>>>>>> should be a red flag, a *big* one! >>>>>>>> >>>>>>>> No-one has answered my basic point that, if Google run the OS, and >>>>>>>> Carlos can read the message, so can Google, >>>>> >>>>> No they can't. See below. >>>>> >>>>>>>> and, given Google's >>>>>>>> track >>>>>>>> record, most probably they will. >>>>> >>>>> You're still misunderstanding/misrepresenting "Google's track >>>>> record". >>>>> Footstamping doesn't make a credible argument. >>>> >>>> Track record is all anyone has to judge a company. I can only suggest >>>> that you read Shoshana Zuboff's book "The Age Of Surveillance >>>> Capitalism" which goes into detail on their track record. >>> >>> Irrelevant. You misrepresent what Google is doing with Gmail and you >>> misunderstand how E2EE works / does not work. >> >> The book is totally relevant, long sections of it details the evidence >> of Google's snooping. > > None on E2EE streams. > >> >>>>>>> Yes, we did. >>>>>> >>>>>> No, you didn't ... >>>>>> >>>>>>> Google can not read the messages, that's the whole point of E2EE. >>>>>> >>>>>> ... because Google is running the OS that is decrypting it for you. >>>>> >>>>> Nope, the OS is not doing the decrypting. >>>>> But your -invalid - point seems to be that someone - i.e. also >>>>> Google >>>>> - could have a backdoor somewhere. >>>>> >>>>> Yes, that's theoretically possible, but in practice it's extremely >>>>> unlikely, because that would get them in big, big trouble. >>>> >>>> No back-doors are needed when the front is wide-open. The results of >>>> decryption are fed back through the OS to be given to the user. >>> >>> Nope. That's not how E2EE works. The OS does not see the decrypted >>> data (unless there's a backdoor). >> >> So, for example, the encryption has its own routines to display a >> message on the screen of the device? No, of course not, OS routines >> do it. > > That would be known eventually, and the culprit would get smeared in big > shit and court suits. > > It is simply not done. > >> >>> Example: WhatsApp and other IM platforms. >>> >>>>> But even if you accept that premise, it also holds for any other >>>>> company which provides end-to-end-encryption, so you haven't any real >>>>> argument whatsoever. >>>>> >>>>> So let's turn this around: What *proof* do *you* have that some >>>>> other >>>>> company can *not* read your end-to-en-encrypted messages? >>>> >>>> This argument is exactly about Google, so why try to omit them from the >>>> argument? >>> >>> I don't omit them, you single them out. >> >> On account of their known record of monetising what should be >> customers' private data. > > I'm sure that it is mentioned in their terms and conditions, and that > data is not E2EE. I think you're probably right that it's somewhere in their T&C, but that's partly the point, few people actually bother to read them, so it's an 'uncontract' that gives them legal coverage to snoop on people with many or most of their customers probably being completely unaware that it is happening. >>>> The point of principle is that *any* company, *including* >>>> Google, that provides an OS can read the results of a decryption after >>>> it has taken place within that OS, >>> >>> But that's your false premise, the decryption does *not* "take place >>> within that OS". >> >> Well, that's trying to bend what I'm saying to suit your own argument, >> but doesn't make it any less true. How exactly do you want me to say >> it? The OS controls the memory space within the device; it controls >> the time sharing between applications; in response to user input it >> launches the programs that use the encryption; finally and most >> importantly, OS routines output the decrypted data on the screen or >> whereever. I think it's reasonable to describe that process as I did >> above. > > No, it isn't. The words used don't alter the principle of what I'm saying, which is that E2EE only works between the two endpoints, it's what happens outside of that that is the potential problem. >>>> so all the general public have to go >>>> on in deciding whether to trust such a company is track-record, and >>>> Google's does not encourage such trust. >>> >>> Well, on *this* (note emphasis) aspect (RCS E2EE), I trust Google >>> more >>> than some Usenet poster >> >> Fine, but, from the sound of it, you would still be very well advised >> to read Shoshana Zuboff's book to understand what is really going on >> with Google and other like companies. >> >>> who 'compares' totally different subject >>> matters. >> >> Eh? Let me remind how this whole subthread began, which was as follows: >> >> On 05/11/2023 15:57, Jeff Layman wrote: >> > >> > I assume that if Google gets their success with RCS that would mean >> > more data available for analysis by them, and more ads for us. >> >> [Note: I've already pointed out that he should have said "more >> targetted ads for us."] >> >> To which Carlos replied: >> >> On 06/11/2023 00:53, Carlos E. R. wrote: >> > >> > No, no big company with a modicum of sense would do that. Just >> > collecting data, massively, to analyze and target publicity? That >> > would get known, many people need to be in the know to make use of >> > that lot of data. Too risky. Thus, not likely. >> >> But Google are already known to do just that, viz: "Just collecting >> data, massively, to analyze and target publicity", so I replied: > > No, they are not known to do just that with E2EE streams. Not *known* to be happening with E2EE streams doesn't mean that in fact it isn't happening, because, if it was, presumably the intention would be to ensure that it wasn't widely known; I have never tried to claim that it was happening or was not, merely I'm pointing out that in principle it *could* happen, and that your faith in Google or any similar company is misplaced, and, even worse, that the reason you gave for your faith is actually false, as I have shown below ... >> On 06/11/2023 11:25, Java Jive wrote: >> > >> > Except Google are already known to be doing this - by their own >> > admission they already scan all emails on gmail, etc. I don't >> > knowingly use cloud services, and therefore haven't read any of the >> > T&C of any cloud service, but I wouldn't be at all surprised to find >> > somewhere in there some phrase such as: >> > >> > "I agree that <Google|whoever> scans my data for malware and the >> > purpose of improving their services to me." >> >> So ISTM that I've been entirely consistent in what I've said. > > Consistently paranoid without justification. I'm not paranoid at all, just pointing that you are mistaken in your assertion that "No, no big company with a modicum of sense would do that. Just collecting data, massively, to analyze and target publicity?" because that is *exactly* how Google make 80% of their revenue: https://www.statista.com/statistics/266249/advertising-revenue-of-google/ -- Fake news kills! I may be contacted via the contact address given on my website: www.macfh.co.uk
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Date | 2023-11-09 22:38 +0100 |
| Message-ID | <kr51r1F5kmlU3@mid.individual.net> |
| In reply to | #109883 |
On 2023-11-09 22:17, Java Jive wrote:
> On 09/11/2023 19:44, Carlos E. R. wrote:
>> On 2023-11-09 18:09, Java Jive wrote:
>>> On 09/11/2023 15:22, Frank Slootweg wrote:
>>>> Java Jive <java@evij.com.invalid> wrote:
>>>>> On 09/11/2023 13:17, Frank Slootweg wrote:
>>>>>> Java Jive <java@evij.com.invalid> wrote:
>>>>>>> On 09/11/2023 11:02, Carlos E. R. wrote:
>>>>>>>> On 2023-11-09 11:17, Java Jive wrote:
>>>>>>>>> On 08/11/2023 14:53, Frank Slootweg wrote:
>>>>>>>>>>
>>>>>>>>>> Java Jive <java@evij.com.invalid> wrote:
>>>>>>>>>>>
>>>>>>>>>>> On 07/11/2023 20:26, Carlos E. R. wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Oh, I did reply. You are not ilustrate enough to understand.
>>>>>> [...]
>>>>>>>>>> Anyway, before criticizing others, first learn the
>>>>>>>>>> difference between
>>>>>>>>>> end-to-end-encryption and no encryption. That Joerg is siding
>>>>>>>>>> with you,
>>>>>>>>>> should be a red flag, a *big* one!
>>>>>>>>>
>>>>>>>>> No-one has answered my basic point that, if Google run the OS, and
>>>>>>>>> Carlos can read the message, so can Google,
>>>>>>
>>>>>> No they can't. See below.
>>>>>>
>>>>>>>>> and, given
>>>>>>>>> Google's track
>>>>>>>>> record, most probably they will.
>>>>>>
>>>>>> You're still misunderstanding/misrepresenting "Google's track
>>>>>> record".
>>>>>> Footstamping doesn't make a credible argument.
>>>>>
>>>>> Track record is all anyone has to judge a company. I can only suggest
>>>>> that you read Shoshana Zuboff's book "The Age Of Surveillance
>>>>> Capitalism" which goes into detail on their track record.
>>>>
>>>> Irrelevant. You misrepresent what Google is doing with Gmail and you
>>>> misunderstand how E2EE works / does not work.
>>>
>>> The book is totally relevant, long sections of it details the
>>> evidence of Google's snooping.
>>
>> None on E2EE streams.
>>
>>>
>>>>>>>> Yes, we did.
>>>>>>>
>>>>>>> No, you didn't ...
>>>>>>>
>>>>>>>> Google can not read the messages, that's the whole point of E2EE.
>>>>>>>
>>>>>>> ... because Google is running the OS that is decrypting it for you.
>>>>>>
>>>>>> Nope, the OS is not doing the decrypting.
>>>>>> But your -invalid - point seems to be that someone - i.e. also
>>>>>> Google
>>>>>> - could have a backdoor somewhere.
>>>>>>
>>>>>> Yes, that's theoretically possible, but in practice it's
>>>>>> extremely
>>>>>> unlikely, because that would get them in big, big trouble.
>>>>>
>>>>> No back-doors are needed when the front is wide-open. The results of
>>>>> decryption are fed back through the OS to be given to the user.
>>>>
>>>> Nope. That's not how E2EE works. The OS does not see the decrypted
>>>> data (unless there's a backdoor).
>>>
>>> So, for example, the encryption has its own routines to display a
>>> message on the screen of the device? No, of course not, OS routines
>>> do it.
>>
>> That would be known eventually, and the culprit would get smeared in
>> big shit and court suits.
>>
>> It is simply not done.
>>
>>>
>>>> Example: WhatsApp and other IM platforms.
>>>>
>>>>>> But even if you accept that premise, it also holds for any other
>>>>>> company which provides end-to-end-encryption, so you haven't any real
>>>>>> argument whatsoever.
>>>>>>
>>>>>> So let's turn this around: What *proof* do *you* have that
>>>>>> some other
>>>>>> company can *not* read your end-to-en-encrypted messages?
>>>>>
>>>>> This argument is exactly about Google, so why try to omit them from
>>>>> the
>>>>> argument?
>>>>
>>>> I don't omit them, you single them out.
>>>
>>> On account of their known record of monetising what should be
>>> customers' private data.
>>
>> I'm sure that it is mentioned in their terms and conditions, and that
>> data is not E2EE.
>
> I think you're probably right that it's somewhere in their T&C, but
> that's partly the point, few people actually bother to read them, so
> it's an 'uncontract' that gives them legal coverage to snoop on people
> with many or most of their customers probably being completely unaware
> that it is happening.
>
>>>>> The point of principle is that *any* company, *including*
>>>>> Google, that provides an OS can read the results of a decryption after
>>>>> it has taken place within that OS,
>>>>
>>>> But that's your false premise, the decryption does *not* "take place
>>>> within that OS".
>>>
>>> Well, that's trying to bend what I'm saying to suit your own
>>> argument, but doesn't make it any less true. How exactly do you want
>>> me to say it? The OS controls the memory space within the device; it
>>> controls the time sharing between applications; in response to user
>>> input it launches the programs that use the encryption; finally and
>>> most importantly, OS routines output the decrypted data on the screen
>>> or whereever. I think it's reasonable to describe that process as I
>>> did above.
>>
>> No, it isn't.
>
> The words used don't alter the principle of what I'm saying, which is
> that E2EE only works between the two endpoints, it's what happens
> outside of that that is the potential problem.
>
>>>>> so all the general public have to go
>>>>> on in deciding whether to trust such a company is track-record, and
>>>>> Google's does not encourage such trust.
>>>>
>>>> Well, on *this* (note emphasis) aspect (RCS E2EE), I trust Google
>>>> more
>>>> than some Usenet poster
>>>
>>> Fine, but, from the sound of it, you would still be very well advised
>>> to read Shoshana Zuboff's book to understand what is really going on
>>> with Google and other like companies.
>>>
>>>> who 'compares' totally different subject
>>>> matters.
>>>
>>> Eh? Let me remind how this whole subthread began, which was as follows:
>>>
>>> On 05/11/2023 15:57, Jeff Layman wrote:
>>> >
>>> > I assume that if Google gets their success with RCS that would mean
>>> > more data available for analysis by them, and more ads for us.
>>>
>>> [Note: I've already pointed out that he should have said "more
>>> targetted ads for us."]
>>>
>>> To which Carlos replied:
>>>
>>> On 06/11/2023 00:53, Carlos E. R. wrote:
>>> >
>>> > No, no big company with a modicum of sense would do that. Just
>>> > collecting data, massively, to analyze and target publicity? That
>>> > would get known, many people need to be in the know to make use of
>>> > that lot of data. Too risky. Thus, not likely.
>>>
>>> But Google are already known to do just that, viz: "Just collecting
>>> data, massively, to analyze and target publicity", so I replied:
>>
>> No, they are not known to do just that with E2EE streams.
>
> Not *known* to be happening with E2EE streams doesn't mean that in fact
> it isn't happening, because, if it was, presumably the intention would
> be to ensure that it wasn't widely known; I have never tried to claim
> that it was happening or was not, merely I'm pointing out that in
> principle it *could* happen, and that your faith in Google or any
> similar company is misplaced, and, even worse, that the reason you gave
> for your faith is actually false, as I have shown below ...
NO.
What I say is that it can not massively happen. If there is a hole like
that they can not use it on everybody, because it would get known
eventually and there would be hell to pay. Someone would murder them.
Obviously there are spy tools, but they target just a few individuals,
and secretively.
It is impossible to have a backdoor and use it to scan all the messages,
to scan everybody. Simply too dangerous for them.
>
>>> On 06/11/2023 11:25, Java Jive wrote:
>>> >
>>> > Except Google are already known to be doing this - by their own
>>> > admission they already scan all emails on gmail, etc. I don't
>>> > knowingly use cloud services, and therefore haven't read any of the
>>> > T&C of any cloud service, but I wouldn't be at all surprised to find
>>> > somewhere in there some phrase such as:
>>> >
>>> > "I agree that <Google|whoever> scans my data for malware and the
>>> > purpose of improving their services to me."
>>>
>>> So ISTM that I've been entirely consistent in what I've said.
>>
>> Consistently paranoid without justification.
>
> I'm not paranoid at all, just pointing that you are mistaken in your
> assertion that "No, no big company with a modicum of sense would do
> that. Just collecting data, massively, to analyze and target publicity?"
> because that is *exactly* how Google make 80% of their revenue:
Ad it is in their T&C, and doesn't apply to E2EE streams.
>
> https://www.statista.com/statistics/266249/advertising-revenue-of-google/
>
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
| From | Java Jive <java@evij.com.invalid> |
|---|---|
| Date | 2023-11-09 23:41 +0000 |
| Message-ID | <uijqmd$2empe$1@dont-email.me> |
| In reply to | #109889 |
On 09/11/2023 21:38, Carlos E. R. wrote: > > On 2023-11-09 22:17, Java Jive wrote: >> >> On 09/11/2023 19:44, Carlos E. R. wrote: >>> >>> On 2023-11-09 18:09, Java Jive wrote: >>>> >>>> Eh? Let me remind how this whole subthread began, which was as >>>> follows: >>>> >>>> On 05/11/2023 15:57, Jeff Layman wrote: >>>> > >>>> > I assume that if Google gets their success with RCS that would mean >>>> > more data available for analysis by them, and more ads for us. >>>> >>>> [Note: I've already pointed out that he should have said "more >>>> targetted ads for us."] >>>> >>>> To which Carlos replied: >>>> >>>> On 06/11/2023 00:53, Carlos E. R. wrote: >>>> > >>>> > No, no big company with a modicum of sense would do that. Just >>>> > collecting data, massively, to analyze and target publicity? That >>>> > would get known, many people need to be in the know to make use of >>>> > that lot of data. Too risky. Thus, not likely. >>>> >>>> But Google are already known to do just that, viz: "Just collecting >>>> data, massively, to analyze and target publicity", so I replied: >>> >>> No, they are not known to do just that with E2EE streams. >> >> Not *known* to be happening with E2EE streams doesn't mean that in >> fact it isn't happening, because, if it was, presumably the intention >> would be to ensure that it wasn't widely known; I have never tried to >> claim that it was happening or was not, merely I'm pointing out that >> in principle it *could* happen, and that your faith in Google or any >> similar company is misplaced, and, even worse, that the reason you >> gave for your faith is actually false, as I have shown below ... > > NO. It's no good just denying it, what you wrote is still quoted above, and the facts that disprove it are still linked, with further additions, below. > What I say is that it can not massively happen. If there is a hole like > that they can not use it on everybody, because it would get known > eventually and there would be hell to pay. Someone would murder them. > > Obviously there are spy tools, but they target just a few individuals, > and secretively. That may have been what you meant, but it's not what you wrote. We are not psychic, and can only argue with what you actually wrote. > It is impossible to have a backdoor and use it to scan all the messages, > to scan everybody. Simply too dangerous for them. How many times do I have to point out that it doesn't have to be a backdoor, when the front door is wide open. For example, most devices can support accessibility functionality such as screen-readers. Like I said, the foundations of your faith are false. >> I'm not paranoid at all, just pointing that you are mistaken in your >> assertion that "No, no big company with a modicum of sense would do >> that. Just collecting data, massively, to analyze and target >> publicity?" because that is *exactly* how Google make 80% of their >> revenue: > > Ad it is in their T&C, and doesn't apply to E2EE streams. Firstly, if, as you claim, you had read the T&C of GMail and therefore knew that scanning was in their T&C, why did you write the falsehood requoted above that began this subthread? However, see new information below ... Secondly, to find out what else may be going on, at very least you'd have to examine the T&C of Android itself, not just the E2EE encryption software or of any app that uses it, but, preferably also, you'd have to examine all the Android code. >> https://www.statista.com/statistics/266249/advertising-revenue-of-google/ I was trying to find out what percentage of GMail users were actually aware that their mails were scanned, and found these instead: Google will stop scanning content of personal emails https://www.theguardian.com/technology/2017/jun/26/google-will-stop-scanning-content-of-personal-emails "Although G Suite customers, who pay Google for business use of a portfolio of web apps including Gmail, Google Docs, Calendar and Contacts, have never had their messages scanned for use in advertising, many potential customers were nonetheless put off the product by the mistaken impression that they were, Greene told Bloomberg. “What we’re going to do is make it unambiguous,” she said." ... so, basically, we have business users to thank for forcing Google partially to clean up GMail for personal users, and, according to the same article, their cloud platforms as well. And ... Google promised not to scan Gmail for targeted ads—but for how long? https://arstechnica.com/tech-policy/2017/09/google-promised-not-to-scan-gmail-for-targeted-ads-but-for-how-long/ "On July 23, Google promised with great fanfare that it would stop scanning consumers' Gmail messages to serve targeted, contextually aware ads. The announcement—which put Gmail in line with competing services and Google's paid e-mail for government, business, and education sectors—was published widely, from tech blogs to the mainstream media. "Free consumer Gmail users," Google said, "can remain confident that Google will keep privacy and security paramount as we continue to innovate." However, court documents suggest that this could be temporary. A month after Google's announcement, the company quietly agreed to settle a class-action lawsuit alleging that the targeted-advertising scanning was illegal wiretapping. That deal, in which a federal judge gave "preliminarily approval" (PDF link) to on Thursday, binds Google for just three years." ... and ... How private is your Gmail, and should you switch? https://www.theguardian.com/technology/2021/may/09/how-private-is-your-gmail-and-should-you-switch "Although Google stopped scanning email content to tailor ads in 2017, last year the company started showing shopping ads in Gmail. And it still scans emails to facilitate so-called smart features such as the ability to add holiday bookings or deliveries straight to your calendar, or to autocomplete suggestions. Every way you interact with your Gmail account can be monitored, such as the dates and times you email at, who you are talking to, and topics you choose to email about, says Rowenna Fielding, founder of privacy consultancy Miss IG Geek. How Google uses your data Much of the information collected by Gmail and shared with advertisers is metadata – data about data. But if you carry cookies from other Google services, your activity can be correlated or “fingerprinted” from associated products such as Google Maps and YouTube. “Gmail becomes a window into your entire online life because of how wide and deep their surveillance architecture goes,” Fielding says. “Practically everything you do online will feed back to Google.” Google claims none of the data collected from scanning emails for purchase information, delivery tracking numbers and flight bookings is used for advertising, but as Andy Yen, founder and CEO of secure email service ProtonMail says: “It remains a fact that Google keeps a record of these events and logs them regardless.”" The above article is worth reading in its entirety. But even worse ... Google Still Lets Third-Party Devs Scan Your Email https://www.tomshardware.com/news/google-lets-developers-scan-email,37829.html "How else is a third-party app made specifically for Gmail supposed to function? People use these products because they want to be able to handle their inboxes better, extract information from the far-too-many emails they receive each day, or do something else that Gmail doesn't. Being upset that Google lets developers access this data is like someone in a high-rise being mad at their doorman for letting UPS into the building. There is one key difference: the WSJ reported in July that some of these developers were having their employees read some emails themselves so they could train AI. Developers can also share information with outside companies, meaning information gleaned via email scanning could be used to inform advertisements, for example. A lot of Gmail users probably didn't realize the contents of their emails could be used in that way." Etc, etc. Expert opinion seems united on the point that, while other firms aren't very much better, GMail are consistently the worst offenders for personal data collection, aka snooping. Sadly, I wasn't able to discover what percentage of GMail users were or are aware of their emails being scanned. Whether by Google or others barely seems relevant to me, my point being that it shouldn't be happening at all. However, legally it might make a difference, because the user signs Google's T&C, but not those of others business entities. -- Fake news kills! I may be contacted via the contact address given on my website: www.macfh.co.uk
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Date | 2023-11-10 15:06 +0100 |
| Message-ID | <kr6ro2FehloU4@mid.individual.net> |
| In reply to | #109900 |
On 2023-11-10 00:41, Java Jive wrote:
> On 09/11/2023 21:38, Carlos E. R. wrote:
>> > On 2023-11-09 22:17, Java Jive wrote:
>>>
>>> On 09/11/2023 19:44, Carlos E. R. wrote:
>>>>
>>>> On 2023-11-09 18:09, Java Jive wrote:
>>>>>
>>>>> Eh? Let me remind how this whole subthread began, which was as
>>>>> follows:
>>>>>
>>>>> On 05/11/2023 15:57, Jeff Layman wrote:
>>>>> >
>>>>> > I assume that if Google gets their success with RCS that would mean
>>>>> > more data available for analysis by them, and more ads for us.
>>>>>
>>>>> [Note: I've already pointed out that he should have said "more
>>>>> targetted ads for us."]
>>>>>
>>>>> To which Carlos replied:
>>>>>
>>>>> On 06/11/2023 00:53, Carlos E. R. wrote:
>>>>> >
>>>>> > No, no big company with a modicum of sense would do that. Just
>>>>> > collecting data, massively, to analyze and target publicity? That
>>>>> > would get known, many people need to be in the know to make use of
>>>>> > that lot of data. Too risky. Thus, not likely.
>>>>>
>>>>> But Google are already known to do just that, viz: "Just collecting
>>>>> data, massively, to analyze and target publicity", so I replied:
>>>>
>>>> No, they are not known to do just that with E2EE streams.
>>>
>>> Not *known* to be happening with E2EE streams doesn't mean that in
>>> fact it isn't happening, because, if it was, presumably the intention
>>> would be to ensure that it wasn't widely known; I have never tried to
>>> claim that it was happening or was not, merely I'm pointing out that
>>> in principle it *could* happen, and that your faith in Google or any
>>> similar company is misplaced, and, even worse, that the reason you
>>> gave for your faith is actually false, as I have shown below ...
>>
>> NO.
>
> It's no good just denying it, what you wrote is still quoted above, and
> the facts that disprove it are still linked, with further additions, below.
No, they are not. It is just your paranoia, and it is EOD for me. Bye.
Not even reading the rest.
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
| From | Java Jive <java@evij.com.invalid> |
|---|---|
| Date | 2023-11-10 14:45 +0000 |
| Message-ID | <uilfm7$2se4t$2@dont-email.me> |
| In reply to | #109916 |
On 10/11/2023 14:06, Carlos E. R. wrote: > > On 2023-11-10 00:41, Java Jive wrote: >> >> It's no good just denying it, what you wrote is still quoted above, >> and the facts that disprove it are still linked, with further >> additions, below. > > No, they are not. It is just your paranoia, and it is EOD for me. Bye. > > Not even reading the rest. To clarify, like it or not, your statement that "no big company with a modicum of sense would do that. Just collecting data, massively, to analyze and target publicity?" has been proven to be false; it's exactly how Google makes 80% of its revenue. -- Fake news kills! I may be contacted via the contact address given on my website: www.macfh.co.uk
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Date | 2023-11-09 15:22 +0100 |
| Message-ID | <kr488kFsdr5U6@mid.individual.net> |
| In reply to | #109845 |
On 2023-11-09 13:45, Java Jive wrote:
> On 09/11/2023 11:02, Carlos E. R. wrote:
>> On 2023-11-09 11:17, Java Jive wrote:
>>> On 08/11/2023 14:53, Frank Slootweg wrote:
>>>>
>>>> Java Jive <java@evij.com.invalid> wrote:
>>>>>
>>>>> On 07/11/2023 20:26, Carlos E. R. wrote:
>>>>>>
>>>>>> Oh, I did reply. You are not ilustrate enough to understand.
>>>>>
>>>>> LOL! You are not 'ilustrate' enough comment about others!
>>>>
>>>> And how's your Spanish? His English is very good, so if he
>>>> happens to
>>>> make a spelling error, just move on.
>>>
>>> My Spanish is almost non-existent, but then I'm not trying to
>>> converse in it. Anyway, the whole point is that it's not only a
>>> spelling error, it's entirely the wrong choice of word, so wrong that
>>> I'm not sure actually what he intended to say - if anything, that's
>>> a malapropism.
>>>
>>>> Anyway, before criticizing others, first learn the difference
>>>> between
>>>> end-to-end-encryption and no encryption. That Joerg is siding with you,
>>>> should be a red flag, a *big* one!
>>>
>>> No-one has answered my basic point that, if Google run the OS, and
>>> Carlos can read the message, so can Google, and, given Google's track
>>> record, most probably they will.
>>
>> Yes, we did.
>
> No, you didn't ...
>
>> Google can not read the messages, that's the whole point of E2EE.
>
> ... because Google is running the OS that is decrypting it for you.
>
Irrelevant.
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
Page 4 of 6 — ← Prev page 1 2 3 [4] 5 6 Next page →
Back to top | Article view | comp.mobile.android
csiph-web