Code Update
What have we been up to?
After the small detection by Xigncode, which they implemented the wrong way, we realized next time we might not have been so lucky.
Not content with our workflow and current set of security tools Clockwork and I set to completely change from our old hack security model to a brand new shiny one, with more bells and whistles.
So why all the downtime?
Rather than updating the hack to get it in working order, we took a step back and decided how we want to move forward, we decided that we needed to develop a suite of tools so we can better promise we're keeping your accounts secure. This is frustrating because the hack is non-operational (Even for us sadly, my poor character gets poorer every day), but this is an important step to be able to, in the end, have a really great, secure product that we're happy to distribute.
Moving forward, ETA, etc
I'll probably get a build back to working again in the next week, it will not have any security enhancements though, but to sate the desire I might do this, while continuing to work on our new tools suite.
Hope this helps, sorry for the unexpected amount of downtime, but if you're a user, you'll be happy in the end.
cheers,
Moon