Prohashing Mining Pool Forums

Here's today's brief status:

• After fixing all sorts of weird cases, this morning the mining server went down for one thing that we couldn't test on our differently configured development server: it ran out of disk space. Fortunately, no money was lost because shares weren't accepted during that time. Chris changed the logging parameters and this particular issue should never recur. As we discover one bug after another, one would hope that the server will become more and more stable over time, even if those bugs are discovered on the live server.
• We released a change yesterday so that the tooltips over charts are now visible on Firefox. That was a long-standing bug reported by many people. We fixed it by downgrading the DevExtreme charts to version 13.
• I spent almost the entire day yesterday trying to resolve the reason why the block explorer crashes in Internet Explorer. I wasn't able to come up with a reason for that, and we decided to permanently close that task. Edge will replace Internet Explorer eventually as Windows 10 becomes dominant, and while some customers are being lost due to the bug, we cannot figure out the cause, can't figure out how to figure out the cause, and don't anticipate ever being able to fix the problem in IE.
• Next weekend, we plan to make our profit reports available to the public. The only difficulty in doing this so far was that we were focused on improving pool profitability for customers, and we need to cache these profit reports that take 60 seconds to generate. As far as I know, this would be a first among mining pools, and we think it's important to provide this data so that customers are able to trust our numbers and payouts.

That would explain the hashrate chart color change, only problem left in reference to tool tip popup's is that they aren't showing up at all on the "Hashrate" chart, perhaps a setting/tag was missed during reconfiguration (this is on both the main page, and Earnings/person.html page

Never-mind my own failure to operate the computer appears to be the issue at hand, older version has to be hovered over at the apex to view that rows number
Hate those pesky debug log options
EDITED For Id10T factor