atjam.at/web/app/styles/ at main · natespilman.at/atjam.at · Tangled

natespilman.at / atjam.at

0

A jam is a shared-deadline creative challenge: one prompt, a roster of participants, a single due date. Submissions point at records that li

0

atjam.at / web / app / styles /

at main 1 file

Nate Spilman web: rank the feed by what's live, and point prod at EPTSS 4w ago

web: rank the feed by what's live, and point prod at EPTSS Prod's home feed was built with VITE_KNOWN_ORGANIZERS set to the nls-testuser1 test account, so atjam.at listed fourteen seeded test rounds and no real ones — EPTSS Round 31 was never in the feed at all. Point it at @eptss.at. Vite bakes this at build time, so it takes a `flyctl deploy` to land. Then rank what's left. Thirty-one archived EPTSS rounds outnumber the one live round 31:1, and an undivided list buries the only round anyone can act on. Split on the existing Round.deriveState — open/in-progress up top under "Active", closed folded into a <details> the browser already knows how to render. Add UNLISTED_ROUNDS for records that are real but not presentable: partial migrations, drafts superseded by a later record. They stay on the network and reachable by direct link, they just don't get featured. A partially migrated duplicate of Round 29 is the first entry — it derives `open`, so it was ranking beside the genuinely active round. Both surfaces that list rounds route through listedRounds(). Also group milestones that share an instant into one transit station. A phase boundary is a point, not a span — EPTSS closes signups and opens voting at the same moment — so drawing two stations put a segment between them and asserted a duration that doesn't exist. Round 31 has two such boundaries and goes from six stations to four. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

1 month ago