Thread: [Metadata Source Plugin] Goodreads
View Single Post
Old 12-17-2015, 07:47 AM   #244
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 trying View Post
I presume (though I didn't look into it) that Calibre is purposely not sending more than 1 request per second per Calibre instance in order to try to follow the spirit of the Goodreads terms of use if not the letter.
No, calibres request limit has nothing to do with Goodreads. It is the chosen limit for all metadata source queries. If it was chosen for a particular site, it will be one of built-in sites.
Quote:
If the plugin did use the API then the limit would be 1 request per second per developer key. All users of the plugin would then have to get their own key, otherwise there could only be 1 request per second for all simultaneous users of the plugin.
The idea of every user of the plugin needing their own developer key is pretty bad. Hopefully it won't come to that.

Personally, I'm not interested in working around Goodreads restrictions. The real question on all this is why is the 403 error appearing? I haven't seen anything from Goodreads on restrictions like this. The only references I can see are some problems when using the API. I also haven't seen the error myself. And that includes when I am fiddling with a metadata source plugin and continuously repeating the same request.
davidfor is offline   Reply With Quote