{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreigxk66s4niekr4zsq6nmi3hjgm7ern53f3hb2sa2qgocmzuul6zom",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3miunk23w2ej2"
  },
  "path": "/viewtopic.php?t=33298&p=271945#p271945",
  "publishedAt": "2026-04-06T21:41:57.000Z",
  "site": "http://forum.palemoon.org",
  "tags": [
    "this section"
  ],
  "textContent": "> Original GreaseMonkey for PM refuses to check for user script updates if you have auto-updating of extensions in Pale Moon disabled, even if triggered by the user, in which case extensions will be checked, but user scripts will be skipped. I just remembered I deleted this section in the copy of GreaseMonkey I've been using for the last couple of years.\n>\n> I didn't study the meaning of aForced parameter, so just deleting all of these may not be the most correct approach.\n>\n> Edit: I see this value is false on manual check, so I guess it was right to delete all of it.\n\nInteresting, I haven't seen that before. I'll be checking onto it and see what would be the approach with it. I'm generally making the extension behave how Violentmonkey on Chrome behaves.\n\n\n...I just realized that I'm probably going to be tackling issues that a lot of people did not report on the old fork of greasemonkey. I legit checked the \"issues\" tab on the old fork's GitHub page to gather all the issues, then fix them and ship my extension fork to the community.\n\nOh well, lay them all on me.\n\n* * *",
  "title": "Add-ons • Re: Working on a Greasemonkey fork for Pale Moon",
  "updatedAt": "2026-04-06T21:41:57.000Z"
}