I was thinking the same thing. In fact instead of what I was planning to work on next, I'm going to build the moderation tool website for chorus.

Back in June I did some work with fiatjaf on NIP-86 https://github.com/nostr-protocol/nips/pull/1325 to create a uniform interface between relays and management software. And chorus supports it on the backend (at least partially). But I'm unaware if anybody has built a NIP-86 front-end web tool designed to moderate relay content yet (showing a queue, 1984 reports, detecting impersonation, etc, etc). So tomorrow I'm going to write some VueJS, something I haven't done for awhile. But I can already tell it is going to be a big project in its own right and so many other nostr devs... someone must already be onto this, right? Do you know of any? A fuck it, I'll just do it my way anyways. I've never been cured of not-invented-here-syndrome.

yeah I like your take on it, I was thinking a very simple API like client requests relay’s metadata - response shows supported NIPs etc. and then some general-purpose key:value interface for arbitrary data?

Something small that could still be put behind an npub interacting via NOSTR itself as the interface, eventually, i.e. silent DM the relay API queries and commands, ecash 🥜 optional 🤔

Reply to this note

Please Login to reply.

Discussion

No replies yet.