Skip to content

pit: a parked name is a page, not a 404 - #149

Merged
ralyodio merged 1 commit into
mainfrom
fix/parked-name-200
Jul 31, 2026
Merged

pit: a parked name is a page, not a 404#149
ralyodio merged 1 commit into
mainfrom
fix/parked-name-200

Conversation

@ralyodio

Copy link
Copy Markdown
Contributor

/n/<name> answered 404 when nobody held the name. The body was right — the directory of what else lives under that ending — but the status said the URL had nothing at it.

It does have something. This is the parking page every resolver and the browser extension send unpointed names to; it's the answer, not the absence of one. A 404 makes a working page read as broken to the browser, to a link checker, and to anything that looks at status before body.

/n/scrambled.eggs   200   ← parked, directory page
/n/not-a-name       400   ← not one label and one ending; no page to be

Pairs with profullstack/tronbrowser.dev#56, which points parking at this route instead of moshcoding.com/parking — a URL that has never existed.

🤖 Generated with Claude Code

/n/<name> answered 404 when nobody held the name. The body was the right page
— the directory of what else lives under that ending — but the status said the
URL had nothing at it.

It does have something. This is the parking page every resolver and the
browser extension send unpointed names to; it is the answer, not the absence
of one. A 404 makes a working page read as broken to the browser, to a link
checker, and to anything that looks at the status before the body.

A malformed name still gets 400: `not-a-name` is not one label and one ending,
and there is no page for it to be.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

vu1nz Security Review

0 finding(s) in PR #?

No security issues found.

@ralyodio
ralyodio merged commit 9836be5 into main Jul 31, 2026
3 checks passed
@ralyodio
ralyodio deleted the fix/parked-name-200 branch July 31, 2026 12:42
ralyodio added a commit that referenced this pull request Jul 31, 2026
* chore(release): v0.13.3

install.sh resolves releases/latest, so everything merged since v0.13.2 has
been sitting on main unreachable — `moshcode dns enable` exists in the source
and not in anyone's binary.

The headline is the DNS bridge (#141). Moshpit names now resolve for every
program on the machine, not just inside TronBrowser: each OS gets the mechanism
that routes ONE SUFFIX rather than the one that replaces the resolver —
/etc/resolver on macOS, systemd-resolved routing-only domains or dnsmasq on
Linux, an NRPT rule per namespace on Windows.

  moshcode dns enable / disable / status
  moshcode uninstall <engine|tool>          (#150, completion in #151)

The pit gained most of a namespace registry in between: key pins per name
(#137), pasted bulk claiming with per-line price and target (#138, #142, #143,
#146), all-numeric endings (#147), /n/<name> serving a name or a directory
(#145, #149), and Buy Now on an unclaimed name (#148).

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* chore: restore the em-dash the version bump escaped

The bump rewrote package.json through a JSON serialiser that defaults to ASCII,
turning the em-dash in `description` into —. Valid JSON and the same string
once parsed, but a gratuitous diff in a commit that should touch one line.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant