{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreif47tzfmtzjdxrx2nbqdq6ojuh5b5mozm55xu5jpl3iqmi43atjjy",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3mowgqj4e3ae2"
  },
  "path": "/t/nearly-family-location-sharing-without-the-data-harvesting/37803?page=2#post_32",
  "publishedAt": "2026-06-23T02:51:51.000Z",
  "site": "https://discuss.privacyguides.net",
  "textContent": "If there are true E2EE (A)GPL clients offering the same thing, then I would largely refuse to use this service until it catches up to the others.\n\nAs the saying goes, E2EE can me enancryption between client and server, so I think we need a big bold preface saying transport encryption is a bare bones expectations, and E2EE between client to client where a server cannot read privacy data is a requirement for a privacy preserving solution. When we say E2EE, we colloquially mean client to client encryption.\n\nIt’s one thing to not encrypt say an email, but the whole point is to encrypt location data. It’s an architecture tradeoff if you aren’t thread modeling as to what is required, and that is to distrust the server.",
  "title": "Nearly – Family Location Sharing Without the Data Harvesting"
}