-
-
Notifications
You must be signed in to change notification settings - Fork 951
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
[NSFW] Sankaku Complex image booru's new IDs #5073
Comments
Posts with alphanumeric IDs are now supported (a416d4c). |
Thanks a bunch, that did the trick. |
Could you also please add a directory and file template field for the new post IDs? |
I can't figure out how to do this in general. I would have thought and hoped that these new IDs can somehow be gotten by converting an existing value (numeric ID, MD5) to another format/base, but that doesn't seem to work. New IDs are all 11 characters long and in base 62 (ASCII letters and digits) from what I can tell. We could obviously just take the given ID for post URLs, but it would be missing for everything else like tag searches. |
So I figured out how to get alphanumeric IDs (34a4ddc, |
https://forum.sankakucomplex.com/t/converting-between-legacy-numeric-new-alphanumeric-post-ids/48568
The admin wrote:
|
@mikf since the id is not |
It is possible to compare |
Since a few days or weeks or so, the Sankaku image booru changed their IDs from purely numeric to alphanumeric (among others apparent changes to their API). Downloads now sometimes fail with various errors or do succeed, but with nonsensical IDs. Here are a few examples:
An attempt to download posts with containing more... extreme content throws the following error message, even though I do have a premium account and could view these kinda posts in the browser without problems:
Another post with extreme content throws the following error:
The text was updated successfully, but these errors were encountered: