{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiemxxcu7ky5jboggg6nmzqsvuikh3pin7w3f5b4lnfs5qz6yjq7ai",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mil766htva32"
  },
  "path": "/viewtopic.php?t=33281&p=271762#p271762",
  "publishedAt": "2026-04-03T07:07:08.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "As an aside, to demonstrate the issues with e10s, current release cycle Firefox security bugs that I just went through had 45 of the bugs I looked at directly related to e10s. In just this month.\nThat's not counting issues that are less obviously _prima facie_ caused by the e10s architecture of Firefox. Keep in mind how long ago this was introduced in Firefox, and we're _still_ constantly having security issues in it _every single month_. It was supposed to be a \"more secure\" way of handling web content, remember? Because web content would be limited to its own less-trusted processes. Turns out it's suffering from exactly what I said, in that the messaging protocol itself is vulnerable to attack in ways a single-process browser would never have exposure to.\n\n* * *",
  "title": "Platform Development • Re: e10s support question",
  "updatedAt": "2026-04-03T07:07:08.000Z"
}