Sunday, November 20, 2011

Some Chase Community Giving Statistics

As nobody was doing this (that I know of), for recent leaderboards I
have been following the votes being got by the leading 9 ME/CFS groups
along with how much 100th position has gone up by (101st would be
slightly more interesting but one can't see that).

For the last 7 12-hour periods, 100th position has gone up by
(chronologically): +39, +44, +53, +40, +61, +75, +50. At the last
leaderboard 100th was at 882 votes. That's with 2 days, 6 hours to go.

Looking at the last two jumps (i.e. +75 and +50) (it would be extra
work for me to calculate too many periods) apart from the IACFS/ME,
the groups have been losing ground.

It is going to be touch-and-go for lots of groups whether they get the
$25,000 or not.

#30 INTERNATIONAL ASSOCIATION FOR CHRONIC FATIGUE SYNDROME/ME Chicago,
IL http://bit.ly/s48mcK  (+74) 1,228 (+53) 1,281

#34 CFSKNOWLEDGECENTER INC Wellington, FL http://bit.ly/lkvWpU (+50)
1,194 (+37) 1,231

#56 MASSACHUSETTS CFIDS/ME & FM ASSOCIATION Quincy, MA
http://bit.ly/sJXeQ9 (+52) 1,016 (+50) 1,066

#72 ROCKY MOUNTAIN CFS/ME AND FM ASSOCIATION Denver, CO
http://bit.ly/s5fAJh (+38) 931 (+36) 967

#76 WI MYALGIC ENCEPHALOMYELITIS/CHRONIC FATIGUE SYNDROME, ASSN, INC.
Sun Prairie, WI http://bit.ly/mlmr0c (+42) 906 (+39) 945

#90 ENTEROVIRUS FOUNDATION INC San Francisco, CA  http://bit.ly/lzhRfi
(+47) 862 (+36) 896

#93 NJCFSA Florham Park, NJ http://bit.ly/tXpa46 (+54) 850 (+43) 893

#158 CFOG, INC Kennesaw, GA http://bit.ly/kdavB3  (+47) 481 (+31) 512

#180 CONNECTICUT-CHRONIC FATIGUE AND IMMUNE DYSFNCTN SYNDROME ASSOC
INC Milford, CT http://bit.ly/uqIqF7 (+20) 368  (+23) 391

In previous CCG contests, there has been a charge towards the end of
the contest from other groups. As is clear, the ME/CFS are generally
just hanging in there - not keeping up with how much 100th is jumping
up by but perhaps able to hold on if things go right. 4 groups are
within 85 votes of 100th position.

A few votes could make all the difference ...

Tom Kindlon
(Twitter: @TomKindlon)

No comments: