Answer the questions somewhere, and say what a vote is where one is cast #71

Two gaps, and they are the same gap seen from different ends: the things a person needs to know before joining in were spread across a hero clause, a login paragraph and a README nobody reads.

A FAQ, as a fourth item in the primary nav rather than a footer link, because it answers the two questions that decide whether somebody takes part at all: what a vote is, and what signing in hands over. Nine questions in the order they get asked. What this is, why it exists, then the two that gate participation, then the mechanics, then the ways out.

The why is the real story rather than a rationalisation: Rolling Stone's list of the 25 most influential creators, the post that shared it, the idea of doing the same for Bluesky, and this site's design nodding at that article. The post is linked through OpenIn like every other at-protocol address here, so it opens in whichever client the reader chose rather than in bsky.app because that is where the URL was copied from.

The public-votes answer does not claim a motive nobody had. Votes are public because a vote is a record in the voter's own account, the same as a post, a like, a follow or a block, and because atproto has no private record to put a ballot in yet. That is the protocol as it stands rather than a stance on ballots, so the page says so and links the atproto spaces announcement.

The vote page carries the short version at the field where a name is chosen. "Votes are public" already appeared on the front page and in the bottom bar, neither of which is where somebody is deciding whether to publish a name under their own account.

Two things worth knowing for anyone editing this:

• The help icon draws its dot as a filled square. The h.01 zero-length path that lucide-style sets use renders only under stroke-linecap="round", and every glyph here is butt-capped, so the first version shipped a question mark with no dot.

• The September video is YouTube's own embed snippet, kept as it ships it. An earlier pass swapped in youtube-nocookie and referrerpolicy="no-referrer" on privacy grounds and the player refused outright, error 153, because the rights holder permits the embed per referrer. It still reads "This video is unavailable" on a dev origin, which is not a bug to chase: the same request carrying the site's own origin comes back playable.

The bottom bar goes to four cells. Nothing wrapped and TAB_ROW still lands on the nose, which is the check that matters: labels are one line each at 375px, so the hand-kept reservation is still the height of the thing it reserves for.

Co-Authored-By: Claude Opus 5 noreply@anthropic.com