it should be 0.1 so I don't feel myself too lucky

this I can understand
18318   2013-06-01 11:29:04   1:58:52   18263762   5099   0.00459765   239049   25.09950000
normal being
18312   2013-06-01 07:01:02   2:09:08   19734291   5473   0.00685987   239012   25.46190000
18311   2013-06-01 04:51:54   2:10:19   20307448   5582   0.00724408   238993   25.26838085
that is because slush has some IP's that suddenly dont work over 4+ minutes I observed that on a block before this and changed 2 of my miners round robin approach to direct IPs. Slush is under the assumption that when one of the IPs wont resolve due to maybe a server overloaded that the miner will round robin to the next IP. but that is not how round robin and DNS works. a client looks up the resolution and takes the IP off the top, it will NOT "TEST" if that IP is working and choose another....

however this is Slush's formula failing due to a bug, as I did not have any connection issues near the end of this block nor did most everyone else
18309   2013-06-01 01:48:37   5:15:09   49659498   13369   0.00189029   238964   25.05830000

along with this one which I assume will be fixed by Slush
18321   2013-06-01 13:18:14   1:35:10   14691906   4191   0.00000669   239063   25.20347868

The payouts got smaller when the pool went from 10544.458 Ghash/s to 11544.458 Ghash/s last week

Yay! 0.1% of normal payout from a 90 minute block!

 

18321    2013-06-01 13:18:14    1:35:10    14691906    658    0.00000106

I would love to look into logic behind it.

This "score reset" should happen in multiple phases, if that's the culprit.

Amount of fucks given from the headquarters is as discouraging as it is small.

There is something wrong with counting rewards on slush

18321    2013-06-01 13:18:14    1:35:10    14691906    17080    0.00002318    239063    25.20347868    
18318    2013-06-01 11:29:04    1:58:52    18263762    20480    0.01752609    239049    25.09950000
18319    2013-06-01 11:33:12    0:04:08    627852    776    0.03168790    239051    25.11800000

also this long block

18309    2013-06-01 01:48:37    5:15:09    49659498    53890    0.00795695

Hmmm, time to reevaluate ....

18321  2013-06-01  13:18:14  1:35:10  14691906  6867  0.00001021  239063  25.20347868  85 confirmations left
...
18314  2013-06-01  08:31:26  1:17:10  11856454  5649  0.01095473  239025  25.17790000  47 confirmations left
...
18308  2013-05-31  20:33:28  1:42:52  16633401  7423  0.01143251  238930  25.00000000  confirmed

18322    2013-06-01 15:08:56    1:50:42    17158976    1462    0.00219536    239080    25.18504000    97 confirmations left
18321    2013-06-01 13:18:14    1:35:10    14691906    766    0.03116995    239063    25.20347868    80 confirmations left

Well, that kinda makes up for all the loss I've had recently..... (the top one is about correct)

For once I was on the good side of the errors.

Are these going to be fixed?

18321 is still incorrect, 18317 and 18 are way off too.