wakoinc on Nostr: I’d start with a white label relay-as-a-service provider, where it’s targeted ...

I’d start with a white label relay-as-a-service provider, where it’s targeted toward an individual or business relay where only they can publish, or alternatively with a community join mechanism, which grants access to either read, publish or both.

We’re lacking the client UI to select which relays to post to today, so perhaps the relay can have publish rules/filters to only accept events being posted in relation to existing channels - similar to discord, slack or teams. We’re also lacking client channel support.

You can moderate as much as you like. Delete events from the relay (abuse, time based, spam, etc), block users, promote moderators, etc. you can review all reports. You can charge to publish events (likely just as a spam deterrent) or even a regular membership fee. Basically a relay administration portal.

The client app UX would be intended to only show data from that single relay (at a time) - which prevents external events (like those from outside the community) from showing to users. Obviously users can opt to see those events too if desired.

Ultimately we need more relays that are topic, purpose, or community focused - and we need to make starting a new relay as easy as possible - all while avoiding wider network censorship or decentralised moderation. We need a way to, not only follow someone, but also follow topics or join communities - or risk Nostr staying an event stream.