Edit2: Loving CherryPicking so far. Would be absolutely amazing if you could do some sort of website output like bithopper and even better if you figured out a way to feed multiple instances of CP into one website output.
Glad to hear that!
![Grin](https://bitcointalk.org/Smileys/default/grin.gif)
About the website, I'll be honest about it: I suck at developing web-based stuff, so I can't make any promise, at least for the time being. However, if CherryPicking becomes more and more popular maybe somebody will make a sort of web front-end that scrapes info from the log or from the future .csv files and displays it online.
As for multiple instances, I assume you mean on different machines and I was already thinking of making it work in "master" and "slave" mode or something like that. Basically, you'd have slave instances of CP connecting to the master instance, the master instance would be the only one gathering stats and then sending them to the slaves, to avoid sending the same requests from all machines if they're on a single network. If I ever get around to doing this there will also be a few commands available to the master instance and I guess having it gather mining stats from the slaves wouldn't be too hard, so it could dump those to a file and the web front-end could get the info there.
This is still a sort of concept idea, I wouldn't say it's the lowest priority but there are other things that are more important right now, like tweaking the hopping algorithm for Score and seeing if PPLNS is worth it or not.
I'll check out that hop you mentioned, it shouldn't hop on Slush at 98.7%. Was that the actual diff percentage or the number it was displaying? The number is a priority calculated differently for different pool profiles.
Edit3: Getting this error on rigs not running a bitcoin server:
[Miner0] mtred.com:8337 Problems communicating with bitcoin RPC 0 2
Doesn't seem to be affecting anything. Just want to make sure that I don't need to be running the bitcoin server for CP to work.
That's a message coming from poclbm itself (anything that has [Minerx] in front is coming directly from a poclbm instance), CP is just relaying it to you and it has nothing to do with it. There probably was lag spike or something and I think the bitcoin server stuff is purely coincidental, CP has absolutely no need of it. I'd ignore it if it isn't affecting mining. I've seen messages like those too while mining but they didn't seem to affect anything.
One thing is worth mentioning I guess, if CP gets 8 of those messages (from Miner0) in the span of 30s it'll mark the pool as lagging/down for 10 minutes and disable any mining on it. This is so it automatically switches from dead pools even if the stats API/web page is working. It doesn't connect to the miner hosts itself so it has to monitor poclbm's error output instead.
Does SMPPS work with 0.6.3?
No, there's no profile for SMPPS in 0.6.3, but you can indeed use them as BACKUP.