Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.mobile.android > #109970
| From | Java Jive <java@evij.com.invalid> |
|---|---|
| Newsgroups | comp.mobile.android |
| Subject | Re: Backups |
| Date | 2023-11-10 23:00 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <uimclh$32a7c$1@dont-email.me> (permalink) |
| References | (13 earlier) <uilfk9$2se4t$1@dont-email.me> <uim0a4.udc.1@ID-201911.user.individual.net> <kr7dhnFiaveU4@mid.individual.net> <uim759$318rv$1@dont-email.me> <kr7o1dFiavdU11@mid.individual.net> |
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
Back to comp.mobile.android | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
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
csiph-web