/hydrus/ - Hydrus Network

Bug reports, feature requests, and other discussion for the hydrus network.

Posting mode: Reply

Check to confirm you're not a robot
Name
Email
Subject
Comment
Password
Drawing x size canvas
File(s)

Board Rules

Max file size: 350.00 MB

Max files: 5

Max message length: 4096

Manage Board | Moderate Thread

Return | Magrathea | Catalog | Bottom

Expand All Images


Version 434 Anonymous Board owner 04/07/2021 (Wed) 22:51:31 Id: 2275fd [Preview] No. 1042
https://youtube.com/watch?v=f1nvZ74OY_I [Embed]
windows
zip: https://github.com/hydrusnetwork/hydrus/releases/download/v434/Hydrus.Network.434.-.Windows.-.Extract.only.zip
exe: https://github.com/hydrusnetwork/hydrus/releases/download/v434/Hydrus.Network.434.-.Windows.-.Installer.exe
macOS
app: https://github.com/hydrusnetwork/hydrus/releases/download/v434/Hydrus.Network.434.-.macOS.-.App.dmg
linux
tar.gz: https://github.com/hydrusnetwork/hydrus/releases/download/v434/Hydrus.Network.434.-.Linux.-.Executable.tar.gz

I had a great three weeks working on long overdue network updates. Most of the changes this week restore old account management UI for server admins, but there are a couple of fixes and improvements for regular users as well.

The network version goes up to 20 today. Clients and servers can only talk to each other if they are on the same version, so if you want to talk to the PTR, you will want to update at some point. No rush, but if you try to talk to the server on an older client, you will get a polite error message.

regular user stuff

On review services, you can now pause repository account sync, update downloading, and update processing separately. If you don't want to process right now but still want the client to be grabbing update files for later, or you want to pause all service network traffice for a while but still process your backlog, it should now be easy to set up.

I fixed an annoying bug where going from 'random' file sort to one with asc/desc sort order by loading a favourite search would always default the asc/desc to the top value. Guess what hydev's default sort is.

Server administrators can now set messages to accounts. If you get a message, your client should get the update within a day or two, at which point it will appear in a popup box and be viewable on review services.

Server administrators can now set some account types to be user-creatable--no need to mess around with registration keys or access keys yourself, the client can fetch them for you from the server. A new button on the manage services edit panel checks this and can do it for you. I understand the PTR is likely to move to this in future for accounts with sibling and parent petition permissions, since grouping these by account will be useful for janny petition workflow. Having separate accounts for these complicated uploads will also allow better account management (including the above rudimentary messaging) for users who make common errors with sibling or parent submissions.

I believe I fixed a bug in repository processing that caused some newer users to get stuck with siblings and other data that was later deleted. This should not happen again, and I am now planning ways to efficiently fix the problem retroactively. (If you were hit by this and want the non-efficient fix, hit 'reset processing->reprocess content' for the repo under review services).

Some users recently got some scary errors about an invalid repository update file. This was the result of the client becoming confused about which update files it should have for a repository. I am still investigating why this happened, but to fix the immediate issue I have added a maintenance routine (under the new review services->reset downloading) that triggers a full resync of update metadata and delete surplus records. This function will fire automatically in future if the service encounters borked update files of any kind. If you got these errors, please try firing it and let me know how you get on.


Anonymous Board owner 04/07/2021 (Wed) 22:54:16 Id: 2275fd [Preview] No.1043 del
admin improvements

After a very long delay, account management is finally back. If you have permission to modify accounts, the 'modify an account' service admin menu item works again and launches a fully revamped window. You can also launch account modification from manage tags for a particular tag selection, the thumbnail right-click for file repository files, or the petition processing page.

The new window shows better data about accounts, and lets you zoom in on individual ones to see current account type, expiration, banned status, or message. It also shows if you are editing yourself!

The account modifications are: change account type, set/extend/clear account expiration, ban, unban, and the new 'set message'. All modifications now print janny and subject account key to the server log. I removed the old 'superban' (which deleted all that user's content contributions), but it will likely return in future.

The service admin menu also has a new 'review all accounts' entry that lets you see a simple summary list of all accounts, which you can then select for modification.

The manage account types dialog now lets you set up auto-account creation. It works a bit like subscriptions, with a 'account creation velocity' limit of 'x accounts per y time delta', like '10 per day'. This defaults to off obviously, but if you set some account types to auto-create, users will be able to see that in manage services.

future admin improvements

As always, there was much more I wanted to do than could get done. I wasn't able to finish improving petition processing workflow or add custom update duration, a serverside tag filter, or a server message, but I was able to get the important network stuff done I needed for these things. Since incrementing the network version is always such an obstacle, I am confident I will now be able to work on these things in normal weekly work. Please let me know how they work out for you as I roll them out.

full list

(1,700 word changelog this week, please check github or the help)

https://github.com/hydrusnetwork/hydrus/releases/tag/v434

next week

I will catch up with the regular work I missed over the three weeks. I will also try to get optional update duration done for the server. And lastly, I absolutely want to figure out macOS releases that work on Big Sur, which is another thing I have left for too long. The test github build some users have been working on apparently works, so I just have to integrate their script into my own github build routine and, fingers crossed, we should be good.


Release Tomorrow! Anonymous Board owner 04/14/2021 (Wed) 06:47:07 Id: 7cca52 [Preview] No.1044 del
I had a good week. I fixed several bugs and added some quality of life, got a Big Sur build working for macOS users to try out, and for users who run smaller servers on a LAN or between friends, hydrus repositories now support changing their 'update periods'.

The release should be as normal tomorrow.



Top | Catalog | Post a reply | Magrathea | Return