What I decided to do with chorus is that the inbox events are visible only to the people that the relay serves, which in my case is only 3 people, and the event's author.... until I actively approve them for public view. This prevents illegal content from being disseminated from my relay (even if it might arrive and get stored). The downside is that some people watching the conversation don't see the conversation in real time (if they however follow the stranger, they will see it from the stranger's relay). Sometimes I may go many days without moderating events on the relay, I've been pretty lax about it.
Login to reply
Replies (2)
This is an interesting solution. Thanks for sharing! Haven could sort of do the same for the Inbox relay, for example, provide an optional admin interface where folks could release or deny events they’re tagged in (all behind a flag; by default, it would simply auto-release all events). Then it’s up to each relay operator to "validate" the npubs however they see fit. If they really want to go out of their way to procure people’s documents, face scans, or whatever, that’s totally up to them and outside Haven’s scope.
I'm getting so many requests and ideas that require an admin page… Haven really, really needs a frontend person, or you folks will soon have to deal with my HTMX-powered "lazy backend" UI 🤣.
@ChipTuner @MichaelJ This isn't a dumb idea. A waiting room.