CapedCrusader reported a discrepancy where a new user appeared unsilenced in the admin profile but displayed a system message stating they were silenced for “typing too fast” after innocently copy-pasting. dax initially advised checking the Permissions section in the user’s admin profile to unsilence them. However, codinghorror clarified that the user had already been unsilenced, explaining that the visible message was merely a log of the past event. Epi320 subsequently asked how to prevent automatic silencing triggered by moderator flags, while leungameta questioned if a specific code path indicated a bug. Later, Lydia2 encountered a UI issue where the “unsilence” button was missing. Bas suggested toggling the “silence” button to reset the state, which Lydia2 confirmed resolved the issue by revealing the unsilence option. Bas noted the workaround was successful but requested reporting if the UI state error recurs.
Very grateful that Discourse shoots down spam. No human community can exist with bots littering everything.
However, when a new user innocently copy & pasted her post, it appears that our “sysadmin” silenced her automatically. (Screenshot: 2019-01-08_1837 - TechSmith Screencast)
When I check her “Silence” status, she doesn’t appear to be silenced.
Yet this user has received several replies to her post and not responded in a few weeks. How do I unsilence her (if she is silenced)?
Thank you, @dax. So her profile says “Silenced? No”.
Yet I got this message next to her post:
“@system silenced this account until December 25, 3018. Reason: New user typed too fast”
Which is correct though?
Her profile in admin that says not silenced, or the message above that appears on her post with a memo icon 
next to her username and says she’s been silenced?
Someone unsilenced that user. So you’re seeing a log of past events.
Oh, I see. Thanks Jeff.
This helped me a lot!
But I have a similar problem.
How do I stop the system from automatically silencing a user because of a admin/moderator flag?
Thanks!
Is there a bug related to hiding/silencing of posts in Discourse code?
Intended behaviour or no?
Hi Lydia,
Seems that that isn’t how it’s supposed to look, not sure what happened 
If this is a one-off, could you see what happens if you click the “silence” button? Maybe that just resets the state to something proper
Thanks, I clicked the “silence” button to silence the user, and then the “unsilence” button was shown.
Task failed successfully 
Do report back if this happens more often though, it’s not a state the system should be in
