Re: “Localhost tracking” explained. It could cost Meta 32 billion.

Liste des GroupesRevenir à m android 
Sujet : Re: “Localhost tracking” explained. It could cost Meta 32 billion.
De : marion (at) *nospam* facts.com (Marion)
Groupes : comp.mobile.android
Date : 15. Jun 2025, 04:42:58
Autres entêtes
Organisation : BWH Usenet Archive (https://usenet.blueworldhosting.com)
Message-ID : <102lfg1$16fr$1@nnrp.usenet.blueworldhosting.com>
References : 1 2 3 4 5 6 7
User-Agent : ForteAgent/8.00.32.1272
On Sat, 14 Jun 2025 23:48:24 +0200, Carlos E.R. wrote :


That WhatsApp has been affected by this security leak is still unclear.
The author of the article I posted doesn't know. Facebook and Instagram
yes, certainly. But WhatsApp promises encrypted communications are kept
private, end to end encryption. Listening to them would be a major
breach of trust (except with a court order). This is not the same with
Facebook, which is intended to publish things.

Thanks Carlos for summarizing as I am also unclear what the privacy
implications are. I don't use FB or Instagram but my kids and grandkids use
Snapchat and Telegram.

Let's hope the courts handle this efficiently.

Thanks for keeping us informed as I was blissfully unaware of this issue.

I saw Richmond's response just before sending this where the problem is
*replacing* WhatsApp where it's not so hard to get my family to use, oh,
say, Google Voice, but is that any safer? I use Google Voice but only on
the iPad (because Google adds an account on the Android phone if you use GV
on Android but Google can't do that on an iOS device - heh heh heh).

The problem is the Europeans all use WhatsApp daily.

To Richmond's suggestion, how do I get the relatives in Germany to use
something else?

Date Sujet#  Auteur
13 Jun 25 * “Localhost tracking” explained. It could cost Meta 32 billion.42Carlos E.R.
13 Jun 25 +* Re: “Localhost tracking” explained. It could cost Meta 32 billion.3Andy Burns
13 Jun 25 i`* Re: “Localhost tracking” explained. It could cost Meta 32 billion.2Carlos E.R.
13 Jun 25 i `- Re: “Localhost tracking” explained. It could cost Meta 32 billion.1Carlos E.R.
14 Jun 25 `* Re: “Localhost tracking” explained. It could cost Meta 32 billion.38VanguardLH
14 Jun 25  +* Re: “Localhost tracking” explained. It could cost Meta 32 billion.36Carlos E.R.
14 Jun 25  i+* Re: “Localhost tracking” explained. It could cost Meta 32 billion.10VanguardLH
14 Jun 25  ii+* Re: “Localhost tracking” explained. It could cost Meta 32 billion.6Jörg Lorenz
14 Jun 25  iii`* Re: “Localhost tracking” explained. It could cost Meta 32 billion.5Andy Burns
14 Jun 25  iii +* Re: “Localhost tracking” explained. It could cost Meta 32 billion.2Java Jive
14 Jun 25  iii i`- Re: “Localhost tracking” explained. It could cost Meta 32 billion.1Jörg Lorenz
14 Jun 25  iii +- Re: “Localhost tracking” explained. It could cost Meta 32 billion.1Jörg Lorenz
14 Jun 25  iii `- Re: “Localhost tracking” explained. It could cost Meta 32 billion.1Arno Welzel
14 Jun 25  ii`* Re: “Localhost tracking” explained. It could cost Meta 32 billion.3Carlos E.R.
14 Jun 25  ii `* Re: “Localhost tracking” explained. It could cost Meta 32 billion.2Jörg Lorenz
14 Jun 25  ii  `- Re: “Localhost tracking” explained. It could cost Meta 32 billion.1Carlos E.R.
14 Jun 25  i`* Re: “Localhost tracking” explained. It could cost Meta 32 billion.25Jörg Lorenz
14 Jun 25  i `* Re: “Localhost tracking” explained. It could cost Meta 32 billion.24Carlos E.R.
14 Jun 25  i  +* Re: “Localhost tracking” explained. It could cost Meta 32 billion.14Marion
14 Jun 25  i  i`* Re: “Localhost tracking” explained. It could cost Meta 32 billion.13Carlos E.R.
15 Jun 25  i  i +* Re: “Localhost tracking” explained. It could cost Meta 32 billion.10Richmond
15 Jun 25  i  i i+- Re: “Localhost tracking” explained. It could cost Meta 32 billion.1Bob Henson
17 Jun 25  i  i i+* Re: “Localhost tracking” explained. It could cost Meta 32 billion.3Carlos E.R.
18 Jun 25  i  i ii`* Re: “Localhost tracking” explained. It could cost Meta 32 billion.2Richmond
18 Jun 25  i  i ii `- Re: “Localhost tracking” explained. It could cost Meta 32 billion.1Carlos E.R.
22 Jun 25  i  i i`* Re: ?Localhost tracking? explained. It could cost Meta 32 billion.5Frank Slootweg
22 Jun 25  i  i i +* Re: ?Localhost tracking? explained. It could cost Meta 32 billion.3Carlos E.R.
22 Jun 25  i  i i i`* Re: ?Localhost tracking? explained. It could cost Meta 32 billion.2Frank Slootweg
22 Jun 25  i  i i i `- Re: ?Localhost tracking? explained. It could cost Meta 32 billion.1Carlos E.R.
22 Jun 25  i  i i `- Re: ?Localhost tracking? explained. It could cost Meta 32 billion.1Richmond
15 Jun 25  i  i `* Re: “Localhost tracking” explained. It could cost Meta 32 billion.2Marion
17 Jun 25  i  i  `- Re: “Localhost tracking” explained. It could cost Meta 32 billion.1Carlos E.R.
14 Jun 25  i  +* Re: “Localhost tracking” explained. It could cost Meta 32 billion.5Richmond
14 Jun 25  i  i+* Re: “Localhost tracking” explained. It could cost Meta 32 billion.2Jörg Lorenz
14 Jun 25  i  ii`- Re: “Localhost tracking” explained. It could cost Meta 32 billion.1Richmond
15 Jun 25  i  i`* Re: “Localhost tracking” explained. It could cost Meta 32 billion.2Marion
15 Jun 25  i  i `- Re: “Localhost tracking” explained. It could cost Meta 32 billion.1Richmond
14 Jun 25  i  `* Re: “Localhost tracking” explained. It could cost Meta 32 billion.4Jörg Lorenz
14 Jun 25  i   `* Re: “Localhost tracking” explained. It could cost Meta 32 billion.3Carlos E.R.
15 Jun 25  i    `* Re: “Localhost tracking” explained. It could cost Meta 32 billion.2Jörg Lorenz
17 Jun 25  i     `- Re: “Localhost tracking” explained. It could cost Meta 32 billion.1Carlos E.R.
14 Jun 25  `- Re: “Localhost tracking” explained. It could cost Meta 32 billion.1Arno Welzel

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal