The Revival Project

The Day The Network Stood Still

The datapoints are a great equalizer, bringing all who come to them the same level of knowledge with the systems they are associated with. Or that's how they're theoretically supposed to work. Truth of the matter is that coming in with some level of competence and understanding can go quite far, and being completely oblivious can have its own repercussions.

Especially when one learns something is theoretically possible and wishes to understand the how of it. Usually such explorations of an apprentice in a skill tended to be better guided by a master to avoid disasters. Well, perhaps disaster is too big of a word to cover what happens from the exploration of the communications systems by Dedicate Initiate Lark.

All it take is looking into a hidden directory here, accidentally deleting some data there, a frantic bit of trying to fix the system from memory, and a true lack of knowledge of Ctrl+Z as a lifesaver. And just like that the communication system's user database was horribly tangled, posting was down, and poor Lark was none the wiser of the chaos she had inflicted.

And so it happened that there came a Day The Network Stood Still.

Well not fully still, but it's sure being difficult. The posting process for public messages is glitching out, video and audio and even text posts bouncing back with a 'System Error: Please Try Again Later' message. Over, and over, and over for hours. Good news? The direct message function still works properly right? Right?

Wrong. Any message sent directly to another He Row will find itself caught up in the error and delivered. But never to the right person. The good news is that once a conversation chain starts, at least the system is sending back and forth reliably. People will just have to live with their mis-sent texts getting out there to other people. Who knows, maybe it will be good for some laughs.


( FAQ )