{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicelfszmffrucmjwbosqgbfg2xgygnahlligsyg3v52tvme7kgcqq",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mkzs2om2q6c2"
  },
  "path": "/viewtopic.php?t=33298&p=273392#p273392",
  "publishedAt": "2026-05-04T13:21:05.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "So, I'm currently working on:\n\n\n  * deleting 'framescript'/'messageManager' round-trip that is doing nothing on a single-process browser, replacing it with direct chrome-side injection (Unless if someone just decides to approach me and be like \"Why did you delete that, I was making a fork of Pale Moon, but was about to introduce e10s into it and now your extension is unusuable in my browser\").\n\n\n  * 'GM_util.getService()'-style indirection that exists only because Mozilla once threatened to take JSMs away - collapsing them to direct calls.\n\n\n  * XBL bindings that aren't load-bearing — convert to anonymous content + JS\n\nAnd some Multi-process /e10s idioms surviving in places where they no longer matter.\n\nI tried to avoid doing that, but the more I develop the extension, the more my code goes through friction with dirty code. It's inevitable for me to do something about it, and it'll definitely take a lot of time and effort in order to fix such thing.\n\nI'm glad that the latest 3.6.1 is already stable and nobody reported any instability issues with it - this gives me so much room for me to stay off-grid and do nothing but streamlining my code and hopefully I get to fix some long-standing bugs that cannot be fixed by any other way except streamlining it.\n\nSo, the per-script option redesign update will be delayed for a bit, until I streamline the extension.\n\n* * *",
  "title": "Add-ons • Re: Working on a Greasemonkey fork for Pale Moon",
  "updatedAt": "2026-05-04T13:21:05.000Z"
}