Slopbook

Social networks force a bad choice: attach every context to one permanent profile, or go anonymous and lose continuity. That leaves little room for people who speak differently across languages, fandoms, creative work, or moods without turning every experiment into their permanent identity. Slopbook is a public beta for that missing middle: persistent characters without identity collapse.

On Slopbook, a person writes what they mean and the active persona decides how to say it. Only a successful transformed result is stored and published; the private input is not persisted. An account can create and switch between up to five personas, each with an editable public identity, owner-only behavior rules, and a deterministic Oort-cloud-like Sigil. People who only want to comment can save one browser-local guest persona and reuse it across conversations without creating an account.

The product makes that separation visible in two memorable moments. Before a new persona exists, the user previews its exact first post; creation publishes that same sentence once. On the feed, the user presses one reaction control and the persona chooses Like, Love, Insightful, Celebrate, Support, or Funny. The social product around those moments is real rather than mocked: public reading, posts, comments, search, follows, notifications, direct messages, reposts, account-fair feed ranking, secure media variants, and English, Korean, Simplified Chinese, and Japanese interfaces are running now.

The service is a Clojure/ClojureScript modular monolith with Clean Architecture dependency rules and DDD bounded contexts. PostgreSQL owns durable state; Supabase provides authentication and bounded object storage; OpenRouter provides the runtime persona transformation boundary. Persona Sigils are rendered once into immutable responsive images instead of placing thousands of SVG particles in the browser.

We used Codex with GPT-5.6 throughout Build Week as a persistent implementation partner: product and interaction design, Clojure/ClojureScript implementation, regression tests, Korean IME root-cause debugging, browser QA, security and privacy review, and Coolify production rollout. The primary session records where the human owner rejected or redirected Codex—the original avatar, staged persona flow, weak i18n approach, image-AI cost, and an evaluation-focused evidence plan—and links each correction to code and verification. GPT-5.6 is a development tool for this project, not a production inference dependency.

Try the public feed at https://app.slopbook.org. Reading and guest commenting do not require an account; Google sign-in unlocks the complete multi-persona and social flow.

Codex with GPT-5.6 also supported the operational work behind the product: OpenRouter runtime configuration, secret and capability boundaries, Coolify rolling deployments, health and log verification, and browser canaries against the public service. It also produced this submission film from the owner's revised story—storyboard, real browser-demo capture, English narration, burned captions, FFmpeg composition, and final frame/audio checks. The owner made the product decisions; Codex carried those decisions through implementation and evidence.

Built With

• clojure
• clojurescript
• codex
• coolify
• docker
• gemma
• gpt-5.6
• openrouter
• postgresql
• supabase