dhkatzandClaude Opus 5.5 8793b5afd8
Pull request / title (pull_request) Successful in 1s
CI / test (pull_request) Successful in 1m4s
CI / image (apps/api/Dockerfile, t5de-hub-api) (pull_request) Skipped
CI / image (apps/web/Dockerfile, t5de-hub-web) (pull_request) Skipped
feat: product drafts, moderator edits with reasons and locks, info history, unlisted products and tags
New uploads are drafts: only their creator and moderators see them, nobody can get or wear them, and they're
deleted if not published within 30 days (their catalogs get delete changes). The creator reviews the info and
publishes it.

Editing a product's info is a permission check now (product:edit): moderators can edit anyone's with a reason the
creator sees, lock fields (product:lock; locked fields need product:edit-locked) and lower ratings
(product:rate-lower, not below its files'). Every change is kept in the product's info history, with who and why,
and can be undone by the same rules.

Products can be unlisted (out of search and lists, the link still works) and tagged; lists filter by tag and
catalog. The console has a Products section (everyone's for moderators, by status) and a drafts to-do.

A product's own category is left for later: the hub has no list of IMVU's categories to pick from.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-11-05 05:40:43 -08:00
2026-11-03 11:29:26 +00:00

t5de-hub

T5DE's hub: accounts linked to IMVU accounts, presence, and (to come) the registry of community products and catalogs, T5DE-hosted rooms, and the moderation console. Part of T5DE (git.t5de.dev/t5de). Design: docs/design.md; the API: docs/api.md; what a room needs from a server: docs/imq-rooms.md.

What works

  • Accounts (Better Auth): sign-up with email, username and password; sign-in by username. The first account is an admin; roles user, moderator, admin. Registration open or closed (new accounts wait for a moderator's approval): an admin's setting in the console, defaulting to the API's REGISTRATION.
  • Linking IMVU accounts: the person puts a code in the account's tagline; the hub reads it from IMVU's public API. The most recent proof wins (an account linked elsewhere moves, with a new pairwise ID). Link caps per person (default 10).
  • Age: an IMVU account counts as adult if IMVU says it's age verified or has Access Pass, checked by the hub, or if its person verified their age with an ID document and a selfie (Didit, when configured: AGE_PROVIDERS, see apps/api/src/index.ts and docs/design.md, "Age").
  • Proxy sign-in: OAuth 2.0 device authorization (t5de-proxy signin shows a code to enter at /device); the proxy then uses its session as a bearer token. JWTs with published keys (/.well-known/jwks.json) for catalogs.
  • Presence: signed-in proxies keep a WebSocket (/api/v1/realtime) telling the hub which IMVU account is in use and the community products it wears. /online shows those who opted in, live, with the opt-in T5DE badge.
  • Products (website): browsing and search, product pages, uploads straight from the browser to a catalog, editing, revisions (retract, stay on one), the library, and registering catalogs (docs/products.md). Pages send a strict Content Security Policy (apps/web/proxy.ts).
  • Console (moderators): counts, who's online (live), people, link caps, bans, roles, the audit log.

Layout

A Bun monorepo (workspaces, Turborepo):

apps/api The API: Elysia on Bun, Better Auth, the realtime WebSocket. Port 4101.
apps/web The website: Next.js 16 (React server components), Tailwind CSS 4, shadcn/ui. Port 4100. Calls the API through its own /api (rewrites), typed end to end with Eden.
packages/db Drizzle schema and migrations; Postgres in production, PGlite (in-process Postgres) for development and tests.

Development

Needs Bun (1.4) and Node (for Next.js).

bun install
bun run dev          # the API on :4101 (database in apps/api/data) and the website on :4100

bun run test tests the API against PGlite; bun run check-types, bun run build.

Running it

  • Self-hosted: AUTH_SECRET=$(openssl rand -base64 32) docker compose up -d runs Postgres, the API and the website (see docker-compose.yml for the public addresses).
  • Elsewhere: the website deploys as is to Vercel and similar (apps/web, env API_URL); the API to any host that runs Bun or containers (Railway, Render, Fly.io, Heroku), with DATABASE_URL, AUTH_SECRET, API_URL (its public address) and WEB_URL (the website's).

A staging site shows a slim "Staging" bar: when it's served from a staging. address (hub.staging.t5de.dev), or with the website's HUB_ENVIRONMENT=staging (production hides it).

T5DE's proxies reach the API's address directly (sign-in and the WebSocket): t5de-proxy signin -hub <API address>.

S
Description
One account for all your IMVU avatars.
Readme
733 KiB
0 Stars 2 Watchers 0 Forks
v0.2.0
Latest
2026-11-03 11:29:30 +00:00
Languages
TypeScript 99%
CSS 0.7%
Dockerfile 0.3%