Skip to content

Client tag (NIP-89) reads JANK#19

Merged
DocNR merged 1 commit into
mainfrom
claude/jank-client-tag-caps
Jun 17, 2026
Merged

Client tag (NIP-89) reads JANK#19
DocNR merged 1 commit into
mainfrom
claude/jank-client-tag-caps

Conversation

@DocNR

@DocNR DocNR commented Jun 17, 2026

Copy link
Copy Markdown
Owner

Follow-up to #18 (caught post-merge). The NIP-89 client tag — the "posted via …" label other Nostr clients show — was still jank, because I'd bucketed nostrClientTag with the wire identifiers when I shipped #18. It isn't one: it's built as a bare ['client', 'jank'] label (src/lib/draft-event.ts) with no NIP-89 handler d-tag and nothing matching the string in logic, so it's visible brand copy. Flipped to JANK so posts read "via JANK", consistent with the rest of the brand.

One-line value change in branding.ts (+ a comment so it doesn't get re-lowercased as a "wire id" later). npm run build green.

The genuine wire/machine IDs still stay lowercase on purpose: npm package name, the deck-sync d-tag, and the MCP serverInfo.name.

No version bump / release-notes entry — trivial consistency follow-up that ships under the 26.15.2 JANK theme. Say the word if you'd rather I bump to 26.15.3.

🤖 Generated with Claude Code

The ['client', ...] label other clients show as 'posted via ...' used BRAND.nostrClientTag = 'jank'. It's a bare label with no d-tag / handler address and nothing matches the string in logic, so it's visible brand copy, not a wire identifier. Flip it to JANK to match the rest of the brand (caught by Daniel post-review).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@DocNR
DocNR merged commit bdbefcc into main Jun 17, 2026
2 checks passed
@DocNR
DocNR deleted the claude/jank-client-tag-caps branch June 17, 2026 10:34
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