birthday and year summary

The first non-experimental beta of hydrus was released on December 14th, 2011. We are now going on twelve years.

Like many, I had an imperfect 2023. I've no complaints, but IRL problems from 2022 cut into my free time and energy, and I regret that it impacted my hydrus work time. I had hoped to move some larger projects forward this year, but I was mostly treading water with little features and optimisations. That said, looking at the changelog for the year reveals good progress nonetheless, including: multiple duplicate search and filter speed and accuracy improvements, and the 'one file in this search, the other in this search' system; significant Client API expansions, in good part thanks to a user, including the duplicates system, more page inspections, multiple local file domains, and http headers; new sidecar datatypes and string processing tools; improvements to 'related tags' search; much better transparency support, including 'system:has transparency'; more program stability, particularly with mpv; much much faster tag autocomplete results, and faster tag and file search cancelling; the inc/dec rating service; better file timestamp awareness and full editing capability; the SauceNAO-style image search under 'system:similar files'; blurhashes; more and better system predicate parsing, and natural system predicate parsing in the normal file search input; a background database table delete system that relieves huge jobs like 'delete the PTR'; more accurate Mr. Bones and File History, and both windows now taking any search; and multiple new file formats, like HEIF and gzip and Krita, and thumbnails and full rendering for several like PSD and PDF, again in good part thanks to a user, and then most recently the Ugoira and CBZ work.

I'm truly looking forward to the new year, and I plan to keep working and putting out releases every week. I deeply appreciate the feedback and help over the years. Thank you!

next week

I have only one more week in the year before my Christmas holiday, so I'll just do some simple cleanup and little fixes.

Hey, my dev machine died today (its GPU actually caught fire when I turned it on!), so no release tomorrow. I'll get a new machine over the holiday and restart for the new year, meaning v557 will be on January 3rd.

Thanks everyone, and 𝕸𝖊𝖗𝖗𝖞 𝕮𝖍𝖗𝖎𝖘𝖙𝖒𝖆𝖘!

I had a good week back after the holiday. I fixed some bugs and improved some system:hash predicate parsing.

The release should be as normal tomorrow.

I had an ok week. I fixed some bugs and wrote a system to force a file to be considered a certain filetype.

The release should be as normal tomorrow.

I had a good week. There's some cbz/Ugoira follow-up, nicer system:time parsing, much better boot error-handling, and some improved UI quality of life.

The release should be as normal tomorrow.

I had an excellent week. I fixed some important bugs--including a subscription/watcher start bug, and even more damaged-file rendering issues--figured out transparency for APNGs, and wrote basic recognition and thumbnail generation for CBZ and Ugoira files.

The release should be as normal tomorrow.

I had a great week. I fixed a bunch of bugs--including the recent false-positive I/O error we saw when checking certain gifs for transparency--improved some quality of life, and made the slideshow work much better with videos.

The release should be as normal tomorrow.

I had a great week. I fixed some bugs and added 'system:has transparency' search.

The release should be as normal tomorrow.

Has this been fixed yet? Last time I asked was over a year ago.
These don't show up in the dupe filter unless I manually disband the dupe group, but how did they obtain it in the first place?
Happens regularly but not that often to be a major nuisance.

I had a good week. I ended up working on technical improvements, fixing some issues with deleted file tracking and exposing multiple maintenance timings for customisation. There is also a variety of optimisation that should slightly de-lag very heavy clients.

The release should be as normal tomorrow.

>>1550
I am sorry, I cannot remember this well. Can you say more what is not working right here? It looks like you have a couple of files set as duplicates, and they are showing up in the search result. Have you never set these as duplicates, and they seem to have spontaneously duped together?

Or do you use the duplicate filter, and have seen files like this, but always set 'and delete the other', and so it is odd that this has happened and they remain in your 'my files'? Is that why there is only one pair when you do this (normally expansive) search?

If it is strange that these files are not showing up in the duplicate filter--that is intentional. The duplicate filter only shows potential duplicate pairs. Once those potentials are processed in the filter, they become like this pair--set as duplicates.

As a side thing, I am planning out a thumbnail expansion to give all thumbnails quick knowledge to all of their current file relationships, which should make some of these menus a bit cleaner and more naturally human (e.g. saying 'these two are duplicates' explicitly, rather than having to infer it from everything else going on). Unfortunately, I have to fetch this data on a per-file basis from the database on every right-click, so I can't do all the calculations I'd like.

>>1551
So I avoided using the dupe filter altogether during all this time to make sure it has nothing to do with it and while the frequency of these weird dupes reduced, they continue to appear. Either way, I never encounter them in the filter before they show up here and I always delete the dupes I find.
These weird dupes differ only in compression as they usually involve an image imported (from API) a long time ago and its copy retrieved recently, probably because the server's compression format being updated. They have multiple image urls, some are matching, others different between the two.

So basically these are images that got assigned the same dupe group without going through the filter where I would have deleted one. Instead I have to look for these stealth dupes in a special search query.

>>1558
Thanks. That's very strange behaviour. As far as I know, the client will only ever apply a duplicate pair relationship if you work through the duplicate filter or apply it manually on a selection of thumbnails, either through that menu or with a shortcut. I have no auto-dupe tech yet.

As a side thing, there is some transitive behaviour, so if A is a dupe of B, and you then set B to be a dupe of C, then A will be duped to C also, but of course this needs the triggering B->C relationship set in the first place, which it sounds like you are not doing. Also, duplicate relationships will survive files being deleted and re-imported, if that could be happening here.

If you can figure out a way to reliably reproduce this situation, or you gather any other information that would help me track this down, please let me know.

>>1554
Where do users share their downloaders? Kemono has been broken but i'm sure someone would have fixed it already.

I had a great week fixing a ton of bugs. As well as a variety of small stuff, there's also a fix for the Mr Bones and top-right media viewer hover crashes that PyQt users have seen this past week.

The release should be as normal tomorrow.

>>1555
Try here, looks like one as of two weeks ago:
https://github.com/CuddleBear92/Hydrus-Presets-and-Scripts/tree/master/Downloaders

>>1556
Thanks, it works.

I had a good week. I fixed several bugs, some important, and reworked 'scale to fill' thumbnails.

The release should be as normal tomorrow.

I had a good week. I overhauled the thumbnail shortcuts system, fixed some bugs, and improved some quality of life.

The release should be as normal tomorrow.