The Historiotheque v.2.0.1: Abject Failure
Notes Towards The Possibility of The Concept of a 24-hour Production-Year
Message From Chief Secretary of Art Operations (unofficial title)
Ok, folks. On Day Two after the official launch of The Historiothèque version 2.0.1, at 10h30 (EST) on the Second Day, I’m unhappy to announce that it is officially being shut down until further notice. Got to do some data analysis, but something went wrong. Won’t need to expand or anything, just rebuild it from scratch. It didn’t even make it to the official release of version 2.0.2. So I’m closing shop until further notice, don’t know how long the analysis will take, sorry for that. That means I finished Production-Year 2017–2018 in a little over a day of work. That’s the record to beat. Now I want to see if I can do even better than that, and in order to do that, I need to rebuild everything from scratch. I will keep you posted on developments periodically. Take care and keep in touch if you need help with anything concrete and with realistic achievability for you and you alone. Ciao-bye!
Addendum v.1.0.0 to the Abject Failure of Historiotheque v.2.0.1:
I realize that a lot of this probably doesn’t make much sense yet. We just had to make a correction to the first document which announced the official launch of Historiotheque v.2.0.1, which was published in this Publication on August 20th, 2016. Yesterday was the official start of the Production-Year 2017–2018 and the Historiotheque had to be shut down. Art Operations housed within the Historiotheque were at v.5.0.1 at the beginning of the day and earlier this morning, before the failure of the Historiotheque, we unofficially released Art Operations v.5.0.2. So at least that’s a net positive. And so far, data analysis shows that we got mixed up with various versions in the previous document. That has been fixed, but we still would have had to shut down The Historiotheque anyway because after about 2 hours of hard work this morning, nothing made sense to anyone anymore. Rather than risk going completely offline, we just put everything on hold until further verifications can be made, tests run. I don’t want to ruin all the fun, but we had an unexpected visitor who just caused a little turbulence. We thought a raccoon had broken in or something. Long story. Hopefully we can get back to work ASAP. This is a really important project for us. Peace.
