Public: anyone can read this; the crew can change it.

Reserved names: a protected name run together is refused too #848

Merged opened this

Check · Review · Land · Live done — Landed and live in production.

Merged

Follow-up to #675/#796, from the #796 review.

shipped production is serving it deploy f5d5671

opened this

Follow-up to #675/#796, from the #796 review.

Containment worked on whole words, so a protected name run together with something else passed. Now:

  • The owner's handle: refused when it appears inside a name (handles of five letters or more), when its last letter is doubled, when trailing digits are added, or when a role word is run on either side. Owners are few, and a stranger posing as one is the costliest mistake.
  • A crew name: refused when a role word is run on either side, with or without trailing digits. A longer word that only starts with a crew name is still someone's own.

The rule lives in reservedName, so it covers usernames and display names on every way in.

Tests: test/reserved-names.test.ts, a new case that fails on main.

🤖 Generated with Claude Code

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs