Nandaka / DanbooruDownloader

*booru image downloader
http://nandaka.devnull.zone/
390 stars 38 forks source link

Legacy API removed from Danbooru; no longer working #108

Open JMM72 opened 7 years ago

JMM72 commented 7 years ago

A very recent update in Danbooru removed the Legacy API which DanbooruDownloader is using right now. This makes DD unable to download from Danbooru (sad irony). Other providers work, tested with Sankaku Complex, Konachan, Gelbooru and Yande.re for a start (since these are still using the Legacy API).

For now it's not sure if they will bring it back again (one serious request for IQDB.org). In any case, it's mentioned it has been deprecated for years and everyone should be using the current API.

Forum post about the issue, look at about the bottom of the page.

Edit: I was able to download images from Danbooru again, but without any tag information. Since the main reason I use DD is for its naming features, it's kind of useless to me, but maybe someone will find this helpful until the current situation is fixed. Edit DanbooruProviderList.xml so the first entry for Danboru looks like this (only 4 lines change btw, Preferred and QueryStringXXX):

<DanbooruProvider>
    <Name>danbooru</Name>
    <DefaultLimit>20</DefaultLimit>
    <HardLimit>1000</HardLimit>
    <Preferred>Json</Preferred>
    <QueryStringXml>/posts.xml?%_query%</QueryStringXml>
    <QueryStringJson>/posts.json?%_query%</QueryStringJson>
    <QueryStringHtml>/posts?%_query%</QueryStringHtml>
    <Url>http://danbooru.donmai.us</Url>
    <UserName />
    <Password />
    <LoginType>Anonymous</LoginType>
    <PasswordSalt>choujin-steiner--%PASSWORD%--</PasswordSalt>
    <PasswordHash />
    <!-- 2016-10-07 19:00:29 -->
    <DateTimeFormat>yyyy-MM-dd HH:mm:ss</DateTimeFormat>
    <BoardType>Danbooru</BoardType>
    <TagDownloadUseLoop>true</TagDownloadUseLoop>
</DanbooruProvider>

Updating tags shouldn't work, I'm not even trying.

Nandaka commented 7 years ago

Looks like they enable the old api again.

JMM72 commented 7 years ago

Yes but it's a temporal measure. They want to remove access to the legacy API due to resource hog whenever it's used, so updating to the new API should be a priority.

Nandaka commented 7 years ago

Related to #128