Initially we suspected that Plurk might have made some change in its APIs, so our API calls failed. However, after checking the log.... we found the error message below:
You have reached your daily limit of 50000 calls. Contact Plurk support to get white listed.What?? What is that?? How's that possible??
We've been monitoring the Plurk API stats of PlurQ everyday, and the average amount of our API calls is only around 14,000~15,000...see, far from 50,000 obviously!!
However, the error message is the evidence, and we can only try to find some way to solve it.
At first, we planned to disable some API calls to avoid reaching the threshold, and then release a temp version as workaround. But still we were not sure if that can resolve the situation, and don't know when PlurQ will be unlocked (due to over the limit).
Then, we decided to contact Plurk to ask them if PlurQ's API key can be added to the white list, i.e. the API calls amount won't be limited.
Luckily, Plurk replied us quickly, and the API key of PlurQ is white listed at 17:25!!
This is really a GOOD BAD News for us.
It's bad that PlurQ caused too many API calls, and caused the inconvenience of PlurQ users.
It's good that PlurQ is sooo popular that the limit can't restrict us at all.
Thanks for Plurk's prompt reply, and thanks to the using of our beloved users; now all the problems are solved, and everyone can plurk via PlurQ again~~
1 則留言:
P.S. After the whole thing is done, we did some math...and found out that 50000 is a easy limit to be overcome. If we have 1000 users, and evert one calls the API 50 times a day....50000 is not enough at all >_<
So...why is the Plurk API stat doesn't show us the correct count T_T
張貼留言