{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiaiwa2ju5wlnxxzzcqufy6whvjxc3eb47s3cwc224cewfuzc3ddci",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mkhcwt5mxgd2"
  },
  "path": "/viewtopic.php?t=33381&p=272833#p272833",
  "publishedAt": "2026-04-27T05:13:18.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "> Which goes back promoting the GTK3 binary to the #1 GNU/Linux position on the Downloads page, and beginning to communicate _**something**_ to the users so they know that this distros-dropping-support train is about to hit them right in the teeth in a very short period of time, and they need to start thinking about planning (or changing plans) accordingly.\n>\n> From what you said earlier, it would appear that _EVEN IF_ you shipped a GTK2 runtime with Pale Moon, it still probably wouldn't run with all plugins, and you would have various glibc mis-matches, etc. You apparently can't just fix people's problems by adding all the libraries to the official Pale Moon binaries.\n\nYeah, I think you're right on that one. That sounds like the most practical approach. You are really making a lot of sense here.\n\nAnd also, thanks for pointing out that we do still have a build-time advantage. I'm sure people understand we won't be figuring all this out right away... that Pale Moon will be in a rough state on Linux for a while. Just like it sometimes is due to Cloudflare and other things beyond our control. And it's not like we aren't making some progress, we did manage to get our Python 3 migration done. Which will help Linux users out a lot. It is one of the things I thought we needed to do for them, since a lot of them are self-building Pale Moon and struggling to find Python 2.\n\n* * *",
  "title": "Platform Development • Re: Future of GTK2 and Pale Moon",
  "updatedAt": "2026-04-27T05:13:18.000Z"
}