It's funny (and sad) that all of the free market concepts and "freedom" represented by bitcoin changes when some don't like how others use it and in turn want to see some regulations that don't exist in some of the markets bitcoin is attempting to supplement with a "better" alternative.

What is happening to the pool? Hashrate has been steadily declining for the last couple of weeks and is about half what it used to be.

I definitely give you credit for paying everyone back. Rebuilding trust with some may be hard if not impossible but you took a step you didn't need to although I suspect your motivation may not have been the most genuine but in short it's good insurance against a quick trip to juvenile hall or probation.

It's definitely the largest however I'm wondering what the reason why is? I'm not asking simply to cause trouble but I am wondering the reasons because using Deppbit and other pools with a fairly large hash rate has given me some perspective and I'm interested in hearing yours.

WE may not have seen the new site yet but you've made the pool very stable now and many of the previous issues don't exist, that in itself is very impressive. I see the hash rate swing enough to realize you have many pool hoppers but I'm running my 5.5Gh/s against this pool full time and have been for some time, impressive work!

Please explain why this is the case?

Great question

If I recall correctly there was a shorter one a few days ago, I might be off base though.

EC2 is transient by nature so without really having a handle on how to manage persistent vs. non-persistent storage in EC2 it's not hard to lose things and has happened countless times to small and large users alike. With that said it does provide an easy way to jump, I haven't followed bitomat but if they provide instance IDs and S3 paths one could take some steps to verify some of their claims.

Per the network it's 1888786.7053531 right now.

Giving the shift in pool hash rate after solved blocks I assume you see a fair number of pool hoppers?

Close to breaking 24 hours, I jumped on to see if the system didn't flush solved blocks like before but with Jine on the thread it sure sounds like this is just a really long block.

Jine,
I know you're busy, dropped you an email or two and a couple of PMs with no reply, just pinging in case your box is loaded up.

It's looks to be calculated based on total difficulty and your hash rate. The number varies based on those variables and not the pool's luck, etc. and I think that is good because those shifts cannot be planned no matter how big or small the pool is.

I have an iPhone 3GS 32GB I can offer up, PM with offers in BTC

Very impressive! Running for 90 minutes or so and keeping rejects at 0.590%

Hash rate down to 280Gh/s now, workers falling off quick, something is definitely wrong with the pool..

How did you end up rate limiting hosts? Asking because almost 15 workers here and sure enough since last night they cannot all reliably connect, if I start up some others fall offline, etc. I cannot keep everything running now without some not getting work, I temporarily moved my 2.7Gh/s rig to Diablo again and it's getting work and others can stay up but the rejects are worse then ever. I'm not sure what to do to keep my 5+Gh/s on this pool since I'm always fighting something..

EDIT: Pool reporting about 340Gh/s are you losing this many users or do you have an issue right now?

Is your limit going to be 400 getworks a second? I only ask because I have about 15 workers behind one IP, an aggregate of about 5Gh/s but I do it this way because shrinking down the number of workers still results in a lot of rejected shares. I'm not where near 400 per second but thought I would ask so everyone can gauge whether or not it will be an issue.

Unlucky, it sure looks like it but the occurrences are picking up, without running the numbers it's hard to get a real feel for what is happening but I see from the posts it's raising suspicions.