Groups | Search | Server Info | Login | Register
Groups > comp.mobile.android > #148851
| From | Richmond <dnomhcir@gmx.com> |
|---|---|
| Newsgroups | comp.mobile.android |
| Subject | Re: “Localhost tracking” explained. It could cost Meta 32 billion. |
| Date | 2025-06-14 20:51 +0100 |
| Organization | Frantic |
| Message-ID | <86zfeagl07.fsf@example.com> (permalink) |
| References | <eb8uhlxstr.ln2@Telcontar.valinor> <1om16wwki1x2j.dlg@v.nguard.lh> <da80ilxkfh.ln2@Telcontar.valinor> <102k0s5$pqa6$1@solani.org> <lpp0ilxs16.ln2@Telcontar.valinor> |
"Carlos E.R." <robin_listas@es.invalid> writes: > On 2025-06-14 16:27, Jörg Lorenz wrote: >> On 14.06.25 14:59, Carlos E.R. wrote: >>> On 2025-06-14 08:03, VanguardLH wrote: >>>> "Carlos E.R." <robin_listas@es.invalid> wrote: >>> >>> ... >>> >>>> Be aware that disabling the WebRTC API can break some web sites. >>>> Probably best on mobile platforms to use a task killer where >>>> Facebook, Instagram, and other socially needy apps (e.g., WhatsApp) >>>> get unloaded instead of left running in the background when you >>>> "exit" the app. >>> >>> It is not practical to actually stop WhatsApp, because then you do >>> not get new messages. >> Simply the best that can happen. There are >>> a lot of better >> messengers. >> No mercy for the idiots that use >>> Zuckerberg-crap. > > I'm sorry to say that about everybody in Spain uses WhatsApp, even > businesses. Like the Bank. It is what it is. Many organisations use facebook too, even churches. All we can do is complain to them that they are not checking out the ethics of these companies. They know they have us over a barrel. It's hard to argue with free calls when the landline can cost 10p per minute, or a free website.
Back to comp.mobile.android | Previous | Next — Previous in thread | Next in thread | Find similar
“Localhost tracking” explained. It could cost Meta 32 billion. "Carlos E.R." <robin_listas@es.invalid> - 2025-06-13 20:47 +0200
Re: “Localhost tracking” explained. It could cost Meta 32 billion. Andy Burns <usenet@andyburns.uk> - 2025-06-13 20:34 +0100
Re: “Localhost tracking” explained. It could cost Meta 32 billion. "Carlos E.R." <robin_listas@es.invalid> - 2025-06-13 23:07 +0200
Re: “Localhost tracking” explained. It could cost Meta 32 billion. "Carlos E.R." <robin_listas@es.invalid> - 2025-06-13 23:11 +0200
Re: “Localhost tracking” explained. It could cost Meta 32 billion. VanguardLH <V@nguard.LH> - 2025-06-14 01:03 -0500
Re: “Localhost tracking” explained. It could cost Meta 32 billion. "Carlos E.R." <robin_listas@es.invalid> - 2025-06-14 14:59 +0200
Re: “Localhost tracking” explained. It could cost Meta 32 billion. VanguardLH <V@nguard.LH> - 2025-06-14 09:08 -0500
Re: “Localhost tracking” explained. It could cost Meta 32 billion. Jörg Lorenz <hugybear@gmx.net> - 2025-06-14 16:28 +0200
Re: “Localhost tracking” explained. It could cost Meta 32 billion. Andy Burns <usenet@andyburns.uk> - 2025-06-14 16:14 +0100
Re: “Localhost tracking” explained. It could cost Meta 32 billion. Java Jive <java@evij.com.invalid> - 2025-06-14 17:01 +0100
Re: “Localhost tracking” explained. It could cost Meta 32 billion. Jörg Lorenz <hugybear@gmx.net> - 2025-06-14 19:35 +0200
Re: “Localhost tracking” explained. It could cost Meta 32 billion. Jörg Lorenz <hugybear@gmx.net> - 2025-06-14 19:29 +0200
Re: “Localhost tracking” explained. It could cost Meta 32 billion. Arno Welzel <usenet@arnowelzel.de> - 2025-06-15 00:34 +0200
Re: “Localhost tracking” explained. It could cost Meta 32 billion. "Carlos E.R." <robin_listas@es.invalid> - 2025-06-14 19:55 +0200
Re: “Localhost tracking” explained. It could cost Meta 32 billion. Jörg Lorenz <hugybear@gmx.net> - 2025-06-14 22:28 +0200
Re: “Localhost tracking” explained. It could cost Meta 32 billion. "Carlos E.R." <robin_listas@es.invalid> - 2025-06-14 23:41 +0200
Re: “Localhost tracking” explained. It could cost Meta 32 billion. Jörg Lorenz <hugybear@gmx.net> - 2025-06-14 16:27 +0200
Re: “Localhost tracking” explained. It could cost Meta 32 billion. "Carlos E.R." <robin_listas@es.invalid> - 2025-06-14 19:57 +0200
Re: “Localhost tracking” explained. It could cost Meta 32 billion. Marion <marion@facts.com> - 2025-06-14 19:50 +0000
Re: “Localhost tracking” explained. It could cost Meta 32 billion. "Carlos E.R." <robin_listas@es.invalid> - 2025-06-14 23:48 +0200
Re: “Localhost tracking” explained. It could cost Meta 32 billion. Richmond <dnomhcir@gmx.com> - 2025-06-15 00:15 +0100
Re: “Localhost tracking” explained. It could cost Meta 32 billion. Bob Henson <bob.henson@outlook.com> - 2025-06-15 09:05 +0100
Re: “Localhost tracking” explained. It could cost Meta 32 billion. "Carlos E.R." <robin_listas@es.invalid> - 2025-06-17 01:40 +0200
Re: “Localhost tracking” explained. It could cost Meta 32 billion. Richmond <dnomhcir@gmx.com> - 2025-06-18 11:43 +0100
Re: “Localhost tracking” explained. It could cost Meta 32 billion. "Carlos E.R." <robin_listas@es.invalid> - 2025-06-18 14:19 +0200
Re: ?Localhost tracking? explained. It could cost Meta 32 billion. Frank Slootweg <this@ddress.is.invalid> - 2025-06-22 10:15 +0000
Re: ?Localhost tracking? explained. It could cost Meta 32 billion. "Carlos E.R." <robin_listas@es.invalid> - 2025-06-22 13:30 +0200
Re: ?Localhost tracking? explained. It could cost Meta 32 billion. Frank Slootweg <this@ddress.is.invalid> - 2025-06-22 19:20 +0000
Re: ?Localhost tracking? explained. It could cost Meta 32 billion. "Carlos E.R." <robin_listas@es.invalid> - 2025-06-22 21:40 +0200
Re: ?Localhost tracking? explained. It could cost Meta 32 billion. Richmond <dnomhcir@gmx.com> - 2025-06-22 23:17 +0100
Re: “Localhost tracking” explained. It could cost Meta 32 billion. Marion <marion@facts.com> - 2025-06-15 03:42 +0000
Re: “Localhost tracking” explained. It could cost Meta 32 billion. "Carlos E.R." <robin_listas@es.invalid> - 2025-06-17 02:00 +0200
Re: ⤽Localhost trackingâ€? explained. It could cost Meta 32 billion. Joerg Walther <joerg.walther@magenta.de> - 2025-06-15 11:45 +0200
Re: “Localhost tracking” explained. It could cost Meta 32 billion. Richmond <dnomhcir@gmx.com> - 2025-06-14 20:51 +0100
Re: “Localhost tracking” explained. It could cost Meta 32 billion. Jörg Lorenz <hugybear@gmx.net> - 2025-06-14 22:34 +0200
Re: “Localhost tracking” explained. It could cost Meta 32 billion. Richmond <dnomhcir@gmx.com> - 2025-06-14 21:45 +0100
Re: “Localhost tracking” explained. It could cost Meta 32 billion. Marion <marion@facts.com> - 2025-06-15 03:46 +0000
Re: “Localhost tracking” explained. It could cost Meta 32 billion. Richmond <dnomhcir@gmx.com> - 2025-06-15 09:49 +0100
Re: “Localhost tracking” explained. It could cost Meta 32 billion. Jörg Lorenz <hugybear@gmx.net> - 2025-06-14 22:29 +0200
Re: “Localhost tracking” explained. It could cost Meta 32 billion. "Carlos E.R." <robin_listas@es.invalid> - 2025-06-14 23:43 +0200
Re: “Localhost tracking” explained. It could cost Meta 32 billion. Jörg Lorenz <hugybear@gmx.net> - 2025-06-15 07:10 +0200
Re: “Localhost tracking” explained. It could cost Meta 32 billion. "Carlos E.R." <robin_listas@es.invalid> - 2025-06-17 01:51 +0200
Re: “Localhost tracking” explained. It could cost Meta 32 billion. Arno Welzel <usenet@arnowelzel.de> - 2025-06-15 00:32 +0200
csiph-web