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 : this (at) *nospam* ddress.is.invalid (Frank Slootweg)
Groupes : comp.mobile.android
Date : 22. Jun 2025, 20:20:57
Autres entêtes
Organisation : NOYB
Message-ID : <1039s2c.n7o.1@ID-201911.user.individual.net>
References : 1 2 3 4 5 6 7 8 9 10
User-Agent : tin/1.6.2-20030910 ("Pabbay") (UNIX) (CYGWIN_NT-10.0-WOW/2.8.0(0.309/5/3) (i686)) Hamster/2.0.2.2
Carlos E.R. <robin_listas@es.invalid> wrote:
On 2025-06-22 12:15, Frank Slootweg wrote:
Richmond <dnomhcir@gmx.com> wrote:
[...]
 
The point is, whatsapp is closed source, it could be doing other things
beside sending your messages. It could be snooping on other things and
sending that data elsewhere. Meta has now demonstrated it doesn't worry
too much about the law. Do you want that software on your phone? or are
you going to wait for the next thing to be discovered?
 
   I just was in the UK for two weeks and the TV broadcasts are
splattered with commercials from WhatsApp, saying that your messages are
safe and that no-one, including WhatsApp can read them.
 
   Of course, commercials 'lie' all the time, but these would open
WhatsApp to some serious legal action (and fines), so until proven
otherwise, we'll should assume that WhatsApp is *not* lying.
 
I understand they can read them with a court order. Somehow. Maybe it
means they have to impound the phones first.
 
There are some corruption cases in the media now in Spain, and their WA
conversations are being displayed on TV all the time.

  That could well be cases of unencrypted WhatsApp *backup*, on the
*device* (i.e. private unless/until hacked) or/and on the *user*'s
Google Drive (same).

  By default, WhatsApp *backup* is unencrypted, but that doesn't mean
that others - than the 'owner'/user of the chats - or WhatsApp can read
them.

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