{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiedmiuy4wtrhvozs6kuviclgzqemdot34yfkr3w7ynb4rxmeyqifq",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mmzmc2vyrot2"
  },
  "path": "/viewtopic.php?t=33298&p=274919#p274919",
  "publishedAt": "2026-05-29T22:18:36.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "> > Maybe I've missed your point, but just give it another name? adBlock Moon / sBlock / BlockIt / etc...\n>\n> I'd have to think of a name, come up with a extension logo, depending on how much I'll be diverging from the upstream version, I might have to come up with a wiki page for it, etc...\n>\n> Too much hassle for dear old me. If it was up to me, I'd much rather handle the back-end of the extension, rather than dealing with the UI.\n\nTwo thoughts:\n\n1) gorhill has already put his stamp of approval on \"uBlock-for-firefox-legacy\", which others have forked without incident, not just UCyborg and JustOff. Could this simply be the most advanced of the uBlock-for-firefox-legacy forks? Seems like it could live in that space for a bit if it makes technical sense.\n2) If not, you could still just handle the back-end of the extension, roll it out as a kind of basic beta with no particular new UI or naming or logo or wiki work, and then some of our creative users could possibly jump in with ideas for pull requests to fill in the gaps. Then it could be a team project, with different contributors focusing on their area of talent and creativity.\n\n* * *",
  "title": "Add-ons • Re: Working on a Greasemonkey fork for Pale Moon",
  "updatedAt": "2026-05-29T22:18:36.000Z"
}