I hardly ever see spam.. So I hunt for it where I see people complaining. This is the ultimate relay list spam setup right here. @Karnage has much thicker skin than I do for reals with this level of spam-relay inbox ๐ฅ



tldr
```
it is non-standard. Current NIP-01 only defines filter tag keys of the form #<single-letter> (#e, #p, #t, โฆ), and the matching convention is that relays index single-letter tags only. Newlay was being spec-faithful when it rejected #buzz-channel โ that's why the rejection message existed at all.
The non-standardness originates on the buzz side, not newlay's. Buzz's own Rust relay stores event tags keyed by their full name in Postgres, so it happily accepts filters on arbitrary tag names, and the buzz ecosystem quietly grew to depend on that: project events (kind 30621) and git repo announcements (kind 30617) carry a buzz-channel tag binding them to their home channel, and upstream de188ebf0 made buzz-acp query exactly that โ {"kinds":[30621],"#buzz-channel":[<uuid>]} โ before every agent turn. It's one of several buzz bridge extensions that already live outside vanilla nostr (search_mode: "prefix", the before_id paging cursor, top_level, etc.), most of which newlay already mirrors for drop-in compatibility. This one just hadn't been needed until the project-home lookup shipped three days ago.
```
Its far too many apple for me to 'deal with' rn..