@Glorfindel That pattern looks like it's already caught by Bad ns for domain in body and Bad ns for domain in answer; append -force if you really want to do that.
This is a question and answer site for Charcoal, the volunteer organisation that stops spam on the Stack Exchange network. It's built and run by you as part of the Stack Exchange network of Q&A sites. With your help, we're working together to build a library of detailed answers to every question about on-topic.
Well, a primary question I have about it is: how open is it intended to be? So far, a significant selling point for the SmokeDetector project is that everything is open to all members of the Stack Exchange community (with very small exceptions for administration and privacy). The source code is open, all documentation is open and available to everyone on a public website, reports from SmokeDetector are sent to an open chat, and all (well almost all) discussions are in that chat.
The channel/team is currently not open to everyone. Users have to go through a sign-up process, which may, or may not, feel arduous to some users. It could be looked at as any information which we have on the channel/team is hidden/not public.
@Undo We've just gone through/are going through a period where we've been dealing with significant PR issues. Some of these have been about discoverability and information availability. I don't feel that putting information behind additional barriers is beneficial to general acceptance. At a minimum, we need to make clear, publicly, that the information is there and that anyone interested is welcome to join.
I do feel that it could be quite beneficial to have this, particularly if it's available to everyone and we make it easily discoverable that the information is there.
As long as the important bits are mirrored on the wiki, we should be fine. If someone attacks us over beta testing SE-provided software... I think I can justify it.
