cinnamon-rolls / hydrus-tag-linter Goto Github PK

User's should be able to assign actions to keys independently of rules.

Currently, actions are defined in the rule file, which requires that the user tweaks a pre-existing rule or creates a phony-rule to get special functionality.

Analogous to and inspired by: hydrusnetwork/hydrus#513

Note: The terms 'action' and 'shortcut' are equivalent, and 'rules' = 'filters'

Currently, every modification to a file is submitted to Hydrus as it happens, which makes undoing or abandoning your changes a little difficult.

If an action does not 'resolve' an issue, then it should not submit to Hydrus until the user moves away.

This might be a major pain to implement, and I don't know if there's a whole lot of demand at the moment, so this would be on the backburner for now

I'm running this on my remote VM running Ubuntu and use Tailscale to use it with my home install of Hydrus. After pip installing flask and hydrus-api and then editing run.sh, I run it and get the following errors:

~/hydrus-tag-linter$ ./run.sh
Traceback (most recent call last):
  File "/home/user/hydrus-tag-linter/__main__.py", line 3, in <module>
    import tag_linter.hydrus_util as hydrus_util
  File "/home/user/hydrus-tag-linter/tag_linter/hydrus_util/__init__.py", line 1, in <module>
    import hydrus
ModuleNotFoundError: No module named 'hydrus'

Display the Sha256 hash somewhere easily copyable to look up in the client with. Some images might be a bit dubious but looking them up in Hydrus for the full set of tags and associated URLs could provide further context to clear up confusion.

Currently, it will assume that my tags is a valid tag service but we all know that isn't necessarily true...

I want to add a drop down thing to specify the tag service but I'm tired and don't want to forget to do that

An option to automatically archive files as you go through them in the filter. There should still be the delete action (though in this case it should allow you to make tag actions afterwards) and a keep in inbox action.

Give feature requests / enhancements the 👍 reaction if you support them or want to see them added

This helps me gauge what's really important and set priorities accordingly

Please upvote your own feature requests... unless you're playing Devil's Advocate for some reason?

This is identical to how things go on the Hydrus Network issue tracker, see: hydrusnetwork/hydrus#260

The Helicopter Parent rule template cannot work as intended until a feature request for Hydrus is resolved: hydrusnetwork/hydrus#921

For now, you will have to use the add_children field and add each child manually.