So I accidentally a new imageboard

He said he overwrote the pictures.

Well, it seems only the images in the database were thumbnailed (... which makes sense), so I took it as a challenge to add an image downloader to the system. I have a temporary one running and recovering things now - though I can't tell if I'll be able to recover images only found on rule34.xxx. They have stupid urls.

But so far it seems like I'm recovering about an image a second, so that's fine for me.

Recovered all but 108 images! XD

I thought the +/- buttons were for the tag search only. Like how e621 does it, with adding the tag to the current search filter.

Except e621's is halfassed and it's only as good if you are too lazy to type it in yourself. But it isn't keeping track of the current tags like a checklist filter on some store sites. So if you add +tag then -tag they will just cancel eachother out and you'll be left with nothing.

First, try Hydron (written in Go) github.com/bakape/hydron
Then, understand that Hydrus is rapidly prototyped for the last 5 years to support thousands of websites.


Not enough features.


SQLite is always the answer for speed


Looks good


Hydrus Dev is implementing it in the near future


What do you mean by "taxonomies"?

Learn 2 get scripts github.com/CuddleBear92/Hydrus-Presets-and-Scripts
There are also default tag scraping for the major *boorus


Then rewrite the code to use Qt instead of WxPython whiny bitch, or make a CLI if you want things to be fast


Nah, the fanbase is large.


Already implemented
Go on, make it happen.


Put it on GitHub/GitGud


Tag characteristics


Hydrus WINS!


>>>/oven/ >>>/trannypol/

Why are you not in an institution?

Because PHP

In addition to types (character, author, copyright, meta) I'm adding taxonomies, Taxo will describe what the tag is describing. For example, "black_and_white", "3d", and "photo" would go under under the "style" taxonomy. "sleeping", "screaming", "running" would have a verb taxo. "2girls", "solo", "female/male" would fall under a subjects taxo, etc. It will also differentiate tags of the same name a little more nicely; is the image a photo, or is there a photo in the image?

Essentially, tag type will be required for a functioning tag, taxo will not be, but taxo will in general help a lot of things. When all the types of taxo are set in stone, images will require tags with certain taxonomies before they can be fully approved. Every image needs a noun, every image needs a subject, a verb, etc.

I have to go through and strip my name out of the source headers first; I borrowed a lot of code from another project, and this isn't something I want to associate myself with. Future employers might get squeamish, so it will be developed under my "18+" alias "Dizmal". :/

Woowee, retard in the end
news.microsoft.com/2018/06/04/microsoft-to-acquire-github-for-7-5-billion/
Did you like attempt to upload your patches ITT?

I also didn't get what you meant but now I get it. I find illustrating ideas helps a lot. Basically it's tag relationships. You can have top level categories and have tags branch from them.

Category1
/ | \
Tag1 Tag2 Namespace:Tag3 Tag4

The image siblings would be at one level but could be combined with parent/children hierarchy.

Sibling1 --- Sigbling2 ---Sibling3

Parent
|
Child1&Sibling1 --- Sibling2