TeaRex is exactly correct in the explanation. The reason I didn't display utility as "expected per share" to begin with, is that each share has unique utility. The database keeps count of the number of shares submitted by each user to each pool in each round, and also of the sum of the shares' utilities in that round. When a round is rewarded, each user receives a proportion of the round's reward equal to the proportion of the user's total utility against the total utility of all users in that round. To me it is easier to think of expected utility in these terms. Couldn't someone write a greasemonkey script if there really is demand for displaying utility as per share, rather than total?
So shares -> (calculations) -> utility (calculations) -> efficiency? ok, got it.
I don't really care about showing utility/shares, but if you could publish the total shares it took the 'victim' pool solve the block our shares are from, that would be awesome. Although prob very hard. Are some of the shares getting grouped together with shares from other blocks?
So what's the deal with eligius? Eligius-us is back up, serving stats and getworks, and accepting shares, but it is "down"? I guess I'll keep it out of rotation while it decides its existential problem.
Yep, Eligius US accepts shares but forwards them on to Eligius EU. Sometimes, though, it's up and hashes for a little bit. But Eligius US is down for all intents:
http://eligius.st/~artefact2/