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 5 of 6 — ← Prev page 1 2 3 4 [5] 6 Next page →
| From | Java Jive <java@evij.com.invalid> |
|---|---|
| Date | 2023-11-09 17:11 +0000 |
| Message-ID | <uij3rt$29v49$2@dont-email.me> |
| In reply to | #109849 |
On 09/11/2023 14:22, Carlos E. R. wrote: > > On 2023-11-09 13:45, Java Jive wrote: >> >>> 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. Sigh! How do you think it gets from the app using encryption onto the screen so that you can read it? -- Fake news kills! I may be contacted via the contact address given on my website: www.macfh.co.uk
[toc] | [prev] | [next] | [standalone]
| From | Jörg Lorenz <hugybear@gmx.net> |
|---|---|
| Date | 2023-11-06 17:19 +0100 |
| Message-ID | <uib3na$hcuh$2@dont-email.me> |
| In reply to | #109642 |
Am 06.11.23 um 01:53 schrieb Carlos E. R.: > On 2023-11-05 16: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. > > 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. Total nonsense! My God are you naïve! They do already such things. -- Gutta cavat lapidem (Ovid)
[toc] | [prev] | [next] | [standalone]
| From | Jörg Lorenz <hugybear@gmx.net> |
|---|---|
| Date | 2023-11-06 17:18 +0100 |
| Message-ID | <uib3kj$hcuh$1@dont-email.me> |
| In reply to | #109618 |
Am 05.11.23 um 16:57 schrieb Jeff Layman: > I guess my use of man-in-the-middle was somewhat misleading as it has a > specific meaning. Perhaps "backdoor" would have been a better choice. No. Google would be the man-in-the-middle. -- Gutta cavat lapidem (Ovid)
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Date | 2023-11-06 01:54 +0100 |
| Message-ID | <kqqrqbF8ghsU5@mid.individual.net> |
| In reply to | #109616 |
On 2023-11-05 15: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.
>
> However what's in RCS for Google is a competitor to iMessage. Especially in
> the US, Android suffers from 'green bubbles syndrome', where people buy
> iPhones because they get better messaging with their iPhone owning mates via
> iMessage, and Android owners have to fall back to SMS which is very much a
> second class citizen. RCS is Google's (umpteenth) attempt on an iMessage
> rival.
>
> (In the US iMessage has a big chunk of market share, in other countries this
> isn't really a thing - everyone uses WhatsApp or Telegram or whatever so the
> blue bubbles/green bubbles difference doesn't matter).
>
> If RCS succeeds, it address a key deficiency of Android compared with iOS
> and helps them sell more Android phones.
>
> Google is pushing the narrative that RCS is 'open' and iMessage is 'closed',
> but, with carriers throwing in the towel and using Google's server, it
> sounds like it's not a million miles different from iMessage.
>
> 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 can buy this analysis :-)
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
| From | Jörg Lorenz <hugybear@gmx.net> |
|---|---|
| Date | 2023-11-06 17:21 +0100 |
| Message-ID | <uib3qc$hcuh$3@dont-email.me> |
| In reply to | #109643 |
Am 06.11.23 um 01:54 schrieb Carlos E. R.: > On 2023-11-05 15:24, Theo wrote: >> 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 can buy this analysis :-) Nowhere near an analysis! *ROTFLSTC* RCS is already dead. -- Gutta cavat lapidem (Ovid)
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Date | 2023-11-06 18:33 +0100 |
| Message-ID | <kqsmbvFlgl5U5@mid.individual.net> |
| In reply to | #109674 |
On 2023-11-06 17:21, Jörg Lorenz wrote:
> Am 06.11.23 um 01:54 schrieb Carlos E. R.:
>> On 2023-11-05 15:24, Theo wrote:
>>> 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 can buy this analysis :-)
>
> Nowhere near an analysis! *ROTFLSTC*
> RCS is already dead.
Yeah, we know your manias.
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
| From | Jörg Lorenz <hugybear@gmx.net> |
|---|---|
| Date | 2023-11-06 19:06 +0100 |
| Message-ID | <uib9vu$ihbn$1@dont-email.me> |
| In reply to | #109680 |
On 06.11.23 18:33, Carlos E. R. wrote: > On 2023-11-06 17:21, Jörg Lorenz wrote: >> Am 06.11.23 um 01:54 schrieb Carlos E. R.: >>> On 2023-11-05 15:24, Theo wrote: >>>> 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 can buy this analysis :-) >> >> Nowhere near an analysis! *ROTFLSTC* >> RCS is already dead. > > > Yeah, we know your manias. You are not able to develop a critical attitude towards services you like as a fanboy. Google as man-in-the-middle? Never ever. Google tries for years now but without any success. *LOL* -- Gutta cavat lapidem (Ovid)
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Date | 2023-11-06 19:13 +0100 |
| Message-ID | <kqsoljFlgl5U6@mid.individual.net> |
| In reply to | #109687 |
On 2023-11-06 19:06, Jörg Lorenz wrote:
> On 06.11.23 18:33, Carlos E. R. wrote:
>> On 2023-11-06 17:21, Jörg Lorenz wrote:
>>> Am 06.11.23 um 01:54 schrieb Carlos E. R.:
>>>> On 2023-11-05 15:24, Theo wrote:
>>>>> 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 can buy this analysis :-)
>>>
>>> Nowhere near an analysis! *ROTFLSTC*
>>> RCS is already dead.
>>
>>
>> Yeah, we know your manias.
>
> You are not able to develop a critical attitude towards services you
> like as a fanboy.
>
> Google as man-in-the-middle? Never ever.
> Google tries for years now but without any success. *LOL*
>
Yeah, we know your manias.
Your opinion is noted and discarded.
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
| From | Ed Cryer <ed@somewhere.in.the.uk> |
|---|---|
| Date | 2023-11-06 18:49 +0000 |
| Message-ID | <uibcgc$j146$1@dont-email.me> |
| In reply to | #109687 |
Jörg Lorenz wrote: > On 06.11.23 18:33, Carlos E. R. wrote: >> On 2023-11-06 17:21, Jörg Lorenz wrote: >>> Am 06.11.23 um 01:54 schrieb Carlos E. R.: >>>> On 2023-11-05 15:24, Theo wrote: >>>>> 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 can buy this analysis :-) >>> >>> Nowhere near an analysis! *ROTFLSTC* >>> RCS is already dead. >> >> >> Yeah, we know your manias. > > You are not able to develop a critical attitude towards services you > like as a fanboy. > > Google as man-in-the-middle? Never ever. > Google tries for years now but without any success. *LOL* > Carlos is toying with you. Google's abusive behaviour is patent, obvious and wide-open to anybody with half a brain. Don't humour him. He needs a head-blow. Ed
[toc] | [prev] | [next] | [standalone]
| From | Larry Wolff <larrywolff@larrywolff.net> |
|---|---|
| Date | 2023-11-25 09:35 -0500 |
| Message-ID | <ujt0mo$1gv4u$1@novabbs.org> |
| In reply to | #109674 |
On this Mon, 6 Nov 2023 17:21:32 +0100, Jörg Lorenz wrote: > RCS is already dead. If RCS is dead, why is Apple saying they'll be adding RCS into iOS 18?
[toc] | [prev] | [next] | [standalone]
| From | Joerg Lorenz <hugybear@gmx.net> |
|---|---|
| Date | 2023-11-25 16:51 +0100 |
| Message-ID | <ujt569$2rfog$1@dont-email.me> |
| In reply to | #110577 |
On 25.11.23 15:35, Larry Wolff wrote: > On this Mon, 6 Nov 2023 17:21:32 +0100, Jörg Lorenz wrote: > >> RCS is already dead. > > If RCS is dead, why is Apple saying they'll be adding RCS into iOS 18? Tactics. It won't change almost nothing. The *European Digital Markets Act* is looming over all the big tech companies. RCS is de facto dead. Android users will be even the bigger losers trying to chat with iOS-users. Take Signal or something else but certainly not such a gimp. -- Sent with Betterbird by a Penguin. Simply better. www.betterbird.eu
[toc] | [prev] | [next] | [standalone]
| From | Arno Welzel <usenet@arnowelzel.de> |
|---|---|
| Date | 2023-12-04 20:44 +0100 |
| Message-ID | <kt6og8Ff0atU4@mid.individual.net> |
| In reply to | #110583 |
Joerg Lorenz, 2023-11-25 16:51: > On 25.11.23 15:35, Larry Wolff wrote: >> On this Mon, 6 Nov 2023 17:21:32 +0100, Jörg Lorenz wrote: >> >>> RCS is already dead. >> >> If RCS is dead, why is Apple saying they'll be adding RCS into iOS 18? > > Tactics. It won't change almost nothing. > The *European Digital Markets Act* is looming over all the big tech > companies. RCS is de facto dead. > > Android users will be even the bigger losers trying to chat with > iOS-users. Take Signal or something else but certainly not such a gimp. More than 1 billion active users does not look very "dead" to me: <https://blog.google/products/android/7-new-messages-features/> <https://www.juniperresearch.com/press/rcs-capable-subscribers-to-reach-1bn> Also an estimated market size of 2 billion USD in 2022 and 14.4 billion USD within the next 10 years: <https://www.gminsights.com/industry-analysis/rich-communication-services-market> -- Arno Welzel https://arnowelzel.de
[toc] | [prev] | [next] | [standalone]
| From | Wally J <walterjones@invalid.nospam> |
|---|---|
| Date | 2023-11-04 21:29 -0400 |
| Message-ID | <ui6r52$oct3$1@paganini.bofh.team> |
| In reply to | #109555 |
Jeff Layman <Jeff@invalid.invalid> wrote >> Why in the first place did you buy an Android smartphone? Google has >> your data anyway. > > Sadly, you're probably right. If you think Joerg is right, then that's a sad assessment on your part. Apple forces you to constantly log into its mothership tracking servers. Google can't. Think about that before you assess that one may be safer than the other.
[toc] | [prev] | [next] | [standalone]
| From | Jeff Layman <Jeff@invalid.invalid> |
|---|---|
| Date | 2023-11-05 16:03 +0000 |
| Message-ID | <ui8ecn$21gb$2@dont-email.me> |
| In reply to | #109601 |
On 05/11/2023 01:29, Wally J wrote: > Jeff Layman <Jeff@invalid.invalid> wrote > >>> Why in the first place did you buy an Android smartphone? Google has >>> your data anyway. >> >> Sadly, you're probably right. > > If you think Joerg is right, then that's a sad assessment on your part. > > Apple forces you to constantly log into its mothership tracking servers. > Google can't. > > Think about that before you assess that one may be safer than the other. I think you're misinterpreting what I'm saying here. I never said that Android was better or worse than Apple regarding privacy. Apple are very closed-source when it comes to their OS, and Google are much more open. But that doesn't mean we /know/ what Google are doing, as some of their code is proprietary. And, as I pointed out in my reply to Theo, can anyone know what all the millions of line of /open/ code in Android are for? FWIW, I wouldn't trust either to not mine data. -- Jeff
[toc] | [prev] | [next] | [standalone]
| From | AJL <noemail@none.com> |
|---|---|
| Date | 2023-11-03 09:01 -0700 |
| Message-ID | <ui35gm$2rb86$1@dont-email.me> |
| In reply to | #109505 |
On 11/3/2023 1:27 AM, Jeff Layman wrote: > Do you really believe that Google doesn't scan all the info you store > on their Cloud servers? I think it's a philosophical question. If a HUMAN reads my stuff it would bother me. If my stuff is bits and bytes in a SERVER somewhere, not so much. If you're bothered by the bits and bytes server scenario then you better cancel all your credit cards, never use any doctors, don't drive, don't work, don't pay taxes, in other words don't have a life. Because your life is on dozens of servers that you have no control over whether you use Google or not... > <https://www.comparitech.com/blog/information-security/google-drive-secure/#Google_Drive_privacy_issues>: Interesting article. I liked this quote: "For most computer users, Google Drive is more reliable, automatically backed up, relatively safe from ransomware, and almost certainly more secure from theft. In general, the benefits largely outweigh the risks." > "Google has, over the years, perfected the art of surveillance > capitalism—where your data is mined and sold to advertisers, which > is then used to manipulate or influence your buying behavior." They're pretty sneaky here. I've used Google Drive for years and have yet to be able to tie any advertising to it. Where are the ads?? > You might also find it interesting to read the section > "Relinquishing control". Scary. Kinda like the legal mumbo-jumbo I gotta sign for a lot of services (like the doctor). Does anybody read all those pages of legalese before they sign...
[toc] | [prev] | [next] | [standalone]
| From | Theo <theom+news@chiark.greenend.org.uk> |
|---|---|
| Date | 2023-11-03 13:31 +0000 |
| Message-ID | <YIy*n2tuz@news.chiark.greenend.org.uk> |
| In reply to | #109487 |
Jeff Layman <Jeff@invalid.invalid> wrote: > Looking at other backup apps on Play Store or F-Droid shows how confused > the picture is. Some backup specifics like apps, contacts, SMS/MMS > messages, or photos, while others do several. Some state they can't > backup data as root access is required. Some say they can backup to an > internal card, and only then copy from that card to an external store. > > Why is backing up in Android apparently so complicated? Why can't I do > as simply as I would with Windows or Linux via USB (or Wi-Fi)? And I > haven't even looked at the issue of whether or not it is straightforward > to restore from a backup. The problem is that, on Windows, you can get access to all your user files in C:\Users\username so you can backup all the user state. On Android there are security protections in place so one app can't access another app's files. On Windows, if you have admin rights, you can access every file. On Android you need root for that, which is something the system is designed to not let you have, for the same security reasons. So if you don't have root, you have to rely on whatever backup mechanisms the system lets you have. That might be: 1 Individual apps 'export my data options' 2 Grabbing whatever parts of the filesystem a backup app is allowed to access 3 adb backup (unreliable) 4 Cloud backups For #2, Syncthing is a handy tool for syncing (parts of) the phone storage to another machine. But it doesn't get you data which is held by apps (eg in a database) rather than stored on your filesystem. Theo
[toc] | [prev] | [next] | [standalone]
| From | Adrian <bulleid@ku.gro.lioff> |
|---|---|
| Date | 2023-11-03 14:25 +0000 |
| Message-ID | <ZkgRnPE8KQRlFwmh@ku.gro.lloiff> |
| In reply to | #109508 |
In message <YIy*n2tuz@news.chiark.greenend.org.uk>, Theo <theom+news@chiark.greenend.org.uk> writes >The problem is that, on Windows, you can get access to all your user >files in C:\Users\username so you can backup all the user state. On >Android there are security protections in place so one app can't access >another app's files. On Windows, if you have admin rights, you can >access every file. On Android you need root for that, which is >something the system is designed to not let you have, for the same >security reasons. > Am I missing something here ? If I plug my Android phone (or tablet) into my PC using a USB lead, I can download data from it. That is generally how I copy off photos that I want to use elsewhere. So if I can do that for photos, what is to stop me downloading the rest of the data on the device onto a PC, or in other words, backing it up ? Adrian -- To Reply : replace "bulleid" with "adrian" - all mail to bulleid is rejected Sorry for the rigmarole, If I want spam, I'll go to the shops Every time someone says "I don't believe in trolls", another one dies.
[toc] | [prev] | [next] | [standalone]
| From | Andy Burns <usenet@andyburns.uk> |
|---|---|
| Date | 2023-11-03 14:38 +0000 |
| Message-ID | <kqkev3F42csU2@mid.individual.net> |
| In reply to | #109509 |
Adrian wrote: > If I plug my Android phone (or tablet) into my PC using a USB lead, I > can download data from it. That is generally how I copy off photos that > I want to use elsewhere. So if I can do that for photos, what is to > stop me downloading the rest of the data on the device onto a PC Because what you see on the PC when connected by USB are only the folders that the phone chooses to let you see, rather than the entire file structure.
[toc] | [prev] | [next] | [standalone]
| From | Frank Slootweg <this@ddress.is.invalid> |
|---|---|
| Date | 2023-11-03 16:38 +0000 |
| Message-ID | <ui3b6g.115k.1@ID-201911.user.individual.net> |
| In reply to | #109510 |
Andy Burns <usenet@andyburns.uk> wrote: > Adrian wrote: > > > If I plug my Android phone (or tablet) into my PC using a USB lead, I > > can download data from it. That is generally how I copy off photos that > > I want to use elsewhere. So if I can do that for photos, what is to > > stop me downloading the rest of the data on the device onto a PC > > Because what you see on the PC when connected by USB are only the > folders that the phone chooses to let you see, rather than the entire > file structure. That is true, but the USB/MTP connection to a Windows system lets you see *more* than is available to an app on the phone. For example with this connection, on Windows I can descend into \Internal Storage\Android\data\net.osmand.plus\files and see all my (.obf) OsmAnd+ maps. If I do the same on my phone with its (Samsung) 'My Files' app (or a similar app [1]), as soon as I try to descend into ...\data, the app says "Due to Android restrictions, the contents of this folder can only be shown on a computer." Note the nice hint to the computer! :-) So with a USB/MTP connection to a Windows system, you can 'backup' *more* of the Android filesystem, but it is rather cumbersome to use, because you can only use this connection in (Windows) File Explorer and only do *manual* copy-paste type operations. It's not a Windows drive - it has no drive letter -, so you can not use it with other utilities, not with 'DOS' (hence not with a .bat script), etc.. We Dutch call it (translated by Google Translate) "the law for the preservation of misery"! :-) c.q. :-( [1] For example the 'FX' app says '/!\ Access was denied.'.
[toc] | [prev] | [next] | [standalone]
| From | Andy Burns <usenet@andyburns.uk> |
|---|---|
| Date | 2023-11-03 17:34 +0000 |
| Message-ID | <kqkp89F5bduU1@mid.individual.net> |
| In reply to | #109513 |
Frank Slootweg wrote: > So with a USB/MTP connection to a Windows system, you can 'backup' > more of the Android filesystem, but it is rather cumbersome to use, > because you can only use this connection in (Windows) File Explorer and > only domanual copy-paste type operations. It's not a Windows drive - > it has no drive letter -, so you can not use it with other utilities, > not with 'DOS' (hence not with a .bat script), etc.. You can access the file explorer via the shell.application object within powershell (or vbscript/javascript if that's more your thing) and the phone shows up with a type of ssfDRIVES <https://blog.daiyanyingyu.uk/2018/03/20/powershell-mtp>
[toc] | [prev] | [next] | [standalone]
Page 5 of 6 — ← Prev page 1 2 3 4 [5] 6 Next page →
Back to top | Article view | comp.mobile.android
csiph-web