{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibmgfrpct5s4hn6znrtjc6gmedrk22klgajaccbikcbhqwdwndyve",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3mfakplwkd532"
  },
  "path": "/t/wish-for-clean-brave-browser/34448?page=4#post_79",
  "publishedAt": "2026-02-19T21:40:16.000Z",
  "site": "https://discuss.privacyguides.net",
  "tags": [
    "(click for more details)"
  ],
  "textContent": "NoWarEarthling:\n\n> This is cool but very strict, what if one need Speedreader or something else?\n\nJust remove the lines you don’t want to use. Afaik, there is no issue with speedreader (personally I leave it enabled). I think that the people that add it to their .json files are either doing so because they copied someone elses list, or because they consider a reader mode to be superflous and disable it as part of ‘debloating’ not because of a privacy reason for doing so. Below I ~~crossed out~~ the lines I would personally exclude from the list unless I had a specific reason:\n\nlist (click for more details)\n\n> Is this mitigated by PG’s recommended configuration?\n\nNot sure about PG’s recommended config, but (like most of these marketing/SEO ‘comparisons’ most of the boxes could be checked for safari with a few minutes of configuration, an adblocker, or more neutrally worded categories. (And some of the bullet points are just marketing, without much to actually mitigate). As a rule, I try to never place any weight on how a company _measures itself against it’s competition, in it’s own marketing materials_ and this is especially true of a project like Brave that always seems more focused on trying to attack competitors, than they are focused on trying to attract mainstream users, and expand the privacy space.",
  "title": "Wish for \"clean\" Brave Browser"
}