• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

.999 thread locked? Why?!

DrPizza

Administrator Elite Member Goat Whisperer
There was an original thread... it was locked because someone decided to post in it hundreds of times (and fill up email boxes for people who actually enjoyed that thread and subscribed to that thread.) Thank you for banning/giving a vacation to the moron.

But, a new thread was started on the same topic, so we could continue the discussion. There was no flaming going on, and except for a couple of people calling the OP a moron for continuing the discussion, the debate was quite lively. (and someone contributed something new to the argument by mentioning the hyperreals - a type of number that hadn't even been mentioned in the original thread.)

Why was the new thread locked? I can't see any reason.

It has been unlocked.

AnandTech Moderator
 
(Oh, before anyone suggests the thread was a repost... the original got locked due to circumstances beyond our control) "threadbombed?"

Out of curiousity, isn't there some way for the mods to simply edit a thread and remove the couple of hundred consecutive posts? Otherwise, it sets precident for anyone who simply wants to kill a thread. They could go to the library, sign up as a noob, and post 100 times or more to the same thread to kill it. I certainly hope that doesn't happen!
 
Originally posted by: DrPizza
(Oh, before anyone suggests the thread was a repost... the original got locked due to circumstances beyond our control) "threadbombed?"

Out of curiousity, isn't there some way for the mods to simply edit a thread and remove the couple of hundred consecutive posts? Otherwise, it sets precident for anyone who simply wants to kill a thread. They could go to the library, sign up as a noob, and post 100 times or more to the same thread to kill it. I certainly hope that doesn't happen!
Let's see.
<---Heads to library.................

 
That's kinda what I mean... if someone gets a bug up their butt, they just head to the library, log on, create a new account, and kill some threads with no repercussions. (ATOT Geek or someone just did it)

Wouldn't simply banning someone and editing the posts out simply make their efforts pointless, rather than successful? I mean, if I went to the library (I wouldn't), killed a thread, got a thread locked, then my new pseudo account was banned - no big deal to me! I'd have won!

I hope the nonsense with that stuff stops quickly,
And, I hope those of us who enjoyed the .999 thread can continue one way or another with that topic.

Thanks.
 
I agree that there needs to be a way to handle this "threadbombing" crap. I got over 5MB of email from that thread (2700+ 2KB emails) and I know a lot of people other than me were subscribed to it as well. Anandtech had to handle and pay of *all* of that wasted bandwidth. Fortunately they have invested in a great server infrastructure that could handle that load properly.

Zuni, doesn't fusetalk have some way of detecting this kind of thing when it starts? 2700+ identical posts, to the same thread, over a short period of time. One would think this could be automatically detected and the account of the person doing it locked automatically. The only solution I've seen put forward is a posting rate limit of 30 seconds (this was implemented in the Beta Forums a while back) but honestly that sucked horribly (although it admittedly worked).

I liked that thread, although I know a lot of people didn't. I didn't see the need for it to be locked.

I'll also point out that Anandtech Moderator originally deleted the thread, but they were nice enough to put it back and simply lock it. I think the Mods deserve a big thank you for that. :heart:
 
Originally posted by: TC2181
Agreed.

Heck, just get new Mods. We need a regime change.

rolleye.gif
 
Originally posted by: Kyteland
Originally posted by: TC2181
Agreed.

Heck, just get new Mods. We need a regime change.

rolleye.gif
Agreed. Makes me think he is a returning, banned user as he hasn't been here long enough to form that opinion.
The Mods ought to check him out.

 
Many boards now limit 1 auto notification on a thread until a revisit to the site. This would be easy to implement even if 'dirty coded' as a quick SQL statement ... another way would be to do a entry where there is a limit between each user triggering an autoreply. This should be thread based as many users post with 10 - 30 secs right down the line on 'bookmarked threads'.

 
Originally posted by: alkemyst
Many boards now limit 1 auto notification on a thread until a revisit to the site. This would be easy to implement even if 'dirty coded' as a quick SQL statement ... another way would be to do a entry where there is a limit between each user triggering an autoreply. This should be thread based as many users post with 10 - 30 secs right down the line on 'bookmarked threads'.

I think the 1 notification is something that should be implemented. You are right that it is easy to do, and is probably the best idea.
 
Back
Top