Thread: [GUI Plugin] Goodreads Sync
View Single Post
Old 03-05-2016, 07:14 PM   #819
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by auspex View Post
But that's normal. You can only make a limited number of calls to the API before it starts throttling all of us! Every calibre plugin has its own (I hope) API key. Goodreads won't let that key make too many requests. So unless you have got your own key and modified the one in the plugin, you're using the same pool that the rest of us are, but even if you go to the trouble of doing that, you won't get to make many more requests than you do now.
That's only partly true. The Goodreads metadata search doesn't use the API. It simply scrapes the site. And at least half of Goodreads Sync doesn't use API functions that need the developers key. With all the problems Rellwood and others has reported, I have never had the error. Unless I'm getting lucky because of my timezone, I don't tend to think we are exceeding the developers key based requests.

But that does suggest a test for Rellwood. Try doing the problem request at an unusual time. If you usually do this in the evening after dinner, try in the morning. Or the afternoon.
davidfor is offline   Reply With Quote