GrapheneOS -- 1d nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqls4psr089gsp9hpd4as2srxqjc00d42d2ud4xug8w4eym0sl7c0s9cs6w x 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. reply [1 reply]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.
thread · root 05a3fc42…02bb · depth 2 · · selected 935995d9…de3a
thread
root 05a3fc42…02bb · depth 2 · · selected 935995d9…de3a
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.
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqls4psr089gsp9hpd4as2srxqjc00d42d2ud4xug8w4eym0sl7c0s9cs6wx You should figure out what's actually making the requests which are being identified that way. It could befrom web browsing where EasyList + EasyPrivacy don't block those because it would break functionality butanother list being used to evaluate the requests considers them trackers. In general, it's not going to considerthe most privacy invasive requests made to an app's own servers to be trackers because it's used for thefunctionality so it doesn't mean much at all.
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.
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqls4psr089gsp9hpd4as2srxqjc00d42d2ud4xug8w4eym0sl7c0s9cs6wx As an example, a bank's services are privacy invasive because they track all of your payments and everything else they can see. They often provide a lot of the data to third parties including selling it. Whether or not their app uses client side analytics and telemetry connecting to a few domains dedicated to that which are considered trackers doesn't matter much. It's the difference between extremely privacy invasive vs. surface level things which tend to not matter much.