Both the README and setup-origin.sh sent operators to
app.moshcode.sh/pit/dns. That page is the instructions for pointing a
machine's *resolver* at Moshpit -- a walkthrough of System Settings on
macOS, resolvectl on Linux. It has no pin form anywhere on it.
So the documented last step of publishing a key could not be completed by
following the documentation. The name stays refused by every client, the
server looks broken, and nothing on the page suggests you are in the wrong
place.
The dashboard is /pit: sign in, "Yours" tab, "Key pins" on the TLD. Same
page carries a name's "points at" target, which is the other half of making
a name reachable, so it is worth naming as the one place to go.
The script now prints the TLD it wants, since "Key pins on .hacker" is
actionable in a way that a bare URL is not.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>