I had a mixed week. I was a bit short on work time, but there are some bug fixes, including some more logic/label fixes in my new date calculation code, and quality of life improvements, such as your recent petition 'reasons' now being remembered in the manage tags/siblings/parents dialogs and easier column-size reset for multi-column-lists.

The release should be as normal tomorrow.

I don't suppose there'd be any interest in making it possible to store media in a blob table in the database?

That requires some tuning to retain good performance (mostly related to the in-memory cache size), but it'd make backing up a lot easier and partial/incomplete files from crashes and other annoyances would be gone. SQLite (https://sqlite.org/c3ref/blob_open.html) can do incremental IO in blobs (so can others) and Python (https://docs.python.org/3/library/sqlite3.html#sqlite3.Connection.blobopen) actively supports it.

I had an ok week. I fixed several bugs (including a really bad one related to deleting inc/dec rating services), added a couple unusual features like jpeg subsampling detection and File URL redirects, and updated several core libraries (e.g. Qt) for all users.

The release should be as normal tomorrow.

I had a decent week working on a bunch of different stuff. There's some bug fixes, quality of life improvements, and more work on timestamps--now you can import/export them with sidecars, merge some in the duplicates system, and store timestamps before 1970.

The release should be as normal tomorrow.

Is there way for nitter importer to apply post date as file metadata date and if it is possible for multiple images in one tweet to have relationship between each other?

How could I set Hydrus to download the entirety of e621? I'm new to Hydrus but want to backup the site due to how much seems to get removed from it

Database is locked after my pc was force shutdown yesterday. I have a backup from yesterday, but ideally, I'd like to restore all the changes I made after creating the backup. Any way to fix this?

I changed to a new PC and am trying to move my hydrus database/files to the new computer from backup. I want the contents of the database on a secondary drive while the program is on my main drive. I followed the help page to migrate the database location to my secondary drive (https://hydrusnetwork.github.io/hydrus/database_migration.html#intro). But, now I can't import my backup because it says my "database is stored in multiple locations." But there's only 1 location in "migrate database" window - the new location on my secondary drive that I specified. How can I import my backup to the database?

Hello
I lost my db, and so my backup is a few weeks old. all my files were on another drive.
how do I get the db to search through its client_files and import or find files not in the db?

I've been head-down on a rewrite of the timestamp management system (for editing import, archived, modified etc.. times), and while the work has gone well, I am not done yet. I only have some simple UI for editing a handful of timestamps, but I want full editing of all of them, and ideally sidecar and API support too. Therefore, there will be no release tomorrow--I'll work instead.

v523 should be on the 12th of April. Thanks everyone!

I had a great couple of weeks overhauling how the program manages file timestamps. Most of the work was boring behind the scenes stuff, but the upshot is a new dialog now lets you edit every file timestamp--import time, deletion time, archive time, modified time, and last viewed time, and I've added 'system:archived time' for searching. There's also an important bug fix for file deletion reasons and some quality of life improvements.

The release should be as normal tomorrow.

I had a good week working on some slightly advanced, more technical things. I added http header management to the Client API, added file notes to import and export sidecars, and fixed some bugs.

The release should be as normal tomorrow.

do you plan on adding yt-dlp support? i tried to import a video along with its metadata and description using the "--write-description --write-info-json" commands, but hydrus doesn't know what to do with the json files
had to do everything manually

I had a good week. I cleaned some code and fixed a bunch of small issues in tag parsing, tag display, file import options, file delete reasons, and file viewing statistics.

The release should be as normal tomorrow.

>>1472
I would like to have some support. I plan to have an 'executable manager', which will let us define certain exe paths and arguments that we can send certain URLs to, e.g. 'this is a twitter video, send it to yt-dlp'.

Having nice note support in that would be a potentially significant extension, though--it would probably start off just as single files, no extra sidecars.

I do have a fairly clever manual sidecar system now, which should be able to deal with simple JSON files, but it doesn't support notes yet (just tags and URLs). You might like to have a play with it nonetheless, in prep for when I add notes, which I would like to do fairly soon. Try importing your video from your hard drive and play around with the 'sidecar' tab after hitting 'add tags/urls with the import'. If you can rename the json files to be very similar to the video file, that would help.

Help page here: https://hydrusnetwork.github.io/hydrus/advanced_sidecars.html

I had a good week. I mostly worked on bug fixes and quality of life, particularly on the tag autocomplete interface.

The release should be as normal tomorrow.

test

I managed to get a first version of an increment/decrement integer rating service working, and I'm happy with it, but it needs more polish and my day tomorrow is crazy, so I'm putting off the release a week to finish it up and get more things done.

v519 should be on the 8th of March. Thanks everyone!

I had a good couple of weeks. There's some small bug fixes and quality of life, improved server janitor tools, and a new 'rating' service that lets you count with clicks.

The release should be as normal tomorrow.

I had an ok week. There's a mix of small fixes, the addition of hours:minutes to system:time calendar predicates, and a neat overhaul of how autocomplete tag search presents its pre-fetch results on slow searches.

The release should be as normal tomorrow.