We got some feedback on twitter I wanted to respond to properly:
Why not enable pre-approval queue by default?
There are are a few biggish reasons we do not
-
The vast majority of Discourse installs out there do not have this setting enabled, in fact, I can only think of a handful of sites that add this. Even very big install.
-
Our built in spam measures catch most spam. Friction is high cause you need JavaScript to spam and we measure stuff like typing time and so on which automatically catches spam.
-
The Akismet plugin catches stuff that missed the automatic measures and is installed by default on our customers
-
At the moment handling the 2 queues (pre-approval and akismet spam) requires a site moderator. This can lead to quite a few situations where a post can be “in the queue” for hours or days, this drives away new users big time
Why is this so hidden?
The big reason is that, in general, we do not notice people need it. If people experience a spam attack we like to hear about it on meta and get as much details as possible so we can correct any of our automatic detection. Enabling “approve everything by TL0” is kind of giving up, so we try to discourage it.
There are also open UX issues and usability issues around approval queues that need to be polished if this feature is to be more prominent. In particular:
-
Why can’t high trust users (tl2) approve content in the queues?
-
Why carry around 2 lists (akismet and approval) of posts?
-
Why can’t mods approve in the context of a topic?
-
What happens if something sits in the approval queue for 1 week without being handled? (we send an email to remind to site_contact email, but this is a bit too hidden)