{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiceeiew3ohe6nzv2cfkkkx665fzh6ppzit5sr32otvqzkjof3q3aa",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3mkxzmackoes2"
  },
  "path": "/t/suggestion-to-add-clearer-caveats-to-privacy-tool-recommendations/37591#post_15",
  "publishedAt": "2026-05-03T19:43:35.000Z",
  "site": "https://discuss.privacyguides.net",
  "textContent": "phnx:\n\n> Surely you are above putting words into my mouth. I am saying that the fact that a paid service requires you to continue to pay the subscription to maintain access to the service is not exactly rocket science.\n\nBut that’s not my point with this post. I’m saying that on PG, when recommending something like using email aliases to someone new to them, it is helpful to point out what the long-term implications could be.\n\nSimilarly, with encrypted email, it might be worth warning someone in advance that the search functionality is nowhere near what someone might be used to on Gmail.\n\nThe idea is to give a heads up to people new to privacy tools about some of the implications of their use that they won’t know about, and many of us do, from our experience using them.\n\nI don’t really agree with the Proton thread OP’s gripes about losing features that are part of a paying service when he stopped paying, but reading through that thread made me realise there is a broader issue about recommending privacy tools.",
  "title": "Suggestion to add clearer caveats to privacy tool recommendations"
}