{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreic6xtfsweef7l5coozaabynwgp3pie57qdllbjcfvzor7momtnp4q",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mkxi7av2tdc2"
  },
  "path": "/viewtopic.php?t=33410&p=273275#p273275",
  "publishedAt": "2026-05-03T15:28:04.000Z",
  "site": "http://forum.palemoon.org",
  "tags": [
    "https://blog.mozilla.org/addons/2021/05 ... v3-update/"
  ],
  "textContent": "> Firefox getting built-in content blocking could mean Mozilla is going to give up on Manifest v2 extension support and cave in to Google's Manifest v3, which does not allow full content blocking extensions such as uBlock's regular version.\n>\n> Which would be an ironic twist - Pale Moon and Basilisk would be the only remaining browsers with the ability to run unlimited content blocking extensions.\n\nMy thoughts exactly!\n\nEspecially with how it's worded here: https://blog.mozilla.org/addons/2021/05 ... v3-update/\n\n\nCODE:\n\n\n    We will support blocking webRequest until there’s a better solution which covers all use cases we consider importantWe have not yet set a deprecation date for Manifest v2 but expect it to be supported for at least one year after Manifest v3 becomes stable in the release channel.\n\n* * *",
  "title": "General Discussion • Re: Firefox 149 bundles content-blocking engine adblock-rust",
  "updatedAt": "2026-05-03T15:28:04.000Z"
}