LWD

joined 2 years ago
[–] [email protected] 8 points 3 months ago

Israel demanded data related to nearly 700 push notifications as part of a single request.

Rookie numbers IMO. But why "nearly 700" - did Israel already know the quantity of notifications, or was that a number they arrived at with Apple's help?

according to the data, the U.S. made 99 requests for push token data related to 345 different push tokens, and received data in response to 65 of the requests between July and December 2023. The U.K. made 123 requests, about 128 tokens, and received data in response to 111...

These raw numbers are smaller but, based on my relative knowledge, scarier. I believe **tokens don't represent single notifications, they represent all notifications to a single app on your phone **.

So the US is asking for 3-4 apps' worth of notification data per request (person?), and get their way about two-thirds of the time. And I'd assume one token worth of data could contain hundreds, thousands, of notifications.

There's only one app I know about that only uses push notifications to alert apps of incoming messages (without injecting the notification content into the push notification), and that's Signal...

[–] [email protected] 1 points 3 months ago* (last edited 2 months ago)

deleted by creator

[–] [email protected] 3 points 3 months ago (3 children)

I guess I'll ask you the same question I ask Putinists: Do you actually have a problem with propagandists? You get to see Hotznplotzn's profile too. If you think there's a different conclusion, a rational person would draw from it, be my guest in elaborate.

It's also a very funny you would accuse me of being a Putin shill.

[–] [email protected] 3 points 3 months ago

I think so.

Some browsers for Android have blocked the abusive JavaScript in trackers. DuckDuckGo, for instance, was already blocking domains and IP addresses associated with the trackers, preventing the browser from sending any identifiers to Meta. The browser also blocked most of the domains associated with Yandex Metrica. After the researchers notified DuckDuckGo of the incomplete blacklist, developers added the missing addresses.

[–] [email protected] 0 points 3 months ago* (last edited 2 months ago) (6 children)

deleted by creator

[–] [email protected] 1 points 3 months ago* (last edited 2 months ago)

deleted by creator

[–] [email protected] 1 points 3 months ago

What this article doesn't mention is that the URL

https://register-with-gp.ht1.uk/

sn't a typical redirect, it actually acts as a landing page that ends up requiring another click.

That extra click takes you to

https://www.nhs.uk/service-search/find-a-gp

... Which is what, a dozen characters longer (and has an extra "www." that can probably be discarded)? The QR codes should work just about as well. Better, if you skip the redirect

[–] [email protected] 0 points 3 months ago (8 children)

OP's post history demonstrates an interest in only one thing. As one example, look at the way they edited this article's title.

Original title: "...involving Meta and Yandex..."

This post: "...involving Meta and Russia's Yandex..."

I continue to wonder if OP is interested in privacy, or is simply upset at the Russianness of this particular thing.

[–] [email protected] 12 points 3 months ago (1 children)

Correct me if I'm wrong, but I don't think this has anything to do with archive.today:

Incidentally, anyone who pays for the paid media content must also expect for user data to go to Russia:

«Until recently, Ringier sent - thanks to these cookies - the IP addresses of "Blick" readers...

This has to do with a non-Russian company inadvertently adding trackers that linked back to a Russian website. There is no inherent danger of archive.today collecting cookies from other websites if you browse to it.

If browsing to archive links is concerning, especially if it's the only available option, I would generally recommend a VPN, but ironically, VPNs seem to trigger CloudFlare (aka non-Russian) issues that prevent me from viewing media archived on this site

view more: ‹ prev next ›