{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidzscpgqhmlawqu5ss65gae26eogx4x64224iixnnth2ht4ques3e",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mjq6zsen2fa2"
  },
  "path": "/viewtopic.php?t=31810&p=272478#p272478",
  "publishedAt": "2026-04-17T22:50:49.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "**Off-topic:**\nI don't think we should drop GTK2 support or NPAPI even if Linux distros are dropping support for GTK2. More experienced users will always be able to compile their own GTK2 if they truly need the GTK2 UI or NPAPI plugins. Even then, when we inevitably in a few years have to switch to an RHEL9 based distro for builds, GTK2 is still available for that OS as well. Same with RHEL10.\n\n\n> The other thing that's worth mentioning is... on non-x86 architectures, especially newer ones, plugin support doesn't really _do_ anything because NPAPI plugins were never built for those platforms to begin with.\n\nIt definitely does do things. I had to make a few small patches in UXP, but I am using a modified personal fork of the LightSpark Adobe Flash NPAPI plugin on LoongArch, an architecture which did not even exist until after NPAPI was deprecated. It does not require GTK 2 or 3 at all. It uses SDL2.\n\n* * *",
  "title": "Contributed 3rd Party Builds • Re: 32bit and gtk2 builds for Debian/Bookworm",
  "updatedAt": "2026-04-17T22:50:49.000Z"
}