{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidznmeq2jk6tj2iwxvu33ngls36vgwzxhqbuuznnuish26nnsmtii",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3mnair3rc4n22"
  },
  "path": "/t/my-recent-changes-towards-more-privacy-friendlier-life/38166?page=2#post_28",
  "publishedAt": "2026-06-01T16:08:32.000Z",
  "site": "https://discuss.privacyguides.net",
  "textContent": "FranklyFlawless:\n\n> because upstream changes the rules and the development work required afterwards is unscalable against them.\n\nIt is a cat & mouse game.\n\nThis is the pain that frontend developers face mainly. If it is blocked by original service.\n\nMany instances will shut down. It will trigger a chain of events and discourage public hosting.\n\nSay Bibliogram one of the well know frontends for Instagram was blocked by meta from scraping since they can’t profile users and at the same they sent a cease and desist letter to the project too. Woth court battles. IIRC\n\nThen they shutdown. Now there is one in Libredirect. Working as of now. It is also matter of time.\n\nFor Libredirect it is just a matter of domain change. But front-end devs and instance maintainers are the real saviors of privacy in digital space. Donate to them, if you can, than us. Many instances shut down due to increasing costs in VPS.",
  "title": "My recent changes towards more privacy friendlier life"
}