>>1850
I read a little of the source code back when it got leaked after the hack, and it is quite different from the conventional open source imageboards. The way something like Lynxchan works is that posts are stored in a database, and then when a user wants to see a thread, the program fetches those posts from the database and sends them to their browser, and caching is done between some of these layers to speed up the process. Yotsuba, for the vast majority of user requests, skips the database step entirely: each thread is just a file (.html) that is served statically and modified in-place whenever someone posts something; this is way faster than even caching database queries like Lynxchan does.
Although the technique works, from a programmer perspective this is ugly, clunky, error-prone, unmaintainable, etc. so personally I don't think we are going to see established projects adopting it. Most imageboards don't need scale, so it's reasonable that people prioritize readability and maintainability. We are more likely to see someone writing an imageboard with LevelDB or Cassandra than re-implementing Yotsuba.
