-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
MangaDex API 5.0 #1535
Comments
The web interface went live today, it's a bit slow and may fail to load at times due to the insane pressure but seems to work. Old IDs like |
A few changes to the old behavior:
and it does not auto-translate legacy IDs to new IDs (yet) |
It seems to work great, though I had to cancel it almost right away since my archive is of course using the legacy IDs. Is this something that will be addressed or should I just begin manually converting the IDs in my archive? Also it seems like setting
EDIT: It seems now nothing works, or only select titles... Quite unstable :D |
It doesn't appear to be is possible to convert new to old, only the other way round. There is
Your example manga doesn't have any chapters in English, hence nothing is returned. |
I was more thinking of automating converting all my old entires to the new format, since I have ~29k mangadex entries in my archive, it'll take a while to go through by hand. But I suppose I'll look into making a script to automate it :P EDIT: https://github.com/kattjevfel/scripts/blob/master/convertmangadexIDs.sh crude but very much functional. |
Spawn a new ChapterExtractor for each individual chapter instead of handling them directly with a MangaExtractor. Doing it that way broke too many features like --chapter-filter, --chapter-range, --zip, etc.
Added the ability to download chapters from an account's follow feed (1197ee2) and the for that required ability to login (07c8adb). |
Hello around, I'm panda__________ dev for MangaDex API. I'm coming around to know if you could use a clean User-Agent when requesting the MD API ? We had some occurrence of a guy using your library to update the manga he's reading and since we saw a old Firefox UA, we tough it was malicious and banned him. He replied to the ban explaining that he was using this library.
There is a zip archive with all the legacy mapping ids available on the MangaDex Discord on channel #dev-talk-api Also if you need any help ask in that channel, I'll be glad to help you out :) |
Sure, would something like
Version 78.0 is the latest ESR release. The next one will be 91.0 on August 10th. |
Sounds perfect 👍 |
Should this User-Agent header also be used for file downloads, or is it enough to use it only when querying the API? |
Both would be awesome :) |
Done (dfe1f49) |
Thanks ! 🎉 |
Is there anything still on the old API? Otherwise I'll close this issue. |
Everything has been moved to the new API, so yes, this should be closed. |
As of yesterday MangaDex has opened their API again after the attacks. It's in an open beta and read-only, but most of the features that gallery-dl might be interested in is there.
Announcement: https://mangadex.org/index.html
API docs: https://api.mangadex.org/docs.html
The text was updated successfully, but these errors were encountered: