{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreigegpp7heyjw7dbbq7aw766tmgdrbpdcgoxxujm5jwugtepd6rpwa",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3mi32p4jmfvc2"
  },
  "path": "/t/redefining-location-privacy-new-tools-and-improvements-for-android-17/36615#post_2",
  "publishedAt": "2026-03-27T20:59:54.000Z",
  "site": "https://discuss.privacyguides.net",
  "textContent": "As much as I hope that this feature will improve privacy, I must say I’m rather pessimistic about its adoption.\n\nI’m thinking it’ll have much the same fate as the Precise / Approximate location split. All the (closed-source commercial) apps that I want to use which demand my location simply refuse to work if I give them only approximate location. They all demand precise location even though they don’t actually need it for anything; they just want it to collect more data (in my opinion).\n\nI’m thinking this feature will be the same. Commercial apps _could_ use the momentary location signal, but that would rob them of their precious location data, and we of course can’t have that! I believe they’ll just request continuous location data regardless of this feature and come up with excuses as to why it’s “necessary” for their apps to work.\n\nTime will tell, I guess. I hope I’m wrong.",
  "title": "Redefining Location Privacy: New Tools and Improvements for Android 17"
}