Plain Text Nostr

<-- back to main feed

thread · root fb56aa96…4e2e · depth 2 · · selected c09f8bdf…d7fe

thread

root fb56aa96…4e2e · depth 2 · · selected c09f8bdf…d7fe

GrapheneOS -- 1d [root] 
|    nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqls4psr089gsp9hpd4as2srxqjc00d42d2ud4xug8w4eym0sl7c0s9cs6w
|    x 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.
|    reply [1 reply]
GrapheneOS -- 1d
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqls4psr089gsp9hpd4as2srxqjc00d42d2ud4xug8w4eym0sl7c0s9cs6w
x As another example, consider a camera app with filters which uploads every picture and video to their servers
to do the processing on their cloud vs. one which does everything locally and doesn't send user data anywhere
but includes a crash reporting system and basic analytics to know how much features get used. The one with the
crash reporting system and analytics will be classified as having 2 'trackers' vs. the very privacy invasive one
sending off your sensitive data with 0.
reply

Write a post

Sign in with a signing-capable method to publish.