docs(pit): put the browser route on /pit/dns - #165
Merged
Conversation
The page told people to change a DNS setting and never mentioned the other way in, so anyone whose DNS is not theirs to change read it as "the namespace does not work for you". TronBrowser asks this registry over ordinary HTTPS before every navigation: no network settings, no admin rights, and the navigation lands on a host with a certificate the browser already trusts, so it is also the only route that does not warn on https://. Listed after the resolvers rather than instead of them, because it only fixes the browser -- curl and git still resolve through DNS. Notes 3.8.8 as the floor: older builds parked unpointed names at moshcoding.com/parking, a route that has never existed, so every claimed name with no target 404'd. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
vu1nz Security Review0 finding(s) in PR #? No security issues found. |
ralyodio
marked this pull request as ready for review
August 1, 2026 02:07
Merged
ralyodio
added a commit
that referenced
this pull request
Aug 1, 2026
install.sh resolves releases/latest, so the sixteen commits merged since v0.13.3 have been sitting on main unreachable — including a fix for a page that locks browsers up. The headline is the pit. /pit rendered every ending an account held and a form per name under each, with no bound on either: at 50 endings x 100 names that was 3.1 MiB of HTML and 36,082 DOM elements, and it managed to jam a browser with no script on the page at all (#167). It now draws a window and says what it is not drawing — 173 KiB, 1,926 elements — with a filter box over the top that takes `eggs` as a substring and `def*` as a glob, debounced against the API (#168). The namespace also stopped being the one part of the product a script could not touch: /api/moshpit/* now accepts the same API key /api/me and /api/sessions already did (#169), and /pit/dns finally documents the TronBrowser route for machines whose DNS is not theirs to change (#165). moshcode: foreign keys are enforced, and the licence package.json claims actually ships (#154) cli: help aliases exit 0 (#157), invalid integration commands fail (#160), `--` is honoured (#159), a BOM before a shebang no longer breaks (#158) skills: engines with no skills primitive are reported, not dropped (#166); `--name` requires a value (#156) mcp: an unsupported flag is rejected rather than registered as the server name (#164) pit: the namespace rules are vendored again with a drift test holding them to the published package (#161, #162, #163) Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.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.
/pit/dnsexplained one way to reach the namespace — point your resolver at ours — and never mentioned TronBrowser. On a machine where DNS is not yours to change, the page read as "this does not work for you."What changed
When a name exists in bothsetting (the per-browser twin ofMOSHPIT_RESOLVE_MODE),mosh.<tld>to claim from the address bar, and Registry (advanced) for a self-hosted pit.https://warning is a resolver-route problem. TronBrowser sidesteps it by rewriting the navigation to the registry's own HTTPS host — stated as the trade it is (the address bar shows where it landed, not what you typed).digon the browser route; openmosh.eggsinstead.moshcoding.com/parking, which has never existed, so they 404'd. Fixed in tronbrowser.dev #56 (v3.8.7) and #58 (v3.8.8, which also discards the stale address left in settings).Testing
node --testinapps/pwa— 301 pass, 0 fail.GET /pit/dnsagainst a live router: 200, and every new string present.🤖 Generated with Claude Code