Version 666

flaming_skull.gif

Author: hydrusnetwork

README.md

@@ -6,7 +6,7 @@ Hydrus supports various filetypes for images, video and audio files, image proje
 
 I am continually working on the software and try to put out a new release every Wednesday by 8pm EST. Executable releases are available for Windows and Linux, but the program is in python, so you can also just run it straight from the source code in Windows, Linux, or macOS. I am not active here on github, but I welcome feedback of any sort on other channels and will try to get back to any pings every Saturday. 
 
-The client can download files and parse tags and other metadata from a number of websites, including the popular imageboards and boorus, and some gallery sites. It can be extended to download from more locations using easily shareable user-made downloaders. It can also be set to 'subscribe' to any gallery search, repeating it every few days to keep up with new results.
+The client can download files and parse tags and other metadata from simple websites using easily shareable user-made downloaders. It can also be set to 'subscribe' to any gallery search, repeating it every few days to keep up with new results.
 
 The program's emphasis is on your freedom. You control everything, and the program never phones home. In the same way, it is quite an advanced program, and not a beautiful one, so it isn't for everyone. Try it out, see if you like it!
 

docs/PTR.md

@@ -60,7 +60,7 @@ These are a mix of standard practice used by various boorus and changes made by
 
 If you are looking to help out by tagging low tag-count files, remember to keep the tags objective, start simple by for example adding the characters/persons and big obvious things in the image or what else. Tagging every little thing and detail is a sure path to burnout.  
 If you are looking to petition removal of tags then it is preferable to sibling common misspellings, underscores, and defunct tags rather than deleting them outright. The exception is for ambiguous tags where it is better to delete and replace with a less ambiguous tag. When deleting tags that don't belong in the image it can be helpful if you include a short description as to why.  
-It's also helpful if you sanitise downloaded tags from sites with tagged galleries before pushing them to the PTR. For example Pixiv, where you can have a gallery of multiple images, each containing one character, and all of the characters being tagged. Consequently all images in that gallery will have all of the character tags despite no image having more than one character.
+It's also helpful if you sanitise downloaded tags from sites with tagged galleries before pushing them to the PTR. For instance, some image sets will be tagged with every character who appears anywhere in the set on all files. This would be appropriate for a single collected CBZ of the chapter or story, but not for individual files.
 
 ### Siblings and parents
 When making siblings, go for the closest less-bad tag. Example: `bad_tag` -> `bad tag`, rather than going for what the top level sibling might be. This creates less potential future work in case standards change and makes it so your request is less likely to be denied by a janitor not being entirely certain that what you're asking is right. Be careful about creating siblings for potentially ambiguous tags. Is `james bond` supposed to be `character:james bond` or is it `series:james bond`? This is a bit of a bad example due to having the case of the character always belonging to the series, so you can safely sibling it to `series:james bond` since all instances of the character will also have the series, but not all instances of the series will have the character. So let us look at another example: how about `wool`? Is it the material harvested from sheep, or is it the Malaysian artist that likes to draw Touhou? In doubtful cases it's better to leave it as is, petition the tag for deletion if it's incorrect and add the correct tag.

docs/adding_new_downloaders.md

@@ -6,16 +6,27 @@ title: Adding New Downloaders
 
 ## all downloaders are user-creatable and -shareable { id="anonymous" }
 
-Since the big downloader overhaul, all downloaders can be created, edited, and shared by any user. Creating one from scratch is not simple, and it takes a little technical knowledge, but importing what someone else has created is easy.
+The client starts with no downloaders, but all downloaders can be created, edited, and shared by any user. Creating one from scratch is not simple, and it takes a little technical knowledge, but importing what someone else has created is easy.
 
-Hydrus objects like downloaders can sometimes be shared as data encoded into png files, like this:
+Many Hydrus objects can be shared as data encoded into png files, like this:
 
-![](images/easy-import-realbooru.com-search-2018.09.21.png)
+![](images/artbooru 2026-03-29.png)
 
-This contains all the information needed for a client to add a realbooru tag search entry to the list you select from when you start a new download or subscription.
+This simple png is encoded with data that hydrus can read. It contains all the information needed for a client to add an [artbooru](https://artbooru.com) tag search entry to the list you select from when you start a new download or subscription.
 
-You can get these pngs from anyone who has experience in the downloader system. An archive is maintained [here](https://github.com/CuddleBear92/Hydrus-Presets-and-Scripts/tree/master/Downloaders).
+You can get these pngs from anyone who has experience in the downloader system. An archive of more is maintained by users [here](https://github.com/CuddleBear92/Hydrus-Presets-and-Scripts/tree/master/Downloaders).
 
-To 'add' the easy-import pngs to your client, hit _network->downloaders->import downloaders_. A little image-panel will appear onto which you can drag-and-drop these png files. The client will then decode and go through the png, looking for interesting new objects and automatically import and link them up without you having to do any more. Your only further input on your end is a 'does this look correct?' check right before the actual import, just to make sure there isn't some mistake or other glaring problem.
+To 'add' the easy-import pngs to your client, hit _network->downloaders->import downloaders_. A little image-panel will appear. You can:
 
-Objects imported this way will take precedence over existing functionality, so if one of your downloaders breaks due to a site change, importing a fixed png here will overwrite the broken entries and become the new default.
+- Drag and drop a png file from a folder
+- Drag and drop a (full-size) png from your web browser
+- Click the image to open a file selection dialog for the png
+- Copy the png bitmap ('Copy image'), file path, or raw downloader JSON into your clipboard and then hit the paste button
+
+The client will then decode and go through the png, looking for interesting new objects. It gives you a 'does this look correct?' check, just to make sure there isn't some mistake or other glaring problem, and then automatically imports and links everything up.
+
+## updates
+
+Objects imported this way will try to take precedence over existing functionality, so if one of your downloaders breaks due to a site change, importing a fixed png here will generally overwrite the broken entries and become the new default.
+
+Behind the scenes, downloaders are actually several different objects that are loosely connected. If successive updates break something or you are left with duplicate entries because of a rename, have a look around _network->downloader components_ and you will see what is actually imported by these pngs. The best solution is to delete any 'GUGs' and 'parsers' with names related to your downloader so you have a fresh slate and then try a fresh import once more.