Yep, they're all interleaved by
Tomash
on 2017-07-20 17:02:00 UTC
Reply
The main reason is the internal architecture of the archives and T-Board. Specifically, the way the archival process works is that various bits of scraping code (the script that hits a YWA board and the function that dumps segments of a T-Board) output the contents of their respective post-containing thing in a specific format (Ruby Marshal dump of lists of hashes and lists). Then, there's another bit of code that takes such an archive files and posts it all to a T-Board instance. In order to make it easy to distinguish the archives from everything else, all archived posts are posted by the user "Archive Script". (This started as a workaround for needing the posts to be posted by some user account, and turned out to be useful.) Finally, there's a series of commands and scripts (which I really need to chain together in a more automated way) that'll get T-Board to output the posted archives into the format everyone sees (and a different, much smaller, set to generate the spreadsheets)
The reason there isn't anything more principled to store multiple archives is that the current system works and I'm lazy.
This system also has the advantage of making it easier to compute statistics over all our various boards. For example, here's some information about the number of posts per day we make
Min. 1st Qu. Median Mean 3rd Qu. Max.
0.00 22.00 37.00 43.05 56.00 317.00
- Tomash, who'd do more stats but needs to go job