{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiebsca7qyrode4vokivablzbxoaply5ryes455bwjxwpplelhposu",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mi4c5jm6qpu2"
  },
  "path": "/viewtopic.php?t=33248&p=271531#p271531",
  "publishedAt": "2026-03-28T08:10:30.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "> > > Either way though, it would be an improvement and I'd be happy to evaluate. The biggest issue I see with the commits isn't actually the substance which looks overall clean, but rather that they need to be cleaned up and/or split to keep code changes focused on just one thing with minimal drive-by changes. I could take on that task if it's not clear how best to make PRs?\n>>\n>> I'll be more then happy to give you or anyone else at the Pale Moon team an account on my Gitea instance if that means Dactyloidae's changes gets pushed to upstream\n>\n> That won't actually be necessary if the repo is public. I'd have to manually go through the code changes anyway and make new commits\n\nThe code isn't exactly 100% finished just yet as I've still got some more WASM and JIT optimisations to make, as well as other changes I want to make before 13.0 becomes stable.\n\n* * *",
  "title": "Other Applications • Re: Dactyloidae Browser (Basilisk fork)",
  "updatedAt": "2026-03-28T08:10:30.000Z"
}