{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidffe4wtmsdacsoouvapuaenah77hosynfz7lfgob3hsg6n3vgka4",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mn56gcgaxax2"
  },
  "path": "/viewtopic.php?t=33298&p=274985#p274985",
  "publishedAt": "2026-05-31T07:22:37.000Z",
  "site": "http://forum.palemoon.org",
  "tags": [
    "GitHub repo",
    "@andyprough"
  ],
  "textContent": "**Off-topic:**\nI think I have decided on the design choices and what will happen with the project:\n\n  * The extension will remain restartless - it turns out that the extension has to be restartless, because it's too dynamic to be an overlay one - Filter lists reload, dynamic rules toggle, per-tab counters update constantly. The extension mutates every single second and the overlay method won't really make sense with it.\n\n\n  * The UI will resemble how it currently look like on Pale Moon (\"legacy\" look); I have tested the chrome-like look on Pale Moon and it didn't look in-place at all, especially with other extensions in use. However, it'll have the same QoL features that exist on the upstream version, i.e. Dark mode, \"Uncloak canonical names\", etc...\n\n\n  * The extension will keep using HTML files; It's not a secret that I would need contributors to help in the development of the extension, and redesigning the UI to be completely in XUL files would alienate anyone below the age of 35. Also, Having the UI made in XUL would give us some advantages, like native menulists/checkboxes, automatic theme inheritance, native scrollbars, slightly better keyboard nav, but the cost is **enormous** , especially with designing something like the logger and I also don't think that XUL has '<input type=\"text\">' equivalent that supports CodeMirror and the filter editors need CodeMirror. So we'd end up with a hybrid XUL-shell-around-HTML-editor anyway. Maybe it'll be something we'd reconsider in the future, but for now, we just want the upstream to be ported to even have a working one in the first place.\n\n\n  * The extension can diverge from the upstream version a bit - the original developer himself have the Firefox version diverged a bit from Chrome, because Firefox simply offered a bit more features to use. Going with that logic, we could also utilize XPCOM's more permissive environment in the extension's good use. The divergence won't happen in the blocking engine at all, this is the main selling point of the extension. The divergence will happen in other corners of the extension, making it have cleaner code - I was thinking of adding some features that couldn't exist in the upstream version, like skipping compression to have faster startup, use native DNS to uncloak CNAME faster, use 'nsIChannelEventSink' directly to avoid rate-limiting mechanism that exist on the upstream version, etc...\n\nAfter thinking of the names that can be used for the extension, I like @andyprough 's suggestion - I might just borrow the same naming scheme of my other extension and just call this one \"uBlock for UXP\" it signals the divergence from the upstream version, while keeping the main selling point of using uBlock Origin's engine, which everyone knows it's the best content blocker engine on the internet right now.\n\nNow, depending on how much help am I gonna get, this extension might finish its development in 1-3 months or in a year - I'll be documenting everything that I can through the forum and through my GitHub repo of the extension. I encourage all the help and PRs that can be added into the extension - I don't assume this project to be all mine or I'll be the one taking all the credit for, if I'm gonna get all the help that I can get to accelerate the development.\n\nI'm documenting the changes and design choices, so that atleast if someone were to ever take my place in the development of this extension, they wouldn't start from scratch and would be aligned with the original design choices or maybe think of superior choices to replace mine. I of course kindly ask to not be pressured into the development and the maintenance of the extension, since not only it's the biggest project that can ever be taken on this platform, but I also maintain another extremely important extension as well.\n\nI figured I'd also post some sneak-peak into the development of the extension: The first screenshot, I just added a temporary placeholder name, until I settle with a main one. The second screenshot shows a total of 328,401 network filters ＋ 103,592 cosmetic filters, instead of the current data of 166,628 network filters ＋ 42,609 cosmetic filters from uCyborg's fork of 1.16.6.1\n\n\n\n\n* * *",
  "title": "Add-ons • Re: Working on a Greasemonkey fork for Pale Moon",
  "updatedAt": "2026-05-31T07:22:37.000Z"
}