From 34425add90ec3b1ec6758a3371f1fb1b5db7aa69 Mon Sep 17 00:00:00 2001 From: Anthony Ettinger Date: Sat, 1 Aug 2026 19:37:05 +0000 Subject: [PATCH] Point pin publishing at /pit, which is where the form actually is 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) --- README.md | 11 ++++++++++- scripts/setup-origin.sh | 3 ++- 2 files changed, 12 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index d6d8570..497355b 100644 --- a/README.md +++ b/README.md @@ -184,7 +184,16 @@ npx moshpit-pin scrambled.eggs:443 # from what a live server presents refuses the name — there is no TOFU and no unauthenticated mode, because the pin stands exactly where a certificate authority would. -Publish the result at [app.moshcode.sh/pit/dns](https://app.moshcode.sh/pit/dns). +Publish the result at [app.moshcode.sh/pit](https://app.moshcode.sh/pit) — sign +in, open the **Yours** tab, and use **Key pins** on the TLD. + +Not `/pit/dns`, which this file used to say. That page is the instructions for +pointing a *machine's resolver* at Moshpit — it has no pin form on it, so the +old link sent operators somewhere they could never finish the job. + +The same page is where a name's **points at** target lives, which is the other +half of making a name reachable. + Keep the previous pin listed alongside the new one while rotating — the client accepts any pin in the list, so a key can change without a flag day. diff --git a/scripts/setup-origin.sh b/scripts/setup-origin.sh index bf62a45..0c903a3 100755 --- a/scripts/setup-origin.sh +++ b/scripts/setup-origin.sh @@ -199,7 +199,8 @@ cat >&2 <