I dont agree because I was watching the network observer at the time and your pools showed small issues. I lost 2 blocks and with this burst price its no longer a cheap fix. 184.108.40.206 got the block cause your cluster wallets didnt see it. I tried to post image but your sever cried error. I am Novell trained and Certified dont mess with me. I kept my business to myself about your network problems. But I am tired of loosing blocks and having to pay my pool because of a bottle neck. How many miners are there in your network? How many PB run through your router.
If it isnt your setup then why is the network messing up? Tell me what you think it is!
You are directly accusing someone of something.
Yet you cannot show any technical proof.
I keep logs of my miners output. I can retrace all deadlines that my miners caclulated, exactly when they were broadcast and anyone can see whats on the blockchain. And I can tell you, mining solo with various versions of the client over 35 months show that I do not always get whats "mine". Sometimes deadlines are too late or just a little too late, or broadcasting is too slow, my ISP may have eaten some packets, sometimes there is no explanation from OBSERVING ONE NODE ONLY.
You decided not to start a technical fact finding hunt, you started to accuse someone.
Now live with echo.
And on another note, Novell, Vmware certified ? Forget it, kids. I have 30+ years of unix+networking experience, AND an impressive beard.
So if you have some technical observation that explains exactly whats happening on Haitch's side to prevent the network from accpecting your deadlines, I can play the grumpy old man to decide. If you have nothing but the anger you've shown, shut up.