Quote from: suchmoon on September 18, 2014, 03:56:05 PM

Quote from: NuShrike on September 18, 2014, 03:07:59 PM

Quote from: NuShrike on September 05, 2014, 04:25:33 PM

Quote from: rdyoung on September 05, 2014, 03:15:33 PM

If you look at erics linkedin profile he has the chops to handle what they are doing. My bet is they are growing too fast and attempting to do too much at once. It also doesn't help that people are buying tons of hashlets and probably leaving them as singles which adds to the db and increases the time needed to process payouts.

Sounds contradictory. How did they get into this mess if he has the "chops" ? Overnight account-system changes aren't SOP for "chops" either.

Also, if he had the "chops", he would've known how to build a scaling system from the start, or at least catch it before it got this bad.

I think I'm still calling it. Another late #payoutwatch day.

And how about those security issues alluded to in the announcement yesterday. I hope they just dumbed it down for PR, but it sounded like the solution was to reduce the session timeout. I don't see how that fixes anything, because it looked like it was allowing access to accounts without validating the session/auth cookie on the server side. Either way it doesn't speak well for their development and QA practices not to mention deposit security (#6 in the OP).

wonder what that timeout is? been going on 2days now and still haven't been logged out again lol well least their putting some 3rd party guys to fix it Wink