If this pattern were to take off I can see power-user centric apps for relay admin sitting alongside client apps. Which would be pretty cool for power users, and super interesting in organisational contexts.
How to you admin the whitelist? Are you editing flat files in code?
Do any relays have API endpoints for configuration which an admin app could build upon (add whitelist npubs, words, etc)?
Nailing community admin UI/UX is :110percent: my focus now.
This is the future of Nostr, for sure. It's the setup that maximizes the utility of a protocol that is distributed, but also (partially) intermediated.
I mean, we've had relay communities, the whole time, but nobody noticed until some of the communities were smaller. We've gone from one community to dozens of communities to hundreds of communities.
Our nostr:nprofile1qqsggm4l0xs23qfjwnkfwf6fqcs66s3lz637gaxhl4nwd2vtle8rnfqprdmhxue69uhhg6r9vehhyetnwshxummnw3erztnrdakj7qfqwaehxw309ahx7um5wghx26tww4hxg7nhv9h856t89eehqctrv5hsz8rhwden5te0w35x2cmfw3skgetv9ehx7um5wgcjucm0d5hsjmvd7t team is highly-focused on organisations, including our own. Nostr isn't a toy, for us, it's the basis for OtherStuff we're planning on marketing primarily B2B (although anyone can use it!), including to software development teams, churches, universities, small businesses, authors and publishers, etc.
We needed an architecture to make that happen, and relay-based communities is that architecture because it intermediates the complexity of Nostr to a community admin and curator.
There can be 1 to n npubs in a community.
