Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.mobile.android > #109487 > unrolled thread

Backups

Started byJeff Layman <Jeff@invalid.invalid>
First post2023-11-02 20:23 +0000
Last post2023-11-03 17:36 +0000
Articles 20 on this page of 108 — 17 participants

Back to article view | Back to comp.mobile.android


Contents

  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 3 of 6 — ← Prev page 1 2 [3] 4 5 6  Next page →


#109805

From"Carlos E. R." <robin_listas@es.invalid>
Date2023-11-08 19:54 +0100
Message-ID<kr23qqFepp5U5@mid.individual.net>
In reply to#109802
On 2023-11-08 17:33, Frank Slootweg wrote:
> Carlos E. R. <robin_listas@es.invalid> wrote:
>> On 2023-11-08 15:53, Frank Slootweg wrote:
>>> Java Jive <java@evij.com.invalid> wrote:
>>>> On 07/11/2023 20:26, Carlos E. R. wrote:
>>>>>
>>>>> On 2023-11-06 22:08, Java Jive wrote:
>>>>>>
>>>>>> So you have no reply.  End of argument.
>>>>>
>>>>> 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.
>>
>> Thank you.
>>
>> My speller says 'ilustrate' is correct.
> 
>    It probably should be 'illustrate', with double-l, but I doubt that's
> what you meant. You probably meant 'literate', the opposite of
> 'illiterate'. Or 'illustrious'?

illustrated, being an illustrated person. Maybe the expression did not 
caught in English. It relates to people from the illustration epoch 
(Spanish and French), which wikipedia says it is "Age of Enlightenment" 
in English.

What language teachers call "a false friend". A word in the second 
language almost identical to another in the first language, with a 
totally different meaning.

:-)

...

-- 
Cheers,
        Carlos E.R.

[toc] | [prev] | [next] | [standalone]


#109808

FromKenan ÇOT <kenancot34@gmail.com>
Date2023-11-08 11:18 -0800
Message-ID<d3a082d0-09dd-422b-a9be-a14132005a4fn@googlegroups.com>
In reply to#109805
8 Kasım 2023 Çarşamba tarihinde saat 21:54:21 UTC+3 itibarıyla Carlos E. R. şunları yazdı:
> On 2023-11-08 17:33, Frank Slootweg wrote: 
> > Carlos E. R. <robin_...@es.invalid> wrote: 
> >> On 2023-11-08 15:53, Frank Slootweg wrote: 
> >>> Java Jive <ja...@evij.com.invalid> wrote: 
> >>>> On 07/11/2023 20:26, Carlos E. R. wrote: 
> >>>>> 
> >>>>> On 2023-11-06 22:08, Java Jive wrote: 
> >>>>>> 
> >>>>>> So you have no reply.  End of argument. 
> >>>>> 
> >>>>> 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. 
> >> 
> >> Thank you. 
> >> 
> >> My speller says 'ilustrate' is correct. 
> > 
> > It probably should be 'illustrate', with double-l, but I doubt that's 
> > what you meant. You probably meant 'literate', the opposite of 
> > 'illiterate'. Or 'illustrious'?
> illustrated, being an illustrated person. Maybe the expression did not 
> caught in English. It relates to people from the illustration epoch 
> (Spanish and French), which wikipedia says it is "Age of Enlightenment" 
> in English. 
> 
> What language teachers call "a false friend". A word in the second 
> language almost identical to another in the first language, with a 
> totally different meaning. 
> 
> :-) 
> 
> ... 
> 
> -- 
> Cheers, 
> Carlos E.R.

https://www.teknofeed.com/clash-of-clans-12-seviye-koy-duzeni/

[toc] | [prev] | [next] | [standalone]


#109833

FromJava Jive <java@evij.com.invalid>
Date2023-11-09 10:17 +0000
Message-ID<uiibji$25agf$1@dont-email.me>
In reply to#109796
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.

-- 

Fake news kills!

I may be contacted via the contact address given on my website: 
www.macfh.co.uk

[toc] | [prev] | [next] | [standalone]


#109838

From"Carlos E. R." <robin_listas@es.invalid>
Date2023-11-09 12:02 +0100
Message-ID<kr3sioFsdr5U4@mid.individual.net>
In reply to#109833
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.

Google can not read the messages, that's the whole point of E2EE.

-- 
Cheers,
        Carlos E.R.

[toc] | [prev] | [next] | [standalone]


#109845

FromJava Jive <java@evij.com.invalid>
Date2023-11-09 12:45 +0000
Message-ID<uiik9m$26t21$1@dont-email.me>
In reply to#109838
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.

-- 

Fake news kills!

I may be contacted via the contact address given on my website: 
www.macfh.co.uk

[toc] | [prev] | [next] | [standalone]


#109846

FromFrank Slootweg <this@ddress.is.invalid>
Date2023-11-09 13:17 +0000
Message-ID<uiiplg.jd4.1@ID-201911.user.individual.net>
In reply to#109845
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.

> > 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.

  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?

[toc] | [prev] | [next] | [standalone]


#109847

FromJava Jive <java@evij.com.invalid>
Date2023-11-09 14:05 +0000
Message-ID<uiioul$27pis$1@dont-email.me>
In reply to#109846
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.

>>> 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.

>    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?  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, 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.

-- 

Fake news kills!

I may be contacted via the contact address given on my website: 
www.macfh.co.uk

[toc] | [prev] | [next] | [standalone]


#109853

FromFrank Slootweg <this@ddress.is.invalid>
Date2023-11-09 15:22 +0000
Message-ID<uij0vb.18lc.1@ID-201911.user.individual.net>
In reply to#109847
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.

> >>> 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).

  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.

>           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".

> 				     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 who 'compares' totally different subject
matters.

  I'm done.

'End-to-end encryption'
<https://en.wikipedia.org/wiki/End-to-end_encryption>

[toc] | [prev] | [next] | [standalone]


#109861

FromJava Jive <java@evij.com.invalid>
Date2023-11-09 17:09 +0000
Message-ID<uij3nn$29v49$1@dont-email.me>
In reply to#109853
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.

>>>>> 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.

>    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.

>>            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.

>> 				     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:

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.

-- 

Fake news kills!

I may be contacted via the contact address given on my website: 
www.macfh.co.uk

[toc] | [prev] | [next] | [standalone]


#109867

FromFrank Slootweg <this@ddress.is.invalid>
Date2023-11-09 19:04 +0000
Message-ID<uije07.cvk.1@ID-201911.user.individual.net>
In reply to#109861
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:
> >>>>>>>>>
> >>>>>>>>> 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.
> >>>
> >>>>>> 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.

  So you keep saying, but your definition of "snooping" seems to be a
rather strange one. Case in point: Google is *not* "snooping" Gmail.
What they do - i.e. scanning - is in their T&Cs. Don't like it, don't
use it. *And*, as I said, but you 'conveniently' ignored, that evil
"snooping" of my Gmail hasn't resulted in a single ad in over 15 years.
Bad Google, bad, bad Google!

> >>>>> 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.

> >    Example: WhatsApp and other IM platforms.

  Hmm!? No comment? Strange!

> >>>     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.

  As do many others, so it's not a reason to single them out, but you
still did and do.

  Face it, you just have an agenda. Don't insult us trying to hide it
behind (non-)technical claptrap.

  BTW, I assume you don't actually own or use any Android devices,
Google services, etc..

> >>            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.

  See above.

> >>                                   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.

  Ah, at least now you include "other like companies", so it's just a
general concern and not really relevant to Google's RCS E2EE. Check.

> > who 'compares' totally different subject
> > matters.
> 
> Eh?  Let me remind how this whole subthread began, which was as follows:
[lots deleted]
> So ISTM that I've been entirely consistent in what I've said.

  Yes, you've been consistent. Consistently biased and consistently
wrong.

  EOD.

[toc] | [prev] | [next] | [standalone]


#109881

FromJava Jive <java@evij.com.invalid>
Date2023-11-09 20:44 +0000
Message-ID<uijgbo$2clm5$1@dont-email.me>
In reply to#109867
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:
>>>>>>>>>>>
>>>>>>>>>>> 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.
>>>>>
>>>>>>>> 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.
> 
>    So you keep saying, but your definition of "snooping" seems to be a
> rather strange one. Case in point: Google is *not* "snooping" Gmail.
> What they do - i.e. scanning - is in their T&Cs. Don't like it, don't
> use it. *And*, as I said, but you 'conveniently' ignored, that evil
> "snooping" of my Gmail hasn't resulted in a single ad in over 15 years.
> Bad Google, bad, bad Google!

Whether or not it's in their T&C, which almost no-one reads anyway  - 
see the definition of the 'uncontract' in Shoshana Zuboff's book  - 
scanning email is a form of snooping, because it is concerning 
themselves with private things that shouldn't be their concern.

>>>>>>> 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?

>>>     Example: WhatsApp and other IM platforms.
> 
>    Hmm!? No comment? Strange!

They both have to write to the screen or other output device, so they 
are covered by what I had already written.

>>>>>      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.
> 
>    As do many others, so it's not a reason to single them out, but you
> still did and do.

On the contrary, I specifically wrote, as is still quoted below: "*any* 
company, *including* Google"

>    Face it, you just have an agenda. Don't insult us trying to hide it
> behind (non-)technical claptrap.

My so-called 'agenda' was only ever to correct what Carlos wrote.

>    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.

>>>>             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.
> 
>    See above.

There is nothing above that is relevant to my point.

>>>>                                    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.
> 
>    Ah, at least now you include "other like companies", so it's just a
> general concern and not really relevant to Google's RCS E2EE. Check.

I've never said anything different.

>>> who 'compares' totally different subject
>>> matters.
>>
>> Eh?  Let me remind how this whole subthread began, which was as follows:
> [lots deleted]
>> So ISTM that I've been entirely consistent in what I've said.
> 
>    Yes, you've been consistent. Consistently biased and consistently
> wrong.

On the contrary, you haven't yet been able to substantiate Carlos' 
original claim that ...

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?

... whereas I've been able to give a concrete counter-example.

>    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.

-- 

Fake news kills!

I may be contacted via the contact address given on my website: 
www.macfh.co.uk

[toc] | [prev] | [next] | [standalone]


#109882

From"Carlos E. R." <robin_listas@es.invalid>
Date2023-11-09 21:49 +0100
Message-ID<kr4uukFsdr5U14@mid.individual.net>
In reply to#109881
On 2023-11-09 21:44, Java Jive 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:
>>>>>>>>>>>>
>>>>>>>>>>>> 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.
>>>>>>
>>>>>>>>> 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.
>>
>>    So you keep saying, but your definition of "snooping" seems to be a
>> rather strange one. Case in point: Google is *not* "snooping" Gmail.
>> What they do - i.e. scanning - is in their T&Cs. Don't like it, don't
>> use it. *And*, as I said, but you 'conveniently' ignored, that evil
>> "snooping" of my Gmail hasn't resulted in a single ad in over 15 years.
>> Bad Google, bad, bad Google!
> 
> Whether or not it's in their T&C, which almost no-one reads anyway  - 

I read them.

> see the definition of the 'uncontract' in Shoshana Zuboff's book  - 
> scanning email is a form of snooping, because it is concerning 
> themselves with private things that shouldn't be their concern.

IT IS THEIR CONCERN. They said in their T&C they were going to do it. 
You accepted this, and you clicked "I have read the T&C.


>>>>>>>> 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?
> 
>>>>     Example: WhatsApp and other IM platforms.
>>
>>    Hmm!? No comment? Strange!
> 
> They both have to write to the screen or other output device, so they 
> are covered by what I had already written.
> 
>>>>>>      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.
>>
>>    As do many others, so it's not a reason to single them out, but you
>> still did and do.
> 
> On the contrary, I specifically wrote, as is still quoted below: "*any* 
> company, *including* Google"
> 
>>    Face it, you just have an agenda. Don't insult us trying to hide it
>> behind (non-)technical claptrap.
> 
> My so-called 'agenda' was only ever to correct what Carlos wrote.
> 
>>    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.
> 
>>>>>             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.
>>
>>    See above.
> 
> There is nothing above that is relevant to my point.
> 
>>>>>                                    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.
>>
>>    Ah, at least now you include "other like companies", so it's just a
>> general concern and not really relevant to Google's RCS E2EE. Check.
> 
> I've never said anything different.
> 
>>>> who 'compares' totally different subject
>>>> matters.
>>>
>>> Eh?  Let me remind how this whole subthread began, which was as follows:
>> [lots deleted]
>>> So ISTM that I've been entirely consistent in what I've said.
>>
>>    Yes, you've been consistent. Consistently biased and consistently
>> wrong.
> 
> On the contrary, you haven't yet been able to substantiate Carlos' 
> original claim that ...
> 
> 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?
> 
> ... whereas I've been able to give a concrete counter-example.
> 

No, you haven't.

>>    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.

Yours is simply ridiculous.

-- 
Cheers,
        Carlos E.R.

[toc] | [prev] | [next] | [standalone]


#109888

FromJava Jive <java@evij.com.invalid>
Date2023-11-09 21:35 +0000
Message-ID<uijja8$2d9mf$1@dont-email.me>
In reply to#109882
On 09/11/2023 20:49, Carlos E. R. wrote:
>
> On 2023-11-09 21:44, Java Jive wrote:
>>
>> On 09/11/2023 19:04, Frank Slootweg wrote:
>>>
>>> Java Jive <java@evij.com.invalid> wrote:
>>>>
>>>> The book is totally relevant, long sections of it details the evidence
>>>> of Google's snooping.
>>>
>>>    So you keep saying, but your definition of "snooping" seems to be a
>>> rather strange one. Case in point: Google is *not* "snooping" Gmail.
>>> What they do - i.e. scanning - is in their T&Cs. Don't like it, don't
>>> use it. *And*, as I said, but you 'conveniently' ignored, that evil
>>> "snooping" of my Gmail hasn't resulted in a single ad in over 15 years.
>>> Bad Google, bad, bad Google!
>>
>> Whether or not it's in their T&C, which almost no-one reads anyway  - 
> 
> I read them.

Fine, but most people don't.

>> see the definition of the 'uncontract' in Shoshana Zuboff's book  - 
>> scanning email is a form of snooping, because it is concerning 
>> themselves with private things that shouldn't be their concern.
> 
> IT IS THEIR CONCERN. They said in their T&C they were going to do it. 
> You accepted this, and you clicked "I have read the T&C.

Your emails should be private and not anyone else's concern.

>> On the contrary, you haven't yet been able to substantiate Carlos' 
>> original claim that ...
>>
>> 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?
>>
>> ... whereas I've been able to give a concrete counter-example.
> 
> No, you haven't.

See other post, 80% of Google's income comes from targeted advertising 
using big data, exactly opposite to what you wrote above.

>>>    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.
> 
> Yours is simply ridiculous.

However ridiculous or not it is, it has to be less ridiculous than 
yours, because it is supported by the publicly known facts about Google, 
Ad Sense, and the income they derive from the latter, as linked 
elsewhere in the thread.

-- 

Fake news kills!

I may be contacted via the contact address given on my website: 
www.macfh.co.uk

[toc] | [prev] | [next] | [standalone]


#109894

From"Carlos E. R." <robin_listas@es.invalid>
Date2023-11-09 23:21 +0100
Message-ID<kr54agF5kmkU1@mid.individual.net>
In reply to#109888
On 2023-11-09 22:35, Java Jive wrote:
> On 09/11/2023 20:49, Carlos E. R. wrote:
>>
>> On 2023-11-09 21:44, Java Jive wrote:
>>>
>>> On 09/11/2023 19:04, Frank Slootweg wrote:
>>>>
>>>> Java Jive <java@evij.com.invalid> wrote:
>>>>>
>>>>> The book is totally relevant, long sections of it details the evidence
>>>>> of Google's snooping.
>>>>
>>>>    So you keep saying, but your definition of "snooping" seems to be a
>>>> rather strange one. Case in point: Google is *not* "snooping" Gmail.
>>>> What they do - i.e. scanning - is in their T&Cs. Don't like it, don't
>>>> use it. *And*, as I said, but you 'conveniently' ignored, that evil
>>>> "snooping" of my Gmail hasn't resulted in a single ad in over 15 years.
>>>> Bad Google, bad, bad Google!
>>>
>>> Whether or not it's in their T&C, which almost no-one reads anyway  - 
>>
>> I read them.
> 
> Fine, but most people don't.

Those can not complain.

>>> see the definition of the 'uncontract' in Shoshana Zuboff's book  - 
>>> scanning email is a form of snooping, because it is concerning 
>>> themselves with private things that shouldn't be their concern.
>>
>> IT IS THEIR CONCERN. They said in their T&C they were going to do it. 
>> You accepted this, and you clicked "I have read the T&C.
> 
> Your emails should be private and not anyone else's concern.

Well, it is not so. It is in the T&C. It is not a matter of opinion, it 
is the law.


>>> On the contrary, you haven't yet been able to substantiate Carlos' 
>>> original claim that ...
>>>
>>> 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?
>>>
>>> ... whereas I've been able to give a concrete counter-example.
>>
>> No, you haven't.
> 
> See other post, 80% of Google's income comes from targeted advertising 
> using big data, exactly opposite to what you wrote above.

I have, and you are simply wrong.

> 
>>>>    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.
>>
>> Yours is simply ridiculous.
> 
> However ridiculous or not it is, it has to be less ridiculous than 
> yours, because it is supported by the publicly known facts about Google, 
> Ad Sense, and the income they derive from the latter, as linked 
> elsewhere in the thread.
> 

LOL.

I'll just write you off as paranoic, and EOD.


-- 
Cheers,
        Carlos E.R.

[toc] | [prev] | [next] | [standalone]


#109901

FromJava Jive <java@evij.com.invalid>
Date2023-11-10 00:06 +0000
Message-ID<uijs70$2f08u$1@dont-email.me>
In reply to#109894
On 09/11/2023 22:21, Carlos E. R. wrote:
> On 2023-11-09 22:35, Java Jive wrote:
>> On 09/11/2023 20:49, Carlos E. R. wrote:
>>>
>>> On 2023-11-09 21:44, Java Jive wrote:
>>>>
>>>> On 09/11/2023 19:04, Frank Slootweg wrote:
>>>>>
>>>>> Java Jive <java@evij.com.invalid> wrote:
>>>>>>
>>>>>> The book is totally relevant, long sections of it details the 
>>>>>> evidence
>>>>>> of Google's snooping.
>>>>>
>>>>>    So you keep saying, but your definition of "snooping" seems to be a
>>>>> rather strange one. Case in point: Google is *not* "snooping" Gmail.
>>>>> What they do - i.e. scanning - is in their T&Cs. Don't like it, don't
>>>>> use it. *And*, as I said, but you 'conveniently' ignored, that evil
>>>>> "snooping" of my Gmail hasn't resulted in a single ad in over 15 
>>>>> years.
>>>>> Bad Google, bad, bad Google!
>>>>
>>>> Whether or not it's in their T&C, which almost no-one reads anyway  - 
>>>
>>> I read them.
>>
>> Fine, but most people don't.
> 
> Those can not complain.

That doesn't alter the fact that probably most people are not aware of 
the implications of using GMail, see my other post.

>>>> see the definition of the 'uncontract' in Shoshana Zuboff's book  - 
>>>> scanning email is a form of snooping, because it is concerning 
>>>> themselves with private things that shouldn't be their concern.
>>>
>>> IT IS THEIR CONCERN. They said in their T&C they were going to do it. 
>>> You accepted this, and you clicked "I have read the T&C.
>>
>> Your emails should be private and not anyone else's concern.
> 
> Well, it is not so. It is in the T&C. It is not a matter of opinion, it 
> is the law.

Legal right is not the same as ethical right.

>>>> On the contrary, you haven't yet been able to substantiate Carlos' 
>>>> original claim that ...
>>>>
>>>> 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?
>>>>
>>>> ... whereas I've been able to give a concrete counter-example.
>>>
>>> No, you haven't.
>>
>> See other post, 80% of Google's income comes from targeted advertising 
>> using big data, exactly opposite to what you wrote above.
> 
> I have, and you are simply wrong.

You can jump up and down screaming "YOU'RE WRONG!" like a spoilt child 
all you like, it doesn't alter one jot that the facts I've linked 
disprove what you claimed.

> LOL.
> 
> I'll just write you off as paranoic, and EOD.

LOL!  I'll just write you off as naive, and a bad loser.

-- 

Fake news kills!

I may be contacted via the contact address given on my website: 
www.macfh.co.uk

[toc] | [prev] | [next] | [standalone]


#109917

From"Carlos E. R." <robin_listas@es.invalid>
Date2023-11-10 15:08 +0100
Message-ID<kr6rqoFehloU5@mid.individual.net>
In reply to#109901
On 2023-11-10 01:06, Java Jive wrote:
> On 09/11/2023 22:21, Carlos E. R. wrote:
>> On 2023-11-09 22:35, Java Jive wrote:
>>> On 09/11/2023 20:49, Carlos E. R. wrote:


>> LOL.
>>
>> I'll just write you off as paranoic, and EOD.
> 
> 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.

-- 
Cheers,
        Carlos E.R.

[toc] | [prev] | [next] | [standalone]


#109923

FromJava Jive <java@evij.com.invalid>
Date2023-11-10 14:44 +0000
Message-ID<uilfk9$2se4t$1@dont-email.me>
In reply to#109917
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.

-- 

Fake news kills!

I may be contacted via the contact address given on my website: 
www.macfh.co.uk

[toc] | [prev] | [next] | [standalone]


#109949

FromFrank Slootweg <this@ddress.is.invalid>
Date2023-11-10 18:55 +0000
Message-ID<uim0a4.udc.1@ID-201911.user.individual.net>
In reply to#109923
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>

[toc] | [prev] | [next] | [standalone]


#109951

From"Carlos E. R." <robin_listas@es.invalid>
Date2023-11-10 20:10 +0100
Message-ID<kr7dhnFiaveU4@mid.individual.net>
In reply to#109949
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.

-- 
Cheers,
        Carlos E.R.

[toc] | [prev] | [next] | [standalone]


#109965

FromJava Jive <java@evij.com.invalid>
Date2023-11-10 21:26 +0000
Message-ID<uim759$318rv$1@dont-email.me>
In reply to#109951
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.  I am happy to accept that you may have *meant* that 
context, but it's not what you actually *said*, and I'm not the only one 
here who isn't psychic, because both Jörg Lorenz and Ed Cryer seem to 
have read your original quote the same way as I did.  And, it seems, 
despite everything that Frank Slootweg has posted since, so did he, 
because his first reply to me when I first pointed out your error 
contained zilch mention of E2EE either ...

On 06/11/2023 14:43, Frank Slootweg wrote:
 >
 >    The - snipped - issue was:
 >
 > <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>
 >
 >    So yes, they do*data analysis*  of your Gmail e-mail, but AFAICT
 > both Jeff's and Carlos' point is *ads*  and in over 15 years of having
 > (a) Gmail account(s), I still have to get the very first ad in or
 > triggered by Gmail!
 >
 >    As I said before, if Google is scanning my emails and allegedly
 > acting on that scanning, they are doing a very poor job, because after
 > the fact, I still get*in-browser*  (*not*  in email/Gmail) ads for
 > products which I already purchased and for which the order/receipt
 >/invoice/etc. are in that same Gmail mailbox! Can you say "stupid"!?
 > (Yes, people have explained why this is so, but that doesn't mean that
 > the end result isn't still stupid.)

So both of you are moving the goalposts to explain away your (Carlos') 
original error.  I accept that instead of allowing myself to be 
inveigled into following the moving goalposts I should have replied 
along the lines above sooner, and for that, I apologise, but you have 
yet to apologise for your error.

-- 

Fake news kills!

I may be contacted via the contact address given on my website: 
www.macfh.co.uk

[toc] | [prev] | [next] | [standalone]


Page 3 of 6 — ← Prev page 1 2 [3] 4 5 6  Next page →

Back to top | Article view | comp.mobile.android


csiph-web