https://youtube.com/watch?v=-ZdLbiF9gCo
windows
zip: https://github.com/hydrusnetwork/hydrus/releases/download/v435/Hydrus.Network.435.-.Windows.-.Extract.only.zip
exe: https://github.com/hydrusnetwork/hydrus/releases/download/v435/Hydrus.Network.435.-.Windows.-.Installer.exe
macOS
NEW app: https://github.com/hydrusnetwork/hydrus/releases/download/v435/HydrusNetwork-v435.dmg
OLD app: https://github.com/hydrusnetwork/hydrus/releases/download/v435/Hydrus.Network.435.-.macOS.old.-.App.dmg
linux
tar.gz: https://github.com/hydrusnetwork/hydrus/releases/download/v435/Hydrus.Network.435.-.Linux.-.Executable.tar.gz
I had a good week. I continued last week's server work and have a macOS Big Sur build available for testing.
new macOS build
This was delayed far longer than I wanted, but I think I have it figured out now. Thanks to work from Suika and ReAnzu on github figuring out the script, the macOS build is now put together on github itself, on Catalina. This new build thus works on Big Sur, and should generally have less compatibility jank on any newer macOS machine. I have included my old 10.12-built release as well today, just in case I messed something up, but if you are a macOS person, please give the new one a try and let me know how you get on.
Assuming this works out ok for the majority of people, I'll be moving to it as the official macOS build. Anyone who is still on an old macOS will have to run from source to stay updated with hydrus. The new release is just out of testing, so I'll clean up the filename and add the readme.rtf and so on so it looks prettier. I will also explore reducing the size (300MB vs 137MB wew), but I am told this may be unavoidable due to some new macOS thing that bundles both old and new versions of libraries in the App.
editable repository update periods
Just in case, it is probably a good idea to back up your server before you try this!
Hydrus repositories now have an editable update period! This was an oft-requested feature for users running a server on a LAN or between just a few friends, so if this is you, please give it a go. There is a new 'edit options' permission for accounts, which any account with 'manage account types' (admins basically) will inherit on update. If you have this, the 'admin services' menu will have a new 'edit update period' entry, which launches a simple time delta widget where you can change it.
Changes occur immediately. The server will create any updates that are now due, and your client will do a resync to keep up to date with the new numbers, so if you have 'review services' open when you make the change, you should see everything update in realtime. Other clients that sync with the server will catch up with the new check times when they next do their normal sync, unless they too force a resync with the new 'review services' button I added last week.
You can change the update several times, up or down, and it shouldn't be a big deal--the client no longer cares if one set of updates were short or long--so please feel free to play around with this a bit, just don't go crazy with super short or long times. The minimum is 10 minutes, but I recommend you only go down to about 60 minutes if you really want to be that fast, at least as we experiment with this. The system was originally built with 100,000 seconds in mind, so I think super short periods will add overhead bloat over time (not to mention, you only see content after processing, which atm only happens in idle time anyway).