{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihtque45lz7g6pe5sjudfdd2wbk4x43oy3yagpjhvdiy552xry6i4",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mmwv3q47oa62"
  },
  "path": "/viewtopic.php?t=33466&p=274836#p274836",
  "publishedAt": "2026-05-28T18:58:20.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "> Maybe that sentence should just be dropped altogether. If people are curious enough they will soon enough find out they can try unsupported extensions from almost a decade ago.\n\nTotally fair. Trying not to sound \"old\" or invoke another browser and just expound on the power of XUL would stand us better.\n\n---\nI'd also like to reiterate that making it easier to make Themes and overall highlighting the GUI customization of Pale Moon would probably go a long way from making the browser \"look old\". As evidenced by Vivaldi, Opera, and even Firefox itself, making your browser look personal is a selling point.\nThough I'm loathe to say it, making default Pale Moon look slightly more \"modern\" (a misnomer, but.. also also, please keep current default theme. Non-flat design? idk what to call it) would ease a lot of transition issues. Judging a book by its cover is sadly common today. Once they get over that initial threshold and start customizing it themselves, a lot of niggling stuff that now looks bigger than they are would surely be glossed over I think.\n\n* * *",
  "title": "General Discussion • Re: Pale Moon's PR Problem",
  "updatedAt": "2026-05-28T18:58:20.000Z"
}