Repository navigation
feat(nip77): advertise NIP-77 in NIP-11 and expose its settings in the admin console - #830
Merged
cameri merged 4 commits intoOct 15, 2026
Conversation
Signed-off-by: Priyanshubhartistm <bhartipriyanshustm@gmail.com>
Signed-off-by: Priyanshubhartistm <bhartipriyanshustm@gmail.com>
🦋 Changeset detectedLatest commit: 5b5ba01 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
 [Medium impact] This PR appears safe to merge.
|
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
Collaborator
Coverage Report for CI Build 38795845036Coverage increased (+0.03%) to 74.515%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsNo coverage regressions found. Coverage Stats
💛 - Coveralls |
cameri
approved these changes
Oct 15, 2026
cameri
pushed a commit
that referenced
this pull request
Oct 16, 2026
) * ci(website): deploy on nostream-website release publish, not on main pushes The site now deploys when the changesets workflow tags and publishes nostream-website@X.Y.Z (the release event this workflow filters on). Merging relay work to main no longer touches the site deploy; a site deploy happens exactly when a release PR that bumps nostream-website merges. Checkout on a release event is the tagged commit, so the deployed assets are the released build. Relay image releases keep their v* gate in release.yml — the tag namespaces do not overlap. workflow_dispatch remains for manual deploys of main. * fix(website): warn instead of failing while the hero film is stale The film guard hard-failed every site build since #830 added NIP-77 (supportedNips 24 -> 25): re-rendering the film needs the GPU pipeline and no GPU is available to the sandbox or the runners. Per operator order the mismatch branch now warns (loudly, with the re-render commands) and exits 0, unblocking releases; the comment in the script names the day, the order, and where to restore exit 1.
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
3 participants
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.
Description
Lets clients discover NIP-77 and lets operators configure it without editing the settings file.
supported_nipsnow lists77, but only while NIP-77 is active (nip77.enabledis true andeventStore.backendispostgres), the same way43is only listed when NIP-43 is enabled. A relay with it switched off, or serving another backend, does not claim support. The 43 and 77 gates are independent.nip77settings (enabled,maxEventsPerSession,maxSessionsPerConnection,sessionIdleTimeoutMs) are added to the admin console's guided settings (and so to the CLI settings menu, which reads the same schema). The numeric fields use a new positive-integer validator, matchingvalidateSettings, which rejects0.77is now inpackage.jsonbut not advertised by default.CONFIGURATION.mdnotes the NIP-11 advertisement and the admin console availability.Related Issue
Closes #819
Motivation and Context
After #818 relays can answer NIP-77 sync requests, but nothing told clients: they had to open a
NEG-OPENand read the error to find out. Advertising it only while it is actually served keeps NIP-11 honest, and exposing the settings bringsnip77in line withnip45,nip50andnip56.