| Deutsch English Français Italiano |
|
<a8mlalxpqt.ln2@Telcontar.valinor> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!news.mixmin.net!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: "Carlos E.R." <robin_listas@es.invalid> Newsgroups: comp.mobile.android Subject: Re: How Google tracks Android device users before they've even opened an app Date: Mon, 17 Mar 2025 14:55:54 +0100 Lines: 34 Message-ID: <a8mlalxpqt.ln2@Telcontar.valinor> References: <80c93cc2ac209e7015ef716663a6761e@dizum.com> <485a6182afb819f8920f7b4ceb7f0469297262df@i2pn2.org> <t6BBP.524317$2zn8.514877@fx15.iad> <vr73k4$f6t$1@nnrp.usenet.blueworldhosting.com> <vr74he$1i5s$1@nnrp.usenet.blueworldhosting.com> <vr77g6$2c0vg$1@dont-email.me> <m7flalx78i.ln2@Telcontar.valinor> <vr980n$3lpsc$1@dont-email.me> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Trace: individual.net nZ6B3kfVMhafIRxMNo9JRgJ6QZtI5yy8lCfyKTrKQE7AoRZG31 X-Orig-Path: Telcontar.valinor!not-for-mail Cancel-Lock: sha1:JwoDOSo+X27alaEDDpHfWvNseRE= sha256:yhv8TmJKB3fB3P3q0AxXbCKVIeyCmA1pe7FZn9KlHSw= User-Agent: Mozilla Thunderbird Content-Language: es-ES, en-CA In-Reply-To: <vr980n$3lpsc$1@dont-email.me> Bytes: 2690 On 2025-03-17 14:27, Jeff Layman wrote: > On 17/03/2025 11:56, Carlos E.R. wrote: >> On 2025-03-16 20:06, Jeff Layman wrote: >> >>> You can have a /greater/ degree of privacy by following your >>> instructions noted in the previous thread in relation to a Google >>> account and the DSID cookie. But "privacy" isn't a term to be assumed >>> where Android is concerned. There's an interesting article at <https:// >>> www.forbes.com/sites/zakdoffman/2025/03/13/googles-android-decision-bad- >>> news-for-all-samsung-pixel-users/>. (*** see below) >> >> ... >> >>> (*** NB - scrolling down the article webpage results in a message: >>> "Application error: a client-side exception has occurred (see the >>> browser console for more information)". The browser page is then lost. I >>> got round this by turning off my Wi-Fi immediately the page had loaded. >>> The whole page could then be read by scrolling down) >> >> Confirm (firefox on Linux) >> >> You can bypass that by loading the page, and then on UBlock I click >> "disable javascript". I can then page down to the end. > > I didn't have the time yesterday to see what was going on with that > page, but reckoned breaking the connection to the mothership might solve > the issue. I tend to use the "Javascript Switcher" extension - it's a > bit easier than going through uBlock as it's a single click to disable/ > enable Javascript. It is also a single click on uBlock. -- Cheers, Carlos.