Patrick O'Keefe

Thanks for adding this. 😉 As I've discussed with @Matt, it's been a total game changer in communities I've managed in the past. In the right communities, it can drastically reduce the time needed to moderate around issues that members can simply take care of themselves.
For example, if a word or term is not allowed, some members will always try to circumvent it, so toss that to the side. For the rest, all well-meaning members or members trying to follow the guidelines, the process will be something like:
Member posts inappropriate word > other members must see it > moderator must see it > moderator must remove it > moderator must contact member > moderator must document removal > member must then read the message about how their post was removed, which will then elicit a reaction of some kind, positive or negative, and they may choose to add back the post in a modified form.
But with this feature, the process becomes: Member tries to post inappropriate word > member is notified it is not allowed > member adjusts their own post, so post is not taken down. We have almost completely stopped moderating for profanity in one of the communities I manage because of the introduction of this feature.
I should say, I don't see these matters in terms of "censorship" and "free speech" or being "nice," just in a sense of what practically happens with responsibly-managed online communities and what can make them work a little better, in some cases.
When folks talk about getting members involved in moderation and working collaboratively, this is one way to do it. And, of course, it's an option. I'd never recommend this be something that is forced on everyone, just like I wouldn't recommend a word censor list be forced on everyone. But for those working in specific communities, this could save them a lot of time, while creating a better overall member experience.

Thanks so much for sharing the show, @Matt! Really enjoyed the conversation.
Sorry for any downtime, @Joel R! We are on a ridiculously old VPS, and I have a new one ready to go, but the podcast and my day job have just been killing me lately, so I haven't been able to find time. I can't wait to get my sites switched over!
Patrick

Thanks so much for sharing the show, @Matt! Really enjoyed the conversation.
Sorry for any downtime, @Joel R! We are on a ridiculously old VPS, and I have a new one ready to go, but the podcast and my day job have just been killing me lately, so I haven't been able to find time. I can't wait to get my sites switched over!
Patrick

Interesting podcast, excellent interview.