{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreia3zd47rgecyh2opbl5cu55fbvh2ypu35dwynpznnocohdn45k4a4",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mpmlfuqwhzs2"
  },
  "path": "/viewtopic.php?t=33568&p=276165#p276165",
  "publishedAt": "2026-07-01T20:43:08.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "While the simplified idea that the PHP code is just interfacing HTML to a storage back-end (and providing novel ways to query the database and present data from it) is correct, I definitely wouldn't want web clients to be allowed to talk to a database back-end directly. While you can have considerable code inside a database (sorry Ben! but modern databases are a lot more than just data storage), having the PHP/html layer between the user and the database is quite necessary, if for nothing else but to sanitize the requests.\n\nGiven that though, a piece of forum software does indeed have a fairly straightforward task and it's not even as much of an issue running an older version of it (or PHP for that matter) if it's sufficiently mature. There are e.g. still plenty of phpBB v2 instances out there and that hasn't seen any updates for I don't know how long. PHP is interesting in that any vulnerability in it is only exploitable insofar as the vulnerable methods are actually exposed via php code to clients.\n\n* * *",
  "title": "Forum and website • Re: Unable to reply while editing a post",
  "updatedAt": "2026-07-01T20:43:08.000Z"
}