Automatic silencing for "typing too fast" doesn't notify administrator

AI-generated summary

InterAction_studios reported an issue with automatic silencing for users who type too fast, where administrators are not notified of the silencing. The user was initially automatically silenced without notification, and after being manually un-silenced, they were automatically re-silenced again without notification. The “If a user is automatically silenced, send a message to all moderators” setting did not resolve the issue. However, the administrator did receive a notification after the user’s third attempt to post. rahim123 suggested that this might be a legitimate bug, referencing two related Discourse meta threads (1 and 2).

Recently I’ve come across several cases of users who:

(a) were automatically silenced but I was never notified (as an administrator) that this silencing took place

and

(b) user was automatically re-silenced (again, without notification) after manually being un-silenced.

Example:

From the point of view of the user:

As you can see, the user was first approved (I’ve turned on “Staff must approve all new user accounts before they are allowed to access the site.” option), then tried to post something which resulted in an automatic silencing (which I was never notified of). After manually un-silencing the user and them posting again, they were re-silenced (again, without notification to me).

After the first silencing, I went into the settings and turned on “If a user is automatically silenced, send a message to all moderators”, however this did not result in a notification either. It might be relevant that the site is also set up with an “approve post count” of 2. “min first post typing time” is set to 30 seconds.

I have un-silenced the user for a second time, and will report of any developments here.

Using Discourse 3.0.1

Update: The user tried posting for the 3rd time and this time I did receive a notification.

4 Likes

Looks like this might be a legitimate bug:

2 Likes