I can understand your skepticism of my fix.  The beauty of using github as a code repository though is that you can see what I changed.  I've been around long enough to see these things happen in the past.  Hell it just happened with TAG, and I did the same fix for my pool.  If you look at the code, all it did was limit who could connect to you.  You can do this manually with IPtables in linux, or you can code it in the client.  I coded it in the client as I was almost 100% sure that the issue was older clients submitting erroneous blocks to the chain.

I just want to clear up something though... it wasn't "my fork".  I resynced the wallet numerous times until I got on the fork with the highest block height(which I was told was the highest block height by the community).  I just pushed a fork along.  At that point really, any fork would have worked.  It's just best practice to try to push the furthest chain if it is valid.

I agree with the point on contrary views comment you made.  It's good to hear the other side.  Hell, in the last week, I called out the owner/dev of Tagcoin.  I've put 4 months into that coin, and I ran one of the largest pools for it.  But the owner was ready to walk away from this forum.  So I spoke up.  That being said, the devs and a community leader made a pool.  Sure the block bonus was definitely questionable, but the devs/leaders corrected that.  That's good leadership.  No need for Kheg to knock them on that.  They are trying, just like the rest of us.

+1 to your comments, but just two things... I'm not the 'owner' of a pool.  I'm the owner of the pool.  And my 'fix' was the fix.

I'm here for the long haul... until the wheels fall off.  I'll embrace anything that looks like a positive attempt to better the coin.

-Fuse