{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibcfvbadpjkkk4u7mjwit44nyrni7ckgtz2ileo64uu45ws3rfmqa",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mnfexsdbhtd2"
  },
  "path": "/viewtopic.php?t=33494&p=275158#p275158",
  "publishedAt": "2026-06-03T14:48:35.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "> I was really hoping this update would have made a significant improvement to Palmoon's compatibility.\n\nIt has. just because the website you check still has issues doesn't mean nothing has changed. And as long as websites keep following daddy Chrome with continual updates to their code and never just settling on something for a longer time (does a railway booking portal really need to use bleeding edge APIs all the time?... Are they telling us that their portal sucks so much each iteration that they must absolutely chase the latest draft specs because otherwise it doesn't fulfil its task of giving visitors a way to book trains? What did users do 2 years ago? Were they not also using bahn.de?...) I think you can see where I'm going with this.\n\n* * *",
  "title": "Web Compatibility Support • Re: www.bahn.de/buchung isn't working—or is it?",
  "updatedAt": "2026-06-03T14:48:35.000Z"
}