Now if only we didn't have to read you go on and on and on and on about it.... yeesh - you're glad you're gone, and so are we - have fun blathering on at your new pool thread....
If there wasn't a stupid comment that there isn't a problem or your stupid comment you wouldn't. I hope that this error soon start affecting you so you will know the pain me and about 10 other users that have reported this had or have. But the comment like that made me move so it is a good think...
And Slush is still my backup pool so I'm still looking if it is working correctly and helping with my experiences to users who gets "It is not the pool it is you"(so they know that if they get ping timeout that doesn't mean that they have a problem as someone suggested or that if tracert doesn't work or that they didn't send the shares even if they seen them on screen or that they got disconnected even if the shares were accepted and so on with stupid explanation). I know this is not the case and I can explain why for every example. But seeing more and more reports shares counting errors and I'm relay thinking of changing priority to make Slush backup pool of backup pool. But then again noting is wrong so really don't know why this is happening right?