>>5009
As far as I'm concerned, it doesn't feel like this board is overburdened yet.
And -while I don't want to impose on hydrus_dev-, perhaps it might simply be time to have a simple add-on manager in Hydrus once there are many scripts, repository URLS, tag repositories, scrapers, services and IPFS shares to keep track of?
Just something that pulls JSON files containing update information from URLs and then lets people add & maintain tag archives, IPFS and hydrus shares, services, scripts and so on. (Hydrus could already ship with a "main" add-on server, and whoever else has, like, a shared list of tag archives and IPFS shares could provide alternative URLs without having to bugger hydrus_dev).
It should make life easier with maintaining up-to-date everything, and kinda avoid endless (re-)instruction threads about how to add this or that thing.