Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

feat(nip77): advertise NIP-77 in NIP-11 and expose its settings in the admin console

未關閉
#819 0 則留言 0 個 reaction 已指派 1 人 在 GitHub 檢視

維護者通常 1 天內回覆

@Priyanshubhartistm 已經在處理了。

開始於 2026年10月12日。

評估

這個 Issue 還沒有評估資料。

描述

enhancement

Is your feature request related to a problem? Please describe.
Relays can now answer NIP-77 sync requests when nip77.enabled is set (#817/#818), but nothing tells clients so. NIP-11 supported_nips does not list 77, so a client or another relay has to open a NEG-OPEN and read the error to find out whether the relay supports negentropy. The nip77 settings can also only be changed by editing the settings file, unlike nip45, nip50 and nip56, which are available in the admin console.

Describe the solution you'd like

  • Advertise 77 in the NIP-11 supported_nips only while NIP-77 is actually active (nip77.enabled is true and eventStore.backend is postgres), the same way 43 is only listed when NIP-43 is enabled. A relay that has it switched off, or that serves another backend, must not claim to support it.
  • Add the nip77 settings (enabled, maxEventsPerSession, maxSessionsPerConnection, sessionIdleTimeoutMs) to the admin console's guided settings, with validation matching validateSettings (positive integers).
  • Tests for the NIP-11 output with the feature on, off, and with a different backend, and for the new guided settings entries.
  • A final pass over the NIP-77 section of CONFIGURATION.md so it matches the shipped behaviour.

Additional context

主要語言
TypeScript
星號
829
分支
234
平均合併
2 天 10 小時
30 天內合併 PR
24

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

cameri/nostream 的其他 Issue

查看 cameri/nostream 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。