Quote Originally Posted by AMDave View Post
I had a look at your stats and our stats and see the difference in volume.
Although your output is low, the chart pattern matches the chart pattern on our stats.
Thus we are subject to the same work unit availability as your team. (that is to say: the issue is systemic)
I can sleep a little more soundly knowing that we're still proportional to you guys. The largest drops seemed to occur in Spring 2012 (about that March), recovering in November. This matches my personal benchmarks as well; in August I had finally dropped to zero; by November I was back up to 50,000 for the month. And then in December it happened again. What is strange is that by January, your benchmarks had recovered from the December crash.

Since the issue of work availability appears to be systemic, I suspect the main difference is here is one of sheer numbers.
That is to say we have many more members running project clients than your team.
That there might explain a lot of it. We have similar amounts of members, but none of us are running more than two instances of the program. I'll assume that you guys will be running anywhere from four to sixteen instances per member, which more than quadruples your possible output.

In the mean time, if you think there is a real problem, I'd contact the project administrator via their contact page: http://www.superdonate.org/contact/

However, I defer to our project leader, NeoGen, to provide further comment and knowledge as he knows this project better than the rest of us.
I am currently awaiting a response from them. I also contacted Charity:Water to see if they'd noticed anything. Anyway, if NeoGen has any insight on what's going on I'd be more than happy to hear it. Thank you.