Considering the fact that flypool is too close to 51% (attack), and that it keeps under reporting my hashrate compared with what the local miners report (both dstm and ewbf) I was willing to give it a try for a day or two and see how it goes. So far it's reporting slightly higher hashrate than flypool. Let's when (hopefully not if...) it pays how that goes.
@zcash.guru if you could, please simply the API, the hashrate as number, I don't know what it is, but is way off... Like 50000 times the hashrate, which means I would have to estimate the hashrate from it. The hashrate as String is no fun reading as it requires string parsing.
For starters, all it needs is the current and average hashrate (real number) for the whole address, and the same (current and average) for each worker.
Then you might need to implement the immature balance, as it will stop people from raiding the pool.
Also there is a spelling error in the API documentation. Stats appears twice.