GrapheneOS -- 1d nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqls4psr089gsp9hpd4as2srxqjc00d42d2ud4xug8w4eym0sl7c0s9cs6w x The number of connections to domains classified as being used for trackers but a given list means very little. The most privacy invasive behaviors by apps are usually done via their own servers. It's primarily the unimportant surface level privacy issues which are tied to those kinds of domains commonly listed as being used for tracking. Domains aren't neatly separated into ones used for tracking and everything else. We don't it's a good way to evaluate privacy or to compare. reply [1 reply]nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqls4psr089gsp9hpd4as2srxqjc00d42d2ud4xug8w4eym0sl7c0s9cs6wx The number of connections to domains classified as being used for trackers but a given list means very little. The most privacy invasive behaviors by apps are usually done via their own servers. It's primarily the unimportant surface level privacy issues which are tied to those kinds of domains commonly listed as being used for tracking. Domains aren't neatly separated into ones used for tracking and everything else. We don't it's a good way to evaluate privacy or to compare.
thread · root d8b1a613…74c5 · depth 2 · · selected 05a3fc42…02bb
thread
root d8b1a613…74c5 · depth 2 · · selected 05a3fc42…02bb
Currently monitoring ad tracking requests on my iPhone 13 and my new-to-me Pixel runningnostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqtva8g98fx0fks0pt38vr75tv02t30qd5ev7n5v7fcpl6t44hf7kqzp8d0p with mostly open-source apps and WOW13 requests to 3 trackers on the Graphene phone this morning, and it's the one I've been actively using.122 on the iPhone that's mostly been sitting on the table.
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqls4psr089gsp9hpd4as2srxqjc00d42d2ud4xug8w4eym0sl7c0s9cs6wx The number of connections to domains classified as being used for trackers but a given list means very little.The most privacy invasive behaviors by apps are usually done via their own servers. It's primarily theunimportant surface level privacy issues which are tied to those kinds of domains commonly listed as being usedfor tracking. Domains aren't neatly separated into ones used for tracking and everything else. We don't it's agood way to evaluate privacy or to compare.
Currently monitoring ad tracking requests on my iPhone 13 and my new-to-me Pixel running nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqtva8g98fx0fks0pt38vr75tv02t30qd5ev7n5v7fcpl6t44hf7kqzp8d0p with mostly open-source apps and WOW
13 requests to 3 trackers on the Graphene phone this morning, and it's the one I've been actively using.
122 on the iPhone that's mostly been sitting on the table.
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqls4psr089gsp9hpd4as2srxqjc00d42d2ud4xug8w4eym0sl7c0s9cs6wx You should figure out what's actually making the requests which are being identified that way. It could be from web browsing where EasyList + EasyPrivacy don't block those because it would break functionality but another list being used to evaluate the requests considers them trackers. In general, it's not going to consider the most privacy invasive requests made to an app's own servers to be trackers because it's used for the functionality so it doesn't mean much at all.