-
-
Notifications
You must be signed in to change notification settings - Fork 939
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Suggestion] EH JSON from API #1325
Comments
"archiver_key", "category", "thumb", "uploader" "rating", and "torrentcount" from what I can tell. And the total file size is only an rough estimate. Everything else just has a different name. I wouldn't mind adding an option to (also) get the metadata from the API, but that's 1 extra HTTP request which might not be necessary.
Use |
That would also work, thank you very much!
Also if there are torrents it gives you the hash,name, torrent+file size for them. Additionally the upload time is missing seconds, which doesn't matter I guess. On a side note, about the current gallery-dl JSON: what is the "subcategory" entry referring to? |
to select between gallery metadata from 'api' or 'html'
now that we are adding more info from the EH-api, its possible to redownload only the metadata for those ? |
- gallery_id -> gid - gallery_token -> token - title_jp -> title_jpn - visible -> expunged - gallery_size -> filesize - count -> filecount Also changes the function of the 'metadata' option. It is now boolean and causes extra data fields from the API to be added instead of completely replacing the data from HTML when activated.
Extracting a @hellupline I recommend |
btw, I created this gist to upgrade metadata files to use |
Would it be possible to add an option to let the JSON data written for E-Hentai downloads be from their official API? https://ehwiki.org/wiki/API
The current implementation sadly leaves out a lot of data, although it provides information about Parent/ visibility which the API doesn't.
Also
gallery-dl -j $gallery_page
option for EH galleries starts going through all the pages instead of just showing the one for the requested URLThe text was updated successfully, but these errors were encountered: