feat(pit): setup instructions for the resolvers, on the site itself - #78
Closed
ralyodio wants to merge 1 commit into
Closed
feat(pit): setup instructions for the resolvers, on the site itself#78ralyodio wants to merge 1 commit into
ralyodio wants to merge 1 commit into
Conversation
A resolver nobody can find the instructions for resolves nothing. `/pit/dns` is the page a normal person lands on: the addresses to use, the setting to change on macOS, Windows, Linux, a router or a browser, and two commands to check it worked. The addresses come from MOSHPIT_DNS_RESOLVERS rather than the source, because they are operational facts that change when a box moves, and a page that keeps telling people to use an address that moved is worse than one that says nothing. Unset — which is today — the page says the resolvers are not published yet and explains how to run one. It never invents an address for a stranger to paste into their network settings, and entries that are not addresses are dropped rather than rendered. The page needs no database, so it stays up when the registry does not. Also says plainly what does not work: HTTPS on a Moshpit name warns, because no public CA will issue for a namespace outside the ICANN root, and clearnet lookups are forwarded to Google and Cloudflare. Both are reasons someone might run their own, which the page tells them how to do. /pit dropped the line about this shipping "until the resolver ships" — it has — and links here instead. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
vu1nz Security Review0 finding(s) in PR #? No security issues found. |
Collaborator
Author
|
Superseded by moshcoder/moshcode#124. The resolver from #77 is unaffected and stays here; only the instructions page moved. Branch left in place if any of the copy is worth salvaging for moshcoding.com. |
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.
Follow-up to #77 (merged). The resolvers exist; this is the page that tells a normal person how to use one.
pit.moshcode.sh/dns— the addresses to use, the setting to change on macOS, Windows, Linux, a router or a browser, and two commands to check it worked./pitlinks to it and drops its line about this shipping "until the resolver ships", since it has.The addresses are config, not source
MOSHPIT_DNS_RESOLVERS=dns1.pit.moshcode.sh=203.0.113.7,dns2.pit.moshcode.sh=203.0.113.8, withMOSHPIT_DOH_URLalongside it. They are operational facts that change when a box moves, and a page that keeps telling people to use an address that moved is worse than one that says nothing.Unset — which is the state today — the page says the resolvers are not published yet and explains how to run one. It never invents an address for a stranger to paste into their network settings, and entries that are not addresses are dropped rather than rendered, because that list goes onto a public page for people to copy into their network settings.
The page reads no database, so it stays up when the registry does not.
Honest about what does not work
https://on a Moshpit name warns — no public CA will issue for a namespace outside the ICANN root — and clearnet lookups are forwarded to Google and Cloudflare. Both are reasons someone might want their own resolver, which the page then tells them how to run.Verified
/pit/dnswith sample config: addresses, DoH endpoint and title all present, 200 with no database configured.tsc --noEmitclean.Note on the base branch
tests/coinpay-amount.test.mjsfails onmasteras it stands, independent of this PR — verified by running the suite onorigin/masteralone.setupAmountUsdrejects ordinary amounts:Math.abs(value - rounded) > Number.EPSILONinlib/coinpay.ts:42compares against an absolute epsilon of 2.2e-16, but the representable gap near $20 is ~3.6e-15, so19.99throws "must not have fractional cents". That came in with #59. Happy to fix it in its own PR.🤖 Generated with Claude Code