Issues

• Document and validate that RateLimit.period is milliseconds

  cameri/nostream#1007 · Filter by author chappie-daemon opened on Oct 31, 2026

• Rate-limit responses: EWMA backoff is a half-life, an outage is reported as rate-limited, and the message bucket ignores message type

  cameri/nostream#1006 · Filter by author chappie-daemon opened on Oct 31, 2026

• relay: the settings validator must own the ceiling, not just the floor

  factoryrewriterust
  cameri/nostream#998 · Filter by author chappie-daemon opened on Oct 25, 2026 · Phase 2: Protocol core
  2

• relay: reject a zero frame-memory budget or per-IP cap in the validator

  factoryrewriterust
  cameri/nostream#996 · Filter by author chappie-daemon opened on Oct 25, 2026 · Phase 2: Protocol core

• relay: on a semantically rejected settings document, the bound report is silently dropped

  factoryrewriterust
  cameri/nostream#994 · Filter by author chappie-daemon opened on Oct 25, 2026 · Phase 2: Protocol core
  2

• relay: Account::refusal()'s wildcard would swallow a third refusal cause

  factoryrewriterust
  cameri/nostream#993 · Filter by author chappie-daemon opened on Oct 25, 2026 · Phase 2: Protocol core

• relay: one address can exhaust the shared frame budget below its own socket cap

  factoryrewriterust
  cameri/nostream#992 · Filter by author chappie-daemon opened on Oct 25, 2026 · Phase 1: Rust foundation

• rewrite: the CLOSE-during-mint test's yield poll can accuse the code, and its comment understates its coverage

  factoryrewriterust
  cameri/nostream#991 · Filter by author chappie-daemon opened on Oct 25, 2026 · Phase 2: Protocol core
  2

• rewrite: expose the frame-memory budget and per-IP cap as settings, not only as RelayConfig

  factoryrewriterust
  cameri/nostream#989 · Filter by author chappie-daemon opened on Oct 25, 2026 · Phase 2: Protocol core
  1

• fix(admin): Greptile follow-ups from #941

  Admin Consolebug
  cameri/nostream#985 · Filter by author Ferryx349 opened on Oct 25, 2026
  

• relay: two sentences around the CLOSE-during-mint test claim more than it proves

  bugfactoryrewriterust
  cameri/nostream#984 · Filter by author chappie-daemon opened on Oct 25, 2026 · Phase 2: Protocol core
  1

• relay: the invite-mint-plus-CLOSE combination is covered by no test at the wire

  bugfactoryrewriterust
  cameri/nostream#983 · Filter by author chappie-daemon opened on Oct 25, 2026 · Phase 2: Protocol core
  1

• relay: a close-aborts-read test stays green under the delay it exists to catch

  bugfactoryrewriterust
  cameri/nostream#982 · Filter by author chappie-daemon opened on Oct 25, 2026 · Phase 2: Protocol core
  1

• test: the filter's created-at endpoint can be wrong by 100x and its parity suite still passes

  bugfactoryrewriterust
  cameri/nostream#981 · Filter by author chappie-daemon opened on Oct 25, 2026 · Phase 2: Protocol core

• Port the capture aborted-union detail: a wrong-typed field answers Invalid input, not the field message

  bugrewriterust
  cameri/nostream#979 · Filter by author chappie-daemon opened on Oct 25, 2026

• relay: a publish racing a kind-62 vanish request survives it

  bugfactoryrewriterust
  cameri/nostream#975 · Filter by author chappie-daemon opened on Oct 24, 2026 · Phase 2: Protocol core

• relay: the CLOSE-during-mint test synchronises on a 50 ms sleep and can fail under load

  bugfactoryrewriterust
  cameri/nostream#963 · Filter by author chappie-daemon opened on Oct 24, 2026 · Phase 2: Protocol core
  1

• relay: extra frame elements are ignored where the capture rejects them

  bugfactoryrewriterust
  cameri/nostream#961 · Filter by author chappie-daemon opened on Oct 24, 2026 · Phase 2: Protocol core
  1

• relay: a float-spelled timestamp is rejected, which the capture accepts

  bugfactoryrewriterust
  cameri/nostream#960 · Filter by author chappie-daemon opened on Oct 24, 2026 · Phase 2: Protocol core
  1

• relay: the 8 MiB frame bound is per socket and sockets are unlimited

  factoryrewriterust
  cameri/nostream#959 · Filter by author chappie-daemon opened on Oct 24, 2026 · Phase 2: Protocol core
  2

• relay: inbound frames dispatch out of order, so a CLOSE can overtake its REQ

  bugfactoryrewriterust
  cameri/nostream#958 · Filter by author chappie-daemon opened on Oct 24, 2026 · Phase 2: Protocol core
  1

• rewrite: record the CLOSE-aborts-read decision the port already makes

  documentationrewriterust
  cameri/nostream#957 · Filter by author chappie-daemon opened on Oct 24, 2026 · Phase 2: Protocol core

• test: census rows may overstate coverage

  bugfactoryrewriterust
  cameri/nostream#956 · Filter by author chappie-daemon opened on Oct 24, 2026 · Phase 2: Protocol core

• test: the replay oracle never asserts silence

  bugfactoryrewriterust
  cameri/nostream#955 · Filter by author chappie-daemon opened on Oct 24, 2026 · Phase 2: Protocol core

• relay: subscription id length is measured three different ways

  bugfactoryrewriterust
  cameri/nostream#954 · Filter by author chappie-daemon opened on Oct 24, 2026 · Phase 2: Protocol core