Conversation

Notices

1. Embed this notice
   :apa: スプリットショックウイルス † (splitshockvirus@mstdn.starnix.network)'s status on Sunday, 26-Jan-2025 16:16:59 JST :apa: スプリットショックウイルス †

   • かき@GNUsocialJP

   That's a new one

   • Embed this notice
     :apa: スプリットショックウイルス † (splitshockvirus@mstdn.starnix.network)'s status on Sunday, 26-Jan-2025 16:16:58 JST :apa: スプリットショックウイルス †

     in reply to

     • かき@GNUsocialJP

     So if you want hear some spooky shit. Some context of this post.

     tl;dr You are the first person who stared face first at the Demon Core. I was starting at the exposed core of Reactor 4 in Chernobyl and didn't know it.

     That name, is not supposed to be like that. And what was happening was it was deleting or rather writing over pieces of the 256+ (which is another qemu bug) backing chain and was never caught by our monitors because it was an unknown unknown or machine check fault I guess you could say in programming language.

     In short 6 months worth of medical data were lossed without backup because the backups just copy the qcow2 but never check chain integrity (because why would you ever build backup test functionality into your product?).

     Anyways the company is under litigation because of this and the two people that found this are now out of work, not in retaliation but because of declining revenue, customer pulled out (I would too).

     ✙ dcc :pedomustdie: :phear_slackware: likes this.
   • Embed this notice
     ✙ dcc :pedomustdie: :phear_slackware: (dcc@annihilation.social)'s status on Sunday, 26-Jan-2025 16:17:36 JST ✙ dcc :pedomustdie: :phear_slackware:

     in reply to
     @splitshockvirus O shit....
     joker_running_away.jpg