I disagree, there hasn't been a block miscalculation since the one everybody went berserk about exactly one week ago.
block=start_time,duration,reward,hashes,luck,difficulty,confirmations
235160=2013-05-08 15:13:44,1:27:14,0.00000096,9167,1.34,10076292,100
Since then people have been reporting the slightest variations as problems - when it's perfectly normal to have some variation - based on your own luck and the pool's luck as a whole.
Where people are reporting zero payouts, they are showing that they have submitted no shares - meaning connectivity issue - not block calculation issues.
I think Slush is monitoring from afar (I don't blame him for not coming on here with all the bitching going on) and long may it continue. Connectivity issues should be kept separate from the block miscalculation issues (which seem to have disappeared as I say).
User was looking at screen as he reports(and he is not the only one). I had logs that prove that shares are missing(unfortunately log is deleted when you restart CGminer and I deleted the copy from my computer since there were no way to report it to Slush and the block got confirmed). CGminer reported accepted shares(meaning that cgminer sanded the share and pool confirmed it valid) and pool didn't record them. Nobody is saying it is a calculation issue. It is database issue when you see this.
And I don't think Slush is monitoring this. Unfortunately I starting to think that something happened to him about 10 days ago and he can't control the pool and it is having bigger and bigger problems.
I still use Slush as a backup pool and I did see in time of maintenance of my new pool one miner connecting on Slush(stratum) and the other with same configuration going over all stratum server and api to old backup. So tell me that this is normal for a normal working pool. After loosing on 13 blocks I have given up on Slush since it cost me about 0.05BTC