{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihn2tmfyuwd5g7wpsyntyc3evshvjifr2me25jskeyr4mnrco33ea",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mmmfif437s72"
  },
  "path": "/viewtopic.php?t=33412&p=274608#p274608",
  "publishedAt": "2026-05-24T15:38:45.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "**Off-topic:**\nApologies for my reacting so abrupt but you didn't mention it was going to be optional.  Even so, an obscure about:config key may be difficult to discover by the average user. If it were in Preferences then it would be alright I guess. Gtk3's dialog is bad, I'm not the only one to say it, so the chance to use the original one would be preferable once the user has specifically chosen the Qt build.\nI know there are people that want full integration by all possible means but that shouldn't come detrimental to usability, IMHO. So yeah, choice would be preferrable.\n\nThere are others who can't wait for a Qt build, and I can only suspect we are mere users not developers, so the most we could help with are ideas and testing. Maybe you noticed I tried hard to build it as it was, and failed too many times. It takes two and a half hours to build - if everything goes as planned, but I've had it bail out at the last moment. Still, I'm willing to test and report issues or ideas. Yeah, it's difficult but sometimes people just don't have a decent choice.\n\nSo please don't take it so hard. It would be a waste of your effort, and we would all lose in the long run.\n\n* * *",
  "title": "Browser Development • Re: Linux Pale Moon with Qt toolkit",
  "updatedAt": "2026-05-24T15:38:45.000Z"
}