Replies: 1 comment 1 reply
-
|
This is already possible with the Set it to |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
This might be better placed in the Q&A section, but I figured I'd post it in Ideas as I think it qualifies as a feature request?
I've recently been digging more deeply into the gallery-dl project in order to better format directories and files to my personal liking. My current setup includes a JSON config that defines keys such as
base-directory,directory, andfilenamewith some mix of definitions at the global scope and in individual extractors and even extractor subcategory scopes. I've been utilizing the wonderful commandline option-K --list-keywordson url patterns to help with formatting the names for my directories and files.Without getting too far into the weeds, I've set up my directories generally to follow a structure like:
This directory structure relies on being able to capture that username of the user whose page I'm extracting data from. So far this hasn't posed any problem for downloading galleries, scraps, timelines, posts--things where the user themselves have submitted the content. However when we get to downloading favorites, or in the case of Bluesky, likes, we have an additional hurdle to overcome. The extractor is now downloading posts that have a user or author that is different from the user supplied in the original URL (the one whose likes we are extracting). In the case of every other extractor I've used, the code has handily supplied keywords for the "favorites user" as well as the "submission or post user". In the case of the BlueskyLikesExtractor, no such keywords currently exist for that "favorites user."
While I have a decent understanding of python code, I'm simply out of my depth as far as attempting to branch the repository and make my own changes to add this functionality in.
I've looked at the codebase and have navigated all the way to the BlueskyLikesExtractor class. It currently overrides one function from its parent class
def posts(self)where it returns, to the best of my knowledge, pythonic generators for post iteration. If I had to guess, one would have to wrap another generator around this to add the required information into the posts, but I'm not quite sure how to acquire this information nor how to properly package it in the post such that it gets exposed as usable keywords.I was wondering if 1) this was a good idea to add in the first place and if so 2) if some savvy folks might be able to help me figure out how to make it happen!
Beta Was this translation helpful? Give feedback.
All reactions