Boards, beef & happenings

Flicks are one half of the place. Talking is the other.

Boards

Boards is the list of walls. Cities get their own cards with counts on them; everything else sits under Everything else as chips.

A board isn't something you apply for. You start one by posting to it — put a flick up with a city on it, or start a thread on a slug that doesn't exist yet, and the board exists.

Each board has two sides:

• talk — threads and replies.
• flicks — what got put up with that board's tag on it.

Threads

Start one on any board. Title, body, up. Replies nest under each other, and a reply can quote and answer a specific one rather than the thread as a whole.

Reply counts show on the board list, so you can see where the noise is without opening anything.

When you reply — in a thread, or in the comments under a flick — you can shout somebody out by typing @, and the app suggests the writers already in that conversation.

Beef

Beef doesn't stick around. When you start a thread you pick how long it runs:

Choice	What it says
24 hours	gone tomorrow
3 days	a weekend of it
a week	settle it properly
pinned	stays up

A thread with a clock on it shows a countdown — "dies in 23h" — and when the clock runs out the wall throws it away itself. It's not hidden from you while quietly sitting in a database; the box that holds it drops it, and the index drops it after. Nothing to restore, nothing to subpoena, no cron job anybody forgot to run.

Boards where things are meant to stay put open on pinned instead. Beef is the default where beef is the point.

Buffing vs. running out

Buffing is you taking something down. A clock running out is the thread taking itself down. Neither one can reach a screenshot somebody else already took.

Happenings

Happenings is jams, meets and shows with a date on them. Soonest first, filterable by city.

A happening isn't a different kind of post — it's a thread with a date. Start a thread on the board you want it on, flip the date switch, put the date on it. It lands on the happenings list, and it clears itself a week after the date passes. Nobody has to sweep up last month's flyers.

Holler

Holler at us is the feedback board, sitting inside the app on the same rails as everything else. Your tag, your words, done — no email, no account, no separate identity of any kind.

It's the right channel for "this is broken on my phone," "this word is confusing," "the feed does something weird after thirty posts," and feature requests. Requests get triaged onto the roadmap, which is the actual backlog.

It's the wrong channel for anything security-sensitive. That goes through responsible disclosure instead, privately, because a published deanonymization bug is a danger to people who can't patch themselves.

You can buff a holler later if you change your mind, same as any other post.

Where to go next

• Shout-outs & messages — @ mentions and private word.
• Keeping it clean — flagging, ignoring, and what happens next.
• The roadmap — what's up and what's coming.