I think it's going to take me a bit to get comfortable with the usefulness if this proposition. I agree with the argument, but still not sure it works in the benefit of the user any more than simply begging for the operator to whitelist them, to which the operator would look at their past notes stored on another relay perhaps and choose to authorized them. Not to mention were simply discussing non-paid public relays I suppose. This also only works if the number of notes to review is low enough to interact. I think were just discussing a human high-level filter. I guess my final thought is, does my opinion matter here? This sounds like a relay feature/implementation detail. The relay should allow for this to be enabled/disabled and offer an admin interface for implementing this. My whole software dev MO is optional features. Build it, but let me turn it off/on. > As for making sure operators don’t simply forget about notes, maybe daily reminder emails? That’s what Mastodon offers. Also who am I to say what the operator _should_ do. What I do know is what I would do, and that's check it whenever I have a few seconds of "free" time. It would probably never happen, so that's my bias!

On my side, I was thinking more about personal or small community relays. But honestly, even at scale, it’s either a big team of human reviewers or a mix of that and algorithms à la big tech social mefis (and given the current state of things, I’d much prefer to go back to the army of mods). My take is: give operators the tools and let them decide. Want to whitelist everyone by default? Fine. Want to blacklist everybody but yourself by default? Also fine. Want a moderation queue? Here you go. Want to be notified about new items to review? No problem, just let me know the level of granularity you want for notifications. This is what we can do on the relay development side without imposing our own views.