A look inside the Tavern
The real product sits behind a sign-in and a short onboarding game, because nothing about a person becomes cohort-visible until they have approved it. That is the right default for members and an annoying one for anyone evaluating the app, so this page shows the surfaces without an account.
Everyone below is a seeded demo profile: fictional people the seed script creates and labels as such. No real member's writing appears on this page.
#general
The channel surface. Signed in, this polls every two seconds and carries reactions, @mentions, and structured message types.
Week two kickoff: if you're looking for a project to join, the directory is under Projects — every one of them takes join requests.
Anyone else find the cohort map slightly too accurate about them, or just me.
A collaborator profile
Drafted from public GitHub work, then edited and approved by the person before anyone else could see a word of it.
Your public work suggests a systems thinker who reaches for TypeScript first and tests before believing anything. Appears happiest untangling other people's async bugs. We may be wrong about this — but the commit messages are suspiciously tidy.
Can help with: Debugging async code, writing tests that catch real bugs
Wants help with: Frontend polish — my UIs look like tax forms
An explained match
Scoring is deterministic; the "why" is written in plain language so a suggestion can be argued with rather than taken on faith. Every card is addressed to the person reading it, so this is the card as Mara Voss sees it.
Dev leads with integration and systems shape, where your map is lighter; you test before believing anything, which is where his is. Pairings like this tend to cover more ground than two of the same, though they usually argue first.
What this page leaves out
- Direct messages and the snug, which are private to their participants and excluded from search by design.
- The onboarding game that builds the collaborator map, and the bartender introduction that follows a match.
- Project tables, join requests, and the structured conversation types that run inside them.
- Posting, reacting, and notifications, all of which need an account.