yeah, there's a number of issues plaguing this business with the shitty clients but what i'm proposing to do bypasses their shittiness and also creates an entire ecosystem of relay service providers, and eliminates the islands in the network

i also think the relay needs to have a run mode where it isolates subscribed users, who can be added by the administrator, but also allows a two way flow for designated types of traffic, such as messages tagged with a particular group so you can have stuff like issues boards, public support messaging, and so on, while keeping team chat and forum private and not distributing it

of course, because nostr is self-authenticated messages, users can leak internal stuff but you could also have "watchtower" style services that the business runs that catch this and alert administrators of a leaker 

 oh yes, and it does need a slightly custom client that adds identifying tags to published messages, and an auth flow that disallows reading or writing to the relay without this extra auth step, it can't just be based on npub and auth

and the auth of course requires teh client to be slightly custom in that it SUPPORTS FUCKING NIP-42