{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifvarjpz4f4xtbtppazvsc4yhcxxn33dd6trablomqjnatm4fi6ey",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mltg5rkzx632"
  },
  "path": "/viewtopic.php?t=33298&p=274009#p274009",
  "publishedAt": "2026-05-14T16:43:46.000Z",
  "site": "http://forum.palemoon.org",
  "tags": [
    "https://forum.palemoon.org/viewtopic.php?f=70&t=33408#p273639"
  ],
  "textContent": "> Old Greasemonkey for PM can get around site's CSP, the UXP version apparently cannot.\n>\n> See https://forum.palemoon.org/viewtopic.php?f=70&t=33408#p273639\n>\n> A common issue with extensions from my experience.\n\nI had the idea of the UXP version behave more like Violentmonkey, when it comes to tempering with a site's CSP (especially the ones who also use 'Trusted Types'), but then I realized that, despite how Violentmonkey has a lot of advantages, I don't also have to have their limitations into my codebase. I'll apply this feature on the next version of 3.7.0 and release a beta version for you and everyone else to test it out, instead of being prompted to automatically (or manually) update your extension to it.\n\n* * *",
  "title": "Add-ons • Re: Working on a Greasemonkey fork for Pale Moon",
  "updatedAt": "2026-05-14T16:43:46.000Z"
}