-
-
Notifications
You must be signed in to change notification settings - Fork 976
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
No support for ripping discord rips on kemono.party (feature request) #1940
Comments
@mikf Could you add the channel names into the metadata? |
Slight issue with the implementation. Since channels can have their content updated in any order, the extractor should treat them similarly to subcategories when it comes to the skip option. In other words, currently, when using a skip option like "abort:1", the extractor stops completely when it hits a filename collision, but the desired behavior would be for it to start checking the next channel. |
@mikf I came across another issue. Some artists just post a cdn.discordapp.com / media.discordapp.net URL in chat, which doesn't embed on the kemono.party website, so gallery-dl isn't currently downloading them. |
fixed in bcbf9bc
Which server? I'd like to see an example of that but haven't managed to find one myself. |
I posted it here: |
@ImportTaste |
Ran into a small issue. Aside from what I mentioned here b6443c5#r58549311, sometimes URLs are surrounded with angle brackets |
Apparently |
- extract media.discordapp.*NET* URLs - rewrite media.discordapp.net to cdn.discordapp.com - use a more restricted set of characters for the URL path
@ImportTaste fixed in f1487a3. |
There is no support for ripping discord rips on kemono.party, the discord rips on kemono have a weird layout, so maybe this isn't possible?
Just go here https://kemono.party/artists and on the drop down menu for service pick discord.
The weird way all the images fit on one screen with an endless load more button might be what makes it hard? I dunno.
edit: I don't know how to label this a request, sorry.
The text was updated successfully, but these errors were encountered: