{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiemknkrfpwmxgfpli2obxz53eadssrzvoxivx4o6ezamekm2warea",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mlcfc42kcks2"
  },
  "path": "/viewtopic.php?t=33412&p=273657#p273657",
  "publishedAt": "2026-05-07T22:40:52.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "Oh, and I was looking into the licensing on XWayland...\n\nWhile we cannot bundle GTK because of viral GPL licensing. It turns out XWayland is mostly MIT and BSD licensed, with no copyleft obligations whatsoever. Which means if Linux distros did stop shipping XWayland, we could bundle it, and it's apparently not much more expensive to bundle than something like Cairo or Angle. Granted, all the sources I can find say that most distros, even fast ones like Fedora and Arch, really want to keep XWayland. But apparently if they ever did get rid of it, every app that relies on it could just start bundling XWayland and it would still work with minimal maintenance.\n\nSo that means X11-on-Wayland is likely to remain a valid way of doing things, and it's not as out of our hands as the toolkit situation. It probably seems counterintuitive or weird that we can ship a _whole X server_ that runs as a Wayland client with less licensing issues than GTK2, but that's apparently the reality.\n\nThis means we may have to worry about toolkits, but I can pretty much guarantee we never have to go Wayland even if the distros lose their minds and force apps to bundle XWayland.\n\n* * *",
  "title": "Browser Development • Re: Linux Pale Moon with Qt toolkit",
  "updatedAt": "2026-05-07T22:40:52.000Z"
}