Point pin publishing at /pit, which is where the form actually is - #10
Merged
ralyodio merged 1 commit intoAug 1, 2026
Merged
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
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>
Copy link
Copy Markdown
vu1nz Security Review0 finding(s) in PR #? No security issues found. |
Sorry, something went wrong.
ralyodio
marked this pull request as ready for review
August 1, 2026 19:41
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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:
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:
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:
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