Boing & Organofcorti: I'm at a loss... that is strange. I made a change to the worker daemon that may resolve that issue. Is it worse now than before? I can't imagine why that would be. I'll get it figured out though. I have one more method that is a sure fire cure, but it's a bit costly so I wanted to avoid it if at all possible.
Fasa: It's fine if you use different servers, they all get aggregated into a central database for statistics and block tracking - just don't try to submit work from one server to another server, that won't work. Not sure how you'd do that anyway.
fadisaaida: Well, for now it's whatever you think is appropriate for what services you are getting
In regards to your suggestions:
1. What resolution are you running? Is it too large on other peoples screens as well?
2. I will add this to the list of things I will be making graphs and statistical tracking for.
3. It's both a security risk and a huge difficulty - integrating with vBulletin is a major pain, but I did make it so you can sign in to vBulletin with your Facebook account, meaning you don't have to go through the registration process, just let Facebook handle it.
We should be hitting a block any time now if we aren't running unlucky
The first day of the pool I was mining 12 hours a day in the EU server without problem, but when we got to 20-25 Ghash/s the problem came. I'm now mining at the US server, since it has less problems (not 0, less problems)