Skip to content

Danbooru

RobbWatershed edited this page Aug 24, 2019 · 5 revisions

This design page is aimed at explaining the approach Hentoid would take to support Danbooru.

What is danbooru ?

A Danbooru is an online imageboard and tag-based image archive using a non-hierarchical semantic structure in which users are able to post content and search for images they want to see through tags and ratings. Such sites have been popularized by Danbooru and Gelbooru.

Examples : Rule34.xxx, yande.re

What's so specific compared to regular doujin books ?

Danboorus are like a huge bag full of images, each of them tagged with specific metadata. What the definition means by "non-hierarchical semantic structure" is that there is no predetermined album or gallery; rather as many ways of organizing images as there are combinations of tags.

Topic Regular H-book Danbooru
Structure A given image is contained into a book, that has a page order Images have no container and no given order
Metadata Tags apply to all pages of the book uniformly Each image has its own combination of tags
Browsing A collection of books is usually viewed by listing books, just like a physical library A danbooru is usually viewed by filtering images through a cumulative series of tags, just like Hentoid's advanced search

How would the app evolve to support danboorus ?

As Hentoid has mainly been designed to download and organize h-books, the app is not good at taming the exotic structure of a danbooru. The following are suggestions to move towards that direction.

Data structure

  • Allow Attributes to be linked to ImageFiles

Physical storage of pictures

  • One folder per source, containing all pictures downloaded from this source

Library display

TBD

Image viewing

TBD