{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreie7f56c4q6oaljy4py2mi6cfznei2aavyfleibymr2jcf3uexxlhq",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3mkxswft5ti42"
  },
  "path": "/t/mv2-3-adblocker-use-instead-of-dns-filtering/37559#post_13",
  "publishedAt": "2026-05-03T17:54:56.000Z",
  "site": "https://discuss.privacyguides.net",
  "tags": [
    "https://www.eff.org/deeplinks/2021/12/googles-manifest-v3-still-hurts-privacy-security-innovation"
  ],
  "textContent": "PoPETS researchers from Goethe University found no statistical reduction in ad-blocking effectiveness for MV3 compared to their MV2 counterparts.\n\nRecalling years back when MV3 was introduced and the EFF was saying this:\n\nhttps://www.eff.org/deeplinks/2021/12/googles-manifest-v3-still-hurts-privacy-security-innovation\n\nand I guess the overall take today is there were some API changes with MV3 imposing rule caps, and prohibiting extensions from remotely loading code or filters requiring changes to be approved by the CWS. It’s made it less effective in that blocking is still functional but not as unrestricted like MV2 was.\n\nThis is why I asked the question and brought up this discussion.",
  "title": "MV2/3 adblocker use instead of DNS filtering"
}