@Yvette That question was bumped just because he was on the blacklist prematurely. That's what Smokey reported. That Q was a false positive due to the erroneous blacklist.
You are misunderstanding. 1 post and 1 comment WAS abusive. The user has dozens of other posts and comments that are still fine. The blacklist was premature and already caused a false positive.
Furthermore, he has not spread his rage to other posts and comments.
I think > I got the answer I looked on another stack flow chat question and used the code and implemented it into mine. It was with resource. So to the fucking douschebags that gave me negative points go fuck yourselves.
is totally unacceptable
If that does not get a user of any rep black listed, then I do not know what would.
I understand what you are saying, but I am disagreeing that the user should not be blacklisted. Isn't it better he be blacklisted and then if his next post (not a previous post) is ok, he can be removed, rather than the other way around?
Should we drop these brackets? Looks like some people from Asia are in the habit of using them to tag their posts in title, as is probably customary on their forums.
@Randal'Thor Its how many request smokey has done to the SE api of those sites, 1 request can contain multiple posts, and smokey does this off-the-peak-hours, but waiting longer between API calls means that spam reporting is delayed until the post has been retrieved and checked
@Randal'Thor Smokey picks up question url's from the realtime page, it places the ur's it gotten in a queue or waiting row. This waiting queue is per site. If the amounts of urls in a certain bucket exceed a certain number, smokey will ask the information about those posts in a single response and then checks every retrieved
post body for spam, every time it makes a request it will add 1 for that sites total, and that is what it just printed out
@Randal'Thor API requests made per site. Smokey uses the websocket to get notified of everything coming in; the websocket doesn't provide the entire body, nor a number of other details about the post. In some cases, if Smokey needs those details, it makes a request to the API to fetch them; those are counted and that's what you're seeing.
We are required to bundle every site's requests in such a queue, because we can only make 10000 requests a day, and the amount of answers + questions posted exceeds that number
@Randal'Thor A persistent connection. Standard web HTTP connections are dropped by the server when it's completed giving you the content you want. Websockets keep the connection open, so they can be used as a stream of data.
@Randal'Thor In theory: yes, but remember that spammers want views to their posts, spamming a non-active site doesn't earn them more views. The default queue size is 2, so every 2 posts that show on the realtime feed, a scan is made
Its mainly the larger sites like stackoverflow (5), serverfault.com (10) or math.stackexchange.com (15) that have bigger than normal queue sizes
