a-booru #

booru with stuff a non-booru user finds important

run the compose file.

general architecture #

graph TD
  subgraph backend
    A[main process] -> B[db]
    A -> C[ML runner (something python)]

  subgraph frontend
    X[React app] -> A : JSON API

todo #

• gated access to subset of images via login
  • notion of "private (per-user)", "login only", and "public" content
• infinite scroll option
• autotagger (some ML model)
• semantic search
  • pgvector functionality
• gallery-dl pipeline
  • paste link(s) into importer and pipe to gallery-dl process
  • get source + image via this
  • run through autotagger + embedding
• tag typeahead
• login
  • passkey
  • oidc
  • atproto
  • tailscale lol

might not do #

these could be added later but i think it falls out of scope of what i want to do

admin moderation tools #

• admin CRUD on all posts
• open - invite only - closed
• banning users by did:plc or oidc sub
• spam handling?
  • email verification?

tbh just not worth it. it's a personal project, people hosting things that need moderation are going to be using something else.

semantic search #

it's already handled by the normaly tagging system so i think it would just feel redundant... could be useful for non-anime/art images but then what's the point of a booru

hacking #

use the flake, otherwise it's rust and bun.