Oddbean

I've been experimenting with relay administration using notes sent from a GUI client, specifically leveraging my own kind 42021 note (note spec to follow). I’ve developed a basic proof of concept that allows Nostr relay operators (or other implementations if they eventually support this kind) to: - Ban or allow pubkeys and kinds from posting to your relay. - Delete stored events from a specific pubkey. -View the allow list for pubkeys and kinds. All of this can be done without the need to SSH into the server or store private keys on your relay or computer. This is just a test case—there are already operators managing relays through notes, but there isn’t a standard relay admin API yet. There’s also ongoing discussion about whether this approach is the right one or if relay operators should instead use a web client for management. I welcome any feedback or criticism of this approach and greatly appreciate anyone willing to test it out! https://github.com/UTXOnly/nostpy-gui #grownostr #relay https://i.nostr.build/Pw6YSXazcUJPIEQ4.gif

One off commands for now, Its basically just a single event kind with tags added to perform the moderation. I have seen discussion of replaceable metadata document which might be a better approach and would probably have a better chance of being adopted. I'm not sure what the best way to go about this is yet, this was admittedly a fire from the hip approach to just experiment and would put it out there for discussion.

if i was running a relay and wanted to manage via nostr notes, id probably use DMs and spec out supported commands (each relay, as a service, gets its own nsec and npub). this makes configuration viable from any client supporting DMs and ive been sucessfully using that approach with bots since early 2023

That is a good idea, I was managing a metadata updater tool via DM and it was working great but haven't worked on it in a while or pushed up that branch. I guess I could still construct the DMs in a GUI client with buttons but like the idea of any client being able to do that.

I have been following along here : https://github.com/nostr-protocol/nips/pull/1325 If that is where you're referring to? But haven't jumped in with any new ideas yet. I'm still weighing the merits of a request/response based approach (which this is) vs a single replace able event type. I will put this up for discussion in that thread soon though.