Point pin publishing at /pit, which is where the form actually is

[ralyodio]

Both the README and setup-origin.sh told operators to publish their key at app.moshcode.sh/pit/dns.

That page has no pin form. It is the walkthrough for pointing a machine's resolver at Moshpit — System Settings on macOS, resolvectl on Linux, the resolver addresses. Nothing on it publishes anything.

So the documented final step could not be completed by following the documentation. The failure is quiet and expensive: the name stays refused by every client, the server looks broken, and nothing on the page hints you are in the wrong place. Verified by fetching it — the visible content is entirely resolver setup:

Use it (DNS) · The addresses · Not published yet. · Set it
macOS — System Settings → Network → … add it with …
Linux — resolvectl dns <interface> <resolver address>

The real dashboard is /pit: sign in → Yours tab → Key pins on the TLD. Its own help text confirms it is also where a name's target lives:

"how do I host a site at a name I hold? — Put your server's IPv6 address in 'points at'."

That makes /pit the single place worth naming, since publishing a pin and setting points at are the two halves of making a name reachable.

Also

setup-origin.sh now prints the TLD it wants, because Key pins on .hacker is actionable in a way a bare URL is not:

  Publish it at https://app.moshcode.sh/pit
  sign in · the "Yours" tab · "Key pins" on .hacker

Verified for both chovy.hacker → .hacker and seo.rank → .rank. sh -n clean, dry-run exercised.

Note

I introduced this link in the earlier origin-side PR by copying it from the existing README, so it propagated rather than originated here. The one remaining /pit/dns mention is deliberate — it names the wrong page so anyone who bookmarked it knows why it moved.

🤖 Generated with Claude Code

[github-actions]

vu1nz Security Review

0 finding(s) in PR #?

No security issues found.