-
-
Notifications
You must be signed in to change notification settings - Fork 995
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
[Site Support Request] inkbunny.net #283
Comments
Now that FA's been done, I really hope IB will be soon |
Any news on this? :) |
No, sorry. |
Understandable, there are better documentations and also better APIs. I've been reading around the docs, doesn't seem that complicated, but it's a bit unconventional. To download someone's favorites or submissions, you have to do a search. Usually there's an endpoint for that, too. While you can search submissions providing a username, you need the userid to get the favorites. But getting your own favorites is easy since your userid is returned at login. Using the search (user's submission, favorites or pool's images) basically means: telling the site you want 100 results and a resultid, repeating the request providing that rid + incrementing a page var. I haven't compared the details but the submission details from the search are limited, so you may want to limit it to returning just the submissions ids. Having submission ids only, like when trying to download a single link, you send a comma seperated list with a maximum of 100 ids to the submission info endpoint ... Only thing to find out is how to get another user's userid the easiest. More or less like that. Hope that sparks your motivation a bit :) |
There's probably still a lot to be done, but here is initial support for |
So the extractor structure in the .conf would look like
after enabling the API box in the site user settings? Or is there anything else you need? |
@biznizz yup, works for me!
|
Have noticed that, when running the user post extractor, the program doesn't run from the latest picture posted, but from seemingly random older picture, then sort of bounce around. It's entirely possible, if your skip value has a low The individual post extractor works fine as far as I'm aware. EDIT: This was tested with the initial dev build before the changes made an hour prior to this posting, just for clarity. EDIT 2: Have tried installing dev build after seeing the commts, then tried running it again. Gallery ripping does not start from the newest image from the top of page 1 (or just newest image if gallery is only one page) like Deviantart or FA, but still starts somewhere else. Ex. if the submission number for the newest image is XXX9380, then ripping the user will start at XXX4328, earlier on the page. It wont start with the oldest image at WWW8922 on the last page either. Very odd behavior. Again, isn't THAT big of an issue, especially if you're ripping the gallery for the first time, but if you use a value of |
Getting detailed submission info via /api_submissions.php reordered the input submissions and sorted them by ID. InkbunnyAPI.detail() now sorts them back and ensures they are returned in their original order. This commit also removes the 'metadata' option and always requests submission descriptions.
Just put everything at the top level, instead of having a separate 'post' object.
Is the |
I hope Inkbunny can be supported
Link to the API
An account you can test to
The text was updated successfully, but these errors were encountered: