{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreie4ohavd2c5jkz32nitlq3tl4f2ag2i2ljr27fjqc4qx6hswmnwta",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3moqodrj5chv2"
  },
  "path": "/viewtopic.php?t=33298&p=275815#p275815",
  "publishedAt": "2026-06-20T19:00:16.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "**Off-topic:**\n\n\n> It has been bothering me a bit on why do some users still use the old fork of Greasemonkey that not only is not functioning on many mainstream APIs, but also has a lot of vulnerabilities in it. Is it that they haven't heard of the new fork? Is it that they believe the new fork is in active development, so they assume they'll be facing a lot of bugs? Is it that they're skeptical about mine somehow introducing more vulnerabilities? I guess I'll never be able to satisfy everyone\n\nI think the older version should be retired from the Pale Moon Add-ons and the Basilisk Extensions pages, as it is 8-years-old and unmaintained. If someone still wanted to use it for some reason, they could always just search 'github greasemonkey for pale moon' and find it easily. Once it is retired, I would expect more of a migration to your up-to-date version. I've been using your version and telling others to use it.\n\nI've written a post in the add-ons section recommending de-listing the older, unmaintained version. We'll see if it gets a response.\n\n> I think I have reached the full parity with the mainstream userscript managers out there\n\nThis is an exciting milestone! Great work!!\n\n* * *",
  "title": "Add-ons • Re: Working on a Greasemonkey fork for Pale Moon",
  "updatedAt": "2026-06-20T19:00:16.000Z"
}