I've been meaning to ask for a while... how are version numbers generated? Do they encode any information of interest to a user?
They are git commit hashes. You can look at the source code for your version by going to
https://github.com/forrestv/p2pool/tree/053d7ca or you can see changes I've committed since your version, by going to
https://github.com/forrestv/p2pool/compare/053d7ca...master .
I'm sorry my sentence keeps coming up, I was answering a previous message from piuk with a link to blockchain.info which had a wrong block listed and just the day before p2pool log file was found by me to contain out-of-date (and as such "misleading" as in "misleading to a user" of p2pool) informations (they clearly are not misleading to their author or to someone who digs into the source code and understands its inner workings).
I also did not check that blockexplorer link because I thought that grepping p2pool log file was the surest way to know what was going on and in case of troubles (blocks being lost and share numbers swinging a lot were yesterday "problems" I was trying to go after) looking up an address to see if it got its payment is not a good idea IMHO since on a lost block every address should not receive any payment.
So I was trying to express the idea that there is not a "place" which lists blocks found and found but rejected by the network as it happens with other pools which often have such a "place".
Maybe my sentence sounds to english speaking peoples in way that is too harsh or just stronger than it was meant to be, my apologies if this is the case.
Ah, sorry, I guess I didn't understand then. The best way to see invalid blocks is to see if any of the blocks mentioned in your log aren't present on Block Explorer. Just looking at Block Explorer only tells you confirmed blocks, and only looking at your log can sometimes tell you old blocks and sometimes not tell you about new blocks, due to them being stale on P2Pool.
It wasn't too harsh!
