>>/9/
That's not as likely to happen because of how LynxChan is designed. In conventional imageboards, whenever somebody posts a new thread or a reply to a thread, every single board page and everything that references that board has to be regenerated by the imageboard software. This is because everything on a conventional imageboard is static HTML; when you access, say, https://8ch.net/tg/catalog.html that is an actual HTML file named catalog.html on a hard drive that is served by a web server. This means that when the imageboard gets big, there's so many HTML files to write whenever something happens that I/O write goes through the fucking roof and everything breaks, like what's happening on 8chan right now. On LynxChan all this shit is generated dynamically from templates and cached in memory, so afaik it's going to be less likely to fail in such a horrible manner when under 8chan-level stress. Also, the system is designed so we can add more servers to the database stack when we need to, so scaling isn't going to be a fucking pain in the ass.