- multiple local tag services:
- you can now add additional local tag services under services->manage services!
- new local tag services will appear in manage tags and tag import options and so on, just like when you add a tag repository
- you can also delete local tag services, but you must have at least one
- the default local tag service created for a new client is now renamed from 'local tags' to 'my tags'. any existing user with their local tag service called 'local tags' will be renamed on update to 'my tags'
- ptr migration:
- the ptr has been successfully migrated to user management! hydrus dev is no longer involved in running or administering it. the old bandwidth limits are removed! it has the same port and access key, but instead of hydrus.no-ip.org, it is now at ptr.hydrus.network
- on update, if you sync with the ptr, you will get a yes/no asking if you want to continue using it at the new location. on yes, it'll update your server's address automatically. on no, it'll leave it as-is and pause it. if you still have a connection to my old read-only file repo, that will be paused
- changed the auto repo setup command to be _help->add the public tag repository_. it points to the new location
- as repo processing and related maintenance is now nicer, and secondarily since bandwidth limits are less a problem for the ptr specifically, the default clientside hydrus bandwidth limit of 64MB/day is lifted to 512MB/day. any users who are still on the old default will be updated
- updated the help regarding the public tag repository, both in general description and the specific setup details
- a copy of the same sanitized and frozen PTR db used to start the new PTR, and convenient tag archives of its content, are now available at https://mega.nz/#F!w7REiS7a!bTKhQvZP48Fpo-zj5MAlhQ
- the rest:
- fixed a small bug related to the new 'caught up' repository mechanic for clients that only just added (or desynced) a repository
- rewrote the tag migration startup job to handle specific 'x files' jobs better--they should now start relatively instantly, no matter the size of the tag service
- on 'all known files' tag migrations, a startup optimisation will now be applied if the tag service is huge
- fixed the tag filter's advanced panel's 'add' buttons, which were not hooked up correctly
- the internal backup job now leaves a non-auto-removing 'backup complete!' message when finished
- on update, server hydrus repositories will collapse all their existing content timestamps to a single value per update. also, all future content uploads will collapse similarly, meaning all update content has the same timestamp. this adds a further layer of anonymity and is a mid-step towards future serverside db compaction (I think I can ultimately reduce server.mappings.db filesize by ~33%). if you have a tag repo with 10M+ mappings, this will take some time
- hydrus servers now generate new cert/key files on boot if they are missing. whenever they generate a new cert/key, they now print a notification to the log
- misc help fixes and updates, and removed some ancient help that referred to old systems
- corrected journalling->journaling typo for the new experimental launch parameternext week
The PTR work took much longer than I expected, and I was unable to get to modified date or file maintenance improvements, so I will have a re-do for those next week. For the ongoing tag work, I will start work on updating the tag 'censorship' system, which is still running on very old code, to more of a 'don't show these tags in places x, y, z', and see about a related database cache to speed up various sibling/display tag choices.
This week was a little bonkers and I fell behind on messages. I am sorry for the delay and will put some time aside to catch up when I can. I think my immediate busy period is done for a bit (although we'll be back to it for the wx->Qt conversion in mid-October), so I'll be grateful to take it a bit easier for a while.