Thread: Goodreads retiring API
View Single Post
Old 12-14-2020, 08:53 PM   #11
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
Just to be clear:

The Goodreads Metadata Source plugin does not use the Goodreads API. It mainly scrapes the page but does use a search API. This is the same as used by the GR for searches. It will not be affected by the API being removed.

The Goodreads Sync plugin makes heavy use of the API. It would be very broken if the API is removed. But, it will keep working until then. It already has a developers key and that should keep working. If the API is removed, all function using it would stop working. That would be most of the function. I do not know if it would be possible to rewrite the plugin using scraping instead.
davidfor is offline   Reply With Quote