Redbox
"Redbox" is a placeholder name: a literal red box, a nickname for a question-and-vulnerability game I've hosted for years, inspired by We're Not Really Strangers. It will likely be renamed so it isn't confused with the rental-kiosk company. When it is, the only things to change are the title in meta.json, the strings in index.html and assets/app.js, and the folder name (which is the URL).
Goal
Simulate the question-asking nights I've hosted: mostly one-on-one, trading questions back and forth, but often in groups — drawing a card for the whole table, spotlighting one person, or alternating between a series of questions for one person and a question for everyone. Questions are curiosity-driven, meant to open up meaningful conversation. Each night has been a little different, so the tool stays loose: it is a deck, a roster, and a shared table, not a rulebook.
How v0.1 works
- Create a room and you get a five-character invite code. You are the host.
- Join with the code (same browser) or with an invite link (any device, as a snapshot — see limits below).
- Play tab — the shared table. One card is on the table at a time. Anyone can draw a random unasked question or pick a specific one from the Deck. Cards you've already used in this room are remembered so draws don't repeat. The host picks the answer format: whole table, spotlight (only the person on the spot), or pair swap (the person on the spot and the one up next trade the question back and forth).
- Deck tab — every question in one list with search, depth filters (Warm-up / Connection / Deep) and source filters. The same filters narrow what "Draw a question" can pull.
- People tab — the roster the host writes down. The person at the top is on the spot, the second is up next, and everyone else is waiting, so people can see when questions are coming their way. The host can add players (one per line), reorder, pull someone to the front, remove, or hit Next person to send the current person to the back of the line. Everyone else sees it read-only.
- Add tab — any player can write a question and drop it into the room's deck. It shows up for everyone in the room as a "This room" question.
- Room tab — the code, copy buttons, export/import, and the host's end-of-session tools.
The three question lists
questions.json— confirmed questions, the curated deck. Hand-edited in the repo.suggested.json— suggested questions, player ideas kept from earlier sessions. Loaded into every game alongside the confirmed deck.- This room — temporary questions added by players during the current session, stored in the room.
At the end of a session the host opens Room → Wrap up. It produces a new suggested.json (the current one plus everything players added, duplicates removed) to copy or download. Replace the file in the repo and push, and those questions persist for every future game. To promote a favorite to the confirmed deck, move it by hand from suggested.json into questions.json and give it a c### id.
Question shape: { "id": "c001", "text": "...", "depth": 1, "category": "warm-up" } where depth is 1 (Warm-up), 2 (Connection) or 3 (Deep). The starter set of 66 questions is original writing, not taken from the commercial card game.
Limits of v0.1 (read this before a live night)
- No server. A room lives in the browser that created it. Tabs of the same browser sync live (handy for testing, or passing one device around), but two phones will not see each other's changes.
- Invite links are snapshots. The link carries the roster, the questions and the card on the table as of when it was copied. Someone opening it on another device sees that moment, not live updates, and their own added questions stay on their device until they export the room file and send it to the host, who imports it (Room → Import questions).
- "Host" is not secured. Host controls are hidden from guests in the interface, but there are no accounts, so anyone technical enough with access to the same browser could act as host. Fine for a room of friends; not fine for strangers.
- Storage is localStorage, so clearing site data deletes rooms. Export a room file if it matters.
Ideas for later phases
Phase 2 — a real live room
- A small shared backend so phones in the same room actually share state: roster, card on the table, asked history and new questions. Options in rough order of effort: a Supabase table with realtime subscriptions (precedent exists in this repo:
tools/private/hearth-old/js/cloud-store.js), Vercel serverless functions plus a KV store with short polling, or a websocket service such as Ably or PartyKit. Polling every two seconds is plenty for this use and is the simplest thing that works. - Because the toolbox is static, a backend would be its own Vercel project with a rewrite for
/redbox, as noted inBACKLOG.md. - A real presence list ("who has this open right now") separate from the host-written roster, with a gentle prompt to add yourself.
- Host handoff, and a host key so only the creator's device can change the roster.
- Rooms that expire on their own after a few hours, and a codename generator instead of random letters.
Phase 3 — more of the real experience
- Question flow modes beyond a plain draw: a guided "five questions for one person, then one for the whole table, then spotlight the next person" sequence, with a timer and a visible round counter.
- Pass and skip: a player can decline a card without anyone being put on the spot, and the card quietly goes back to the deck.
- A "reveal" step where answers can be typed privately and shown together, for online groups.
- Reactions or a "that landed" button — a way to acknowledge a vulnerable answer without interrupting it.
- Tagging questions by mood or occasion (first meeting, old friends, couples, team offsite) so the host can load a themed deck, and a way to author a deck per event.
- Printable card export (PDF) so the deck can exist as a real red box.
- An approval screen for the host to review suggested questions and promote or reject them without editing JSON by hand, ideally committing back to the repo through the GitHub API.
- Safety pieces worth considering for groups: a content note on Deep questions, a one-tap "pass" that is always available, and a short host-visible reminder that sharing is optional.
Open questions for the host
- What should it be called? (The rental-kiosk company makes "Redbox" a problem outside the friend group.)
- Should guests be able to put a card on the table, or only the host and the person on the spot?
- Is the roster always chosen by the host, or should players be able to "get in line" themselves?
- Does the deck need more than three depth levels, or categories players can filter by (family, love, work, regrets)?
- How long should a room live, and should old rooms be listed somewhere?