You have requested this feed too many times within a given time frame.

The edit tactic only works for a short time and then things get scrambled again. I've read reports of smaller than expected and significantly larger than expected statistics.

it won't work at stat update time - the reason it works is because it is only querying the page one time. database says there are 427 unique usernames with a wcg statbar....so when the script that updates runs, it querys those 427 names individually, as my options are to either go through the 300k+ list for the 427 users i need, or to make a small query 427 times. querying 427 times is more efficient for me then trying to filter through 300k users...


so what's happening right now is, it will retrieve person a's stats. it will store those stats for person a. it moves on to person b. it tries to query the stats for person b, but wcg flood control says you can't. the script is currently written such that, if it can't get person b's stats, it will use person a's. moves on to person c....if the flood control still doesn't like it, then person c will also have person a's stats....and so on. hadn't considered this scenario when writing the script that retrieves the stats - it can be rewritten to wait a set period of time, but i need to know what the flood control is at to make sure the overall process stays efficient....as it currently takes at least 2 hours to run through the stats for ALL the projects dc stat currently supports....