Skip to content

Craft talk · not launched

We do not have a chat server

Every product page eventually grows a “Join our Discord” button, and most of them point at a channel where the last message is eight months old. 9 sample personas and zero real conversations is exactly the situation where that button would be a lie, so this page is the honest version: the conversation, the rules, and where it already happens without a server.

What would actually be discussed

  • Where a component breaks in a real product — the bug reports that are too specific for an issues tracker and too useful to lose.
  • Model drift: which brief stopped reproducing, on which model, on which day.
  • Audit disagreements: “you scored this 94, my axe run says 89, here is the trace.”
  • Bundle arguments. The 5 KB budget is a design opinion and it deserves to be argued with.

Rules we would set on day one

  • No unpaid promotion, no “check out my thing” with no craft content.
  • Critique the work, not the person — and lead with what the work is trying to do.
  • Every claim of a defect comes with the environment it was seen in.
  • Beginners welcome, unexplained jargon not. Explaining a term is not a distraction from the conversation, it is the conversation.

What would have to be true before we open a server

  1. Enough submissions arriving that moderators are talking to people anyway.
  2. A named person who answers there within a day, every week — a channel without a host is a dead channel.
  3. A moderation policy that survives contact with a bad week, not just a good one.
  4. Something better than a link: the audit gates, the challenge calendar and the requests board all feeding the same room.

Until those four are true, this page stays up and the join button does not. If you want to argue with that decision, the requests board takes arguments too.