full list

- misc:
- fixed a bug in the new taglist backend that would sometimes error out in a paint event(!) on display initialisation or data changes for some clients
- improved the taglist 'tag' vs 'copyable string' copy/select/action menu logic. e.g. 'namespace:*' is copyable, but it is not a tag
- thread watchers now skip/clean up unactioned check log entries (this usually happens when a check is due during network traffic paused, queueing the job, and then the client shuts down). if you noticed some odd perpetually 'pending' checkers in last week's status overhaul, this was the issue, and they should clean up. this was always harmless, just revealed with new status code
- thread watchers now record serious network error detail in the check log
- thread watchers are quicker about notifying UI on checker log changes
- thread watchers now report 'time delta' as their simple status when waiting to check, rather that 'checking in (time delta)'. let's see if that fits better in the columns
- fixed an issue where several dialogs with multi-column lists would reset their 'last column' size to the minimum three characters on the next load if they did not receive certain size events while they were open. you should just have to fix any broken dialogs once and you'll be good again
- I believe I also improved/fixed the issue of dialogs with multi-column lists sometimes shrinking by a few pixels every open/close
- the 'we just woke from sleep' detection is now more aggressive. it should now detect a wake after sleeps as short as 60 seconds (down from 5 mins). let's see if we get any false positives during maintenance or other busy periods
- if you have a complicated database (one stored across multiple locations), the 'database' menu now has a label in place of the simple database's 'backup/restore' commands
- improved the 'directory is writeable-to' check used in the program. on windows, due to some python tempfile weirdness, this was actually hanging on Program Files.
- improved the related 'is db dir writeable-to' test in the boot script. if you try to run the program on a custom non-writeable db directory, the crash error should now be nicer, and running a straight client.exe installed to 'Program Files' should now auto-place your db in your user folder, no complaints, like the macOS App
- corrected 'writable' typo to 'writeable' across the program lmao
- fixed the new header links in the FAQ file, which I accidentally messed up
- started work on updating neighbouring .txt tag sidecar export. it isn't ready yet, but it will add tag filters and tag display type to sidecar export with easier expansions in future, and fold it nicely into Export Folders
- improved some log-off detection + clean shutdown code, but I do not yet have nice multiplatform support
- .
- filetypes:
- the stacked expand/collapse checkbox widget that lets you select filetypes now always starts collapsed. also, some 'partially clicked' logic is improved when you click through filetype group
- application/clip (clip studio paint) files are now supported! thanks to a user for helping out here
- just a side note: I looked into animated webp support this week, but it turns out decoding support is rarer than encoding. my normal and fairly new FFMPEG can't reliably render subsequent frames or figure out duration, nor can PIL or OpenCV. I think we will simply have to wait for an update on one of their ends

- boring db cleanup:
- wrote a local hashes cache to store hashes for all the files on your disk, much like the tag one. this should speed up all normal searches and other common file lookups in the db
- the raw storage mapping tables are spun off to their own module
- basic file info and inbox is spun off to its own module
- improved and sped up some inboxing file count calculations
- cleaned up some more misc file metadata and inbox code
- improved logic in local tags cache

next week

Some IRL stuff has been eating my time and energy recently. That should be easing up, so I'll be back at network improvements and hopefully some autocomplete improvements for short inputs.

I am crushed for time atm. Sorry for the delays, I will catch up with Endchan thread replies on Saturday.

Help I'm scared

>>982
Often times anti viruses/firewalls don't like hydrus due to its autism code so sometimes you'll have to whitelist it. Some will even ignore your whitelist and still continue to block it. If that happens and you still can't white list hydrus then you'll have to actually summit the program to your anti virus over to their lab and have them white list it. Usually they'll have a section on their site where you can summit false positives.

>>982
>>987
I am very sorry about this. We've had several of these the past weeks. I am not sure what specifically is doing it. My code is unusual, unsigned, and packaged with duct tape and pyinstaller, and I do network and file stuff and a little encryption code, so I guess some libraries and calls look suspicious. So far, every one of these has been a false positive. I appreciate the notice--if ever one of these is real, I want to know asap.

The 'this program is dangerous and executes commands from an attacker' is a new one they have been showing. Maybe they just started recognising the client api, and it looks like a virus command server?

The warnings usually go away after a couple of weeks once new anti-virus definitions roll out, if you would prefer to wait. Or you can just whitelist the exe/directory or whatever. If you know python, the nuclear solution for this is to run from source, but if you aren't familiar with python, it would be a whole bunch of work.

https://hydrusnetwork.github.io/hydrus/help/running_from_source.html

I had an ok week. I fixed the tumblr downloader, which accidentally broke recently, and some lagging text display in the download UI, added show/hide options for the new tag parents in the manage tags dialog (along with some other quality of life), and made it so short tag autocomplete inputs can match odd characters, so 'a' will give a result of '/a/'.

The release should be as normal tomorrow.