docs: state of the Nuri support portal — start here - #10
Merged
Conversation
Someone sent the repo link and expected the next person to be productive immediately. They would not have been: the landing README was upstream Buzz with no mention of the portal, and the production state was recorded nowhere. - README gets a banner above everything else: what this fork runs, where the handover doc is, and the three facts that will otherwise waste a day. - docs/nuri-support-portal.md — deploy commands, server paths, both authorization layers with file references, owner rotation without asking anyone to copy a 64-char key, the ranked issue list, and next steps in dependency order. - CHANGELOG gets a Nuri fork section separating this fork's history from the inherited upstream entries. Three things this records that were not written down anywhere: 1. Production runs feat/nuri-passkey-wallet, not main. 2. Two chat implementations exist in the same directory — PR #7 on main and the branch — written in parallel without knowing about each other. They conflict. Deciding which survives is task one. 3. BUZZ_REQUIRE_RELAY_MEMBERSHIP=false in production. The README claimed true. The relay is open, any Nostr key can participate, and the passkey is not enforced as an entry requirement. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Three pull requests are open on this portal and they overlap. PR #9 and feat/nuri-passkey-wallet fix the identical WebAuthn focus bug, built twice in isolation — the clearest evidence that the state was written down nowhere and everyone was guessing. 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.
Makes the repo self-explanatory. Right now a first-time visitor lands on the upstream Buzz README with no mention of the Nuri portal, and nothing anywhere records what production actually runs.
What this adds
docs/nuri-support-portal.md— deploy commands, server paths, both authorization layers with file references, how to rotate the owner without asking anyone to copy a 64-char key, a ranked issue list, and next steps in dependency order.CHANGELOG.md— a Nuri fork section, separated from the inherited upstream entries.Three things this records that were written down nowhere
feat/nuri-passkey-wallet, notmain. support.nuri.com serves bundleindex-PQCgW_DB.jsfrom that branch, which has an/adminUI and two bug fixesmaindoes not.mainand the branch — written in parallel without knowing about each other. They conflict onChatPage.tsxand the route files. Deciding which survives is task one.BUZZ_REQUIRE_RELAY_MEMBERSHIP=falsein production. The README claimedtrue. The relay is open: any Nostr key can read and post, and the passkey is not enforced as an entry requirement.Docs only — no code changes, no conflict with either chat implementation.
🤖 Generated with Claude Code