I have twice this evening tried to send something and gotten this message in the bottom left of the screen. The screen goes dim and doesn’t look look like the message sent, but if I try to resend it I get the “you’ve posted 1 times (sic) within 60 seconds -spam block is in effect and now have to wait 600 seconds before posting again” message. What is going on and what is an unsupported operand type?
A glitch which has been reported to the IT team
I got it this morning when trying to do a post report.
SO…I did the post report again…but got the 300 second spam block on my account!
Seriously…how was I supposed to know that my report had been sent when the message said otherwise.
I got it when posting to a thread that was apparently deleted by a mod partway through my post yesterday.
I forgot to flag @CCadmin_Sorin in my first post. Wanted to get the darned thing posted before getting another error message and getting a time block again!
Still happening today
To be fair, 11:43 p.m. yesterday is, for all intents and purposes, today. 
Thats when I reported it. Its not necessarily when it happened… which was a few times yesterday evening. Besides, one can’t post a report re: a community/forum issue when that (Q&E^)Q(#R^Q#). red bar thing thinks one is spamming CC.
Guys, as @skieurope confirmed, we have already reported the issue to the tech team. We hope to have this addressed as soon as possible, but we do work on limited resources due to the winter holidays. Thanks for bearing with us!
You usually ask us to keep you posted, @CCadmin_Sorin - so was just updating. Not sure when others experienced it, but I would estimate it happened to me twice last evening between 9-11 pm EST. and again around noon EST.
If this takes a while to resolve, we could use an alternate way to report problem posts or posters.
@lookingforward, these reports end up in a “moderating queue,” so we are seeing them, anyway. I think we’ve figured out the issue, but we have to confirm with Sorin. The holidays are definitely having an effect on response time.
Hopefully this is fixed now. Thanks for your help!