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 : robin_listas (at) *nospam* es.invalid (Carlos E.R.)
Groupes : comp.mobile.android
Date : 14. Jun 2025, 22:48:24
Autres entêtes
Message-ID : <8a71ilxjqj.ln2@Telcontar.valinor>
References : 1 2 3 4 5 6
User-Agent : Mozilla Thunderbird
On 2025-06-14 21:50, Marion wrote:
On Sat, 14 Jun 2025 19:57:41 +0200, Carlos E.R. wrote :
 
I'm sorry to say that about everybody in Spain uses WhatsApp, even
businesses. Like the Bank. It is what it is.
 Please ignore Joerg. He feels compelled to ROTFWL on every thread.
He has nothing to add. He's a worthless despicable human being.
 Now... as for your point - I agree with you since I agree with anyone who
makes a sensible logical statement.
 Even I use WhatsApp. And I care about privacy.
So I'm happy you (and Richmond) brought this up.
 I don't understand the implications, but I can tell others that I use
WhatsApp for two sensible reasons, one of which is that it's what all my
relatives use on their mobile phones in Germany. So it's what works since
calling them would cost me an arm and a leg with international prices.
 The other reason is the parents of both my great grandchildren use Apple
devices, so everything is blurry without using something like WhatsApp.
 Sure, another messenger would work, but so does WhatsApp.
Caveat in the sig.
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.
--
Cheers, Carlos.

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