{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihakaneefc4nhmfio5ywcx4s2unlgvl3bevunyeasmwf5g55eexpu",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mon47igs4yg2"
  },
  "path": "/viewtopic.php?t=33531&p=275759#p275759",
  "publishedAt": "2026-06-19T09:57:13.000Z",
  "site": "http://forum.palemoon.org",
  "tags": [
    "https://bugzilla.mozilla.org/show_bug.cgi?id=1876342"
  ],
  "textContent": "> Does this shed some more light on that black box? https://bugzilla.mozilla.org/show_bug.cgi?id=1876342\n\nNot really, as it just deals with system registration of the proxy as a scheme handler; it doesn't explain anything about the proxy itself other than a drive-by mention of a \"dual browser\" setup and launching Firefox from within Chrome, which I already figured out before. It says nothing about why this would be a thing to begin with, or why Firefox needs to integrate so tightly with Chrome, or how it can be used in good or bad ways.\nAssuming Firefox defaults to accepting known extension IDs in Chrome, I can see abuse being easy.\n\n* * *",
  "title": "Pale Moon for Mac OS • Re: How is PaleMoon 5 times smaller than Firefox on macOS?",
  "updatedAt": "2026-06-19T09:57:13.000Z"
}