We all know that sometimes you click New Posts button just one time and still get the 120 second warning. I mean, yeah, sometimes you click twice by accident, but lets face it, that warning pops up by accident sometimes as well even when you did nothing wrong.
Just now I got this warning.
Read that text carefully, I’ve never seen that one.
Leap-second.
Always safer than leaping first.
I’ve tried multiple times to look at your Photobucket link and every time I do I get a malware box that jumps in front of the image and invites me to download “MPlayer upgrade.” Can you copy the text into this thread so I can read it? I’d be most grateful.
Ironic.
“This forum requires that you wait 120 seconds between searches. Please try again in 121 seconds”
It says “This forum requires that you wait 120 seconds between searches. Please try again in 121 seconds.”
One of the hamsters requested a break, so they added a second.
More seriously, the software probably starts a 120 second countdown timer, during which you can’t post. After 120 seconds, the block is still in place, and the counter expires. The block is then removed, so 1 second after that (or in other words a total of 121 seconds later) you can post.
It does look funny when you catch it right during that first second though, doesn’t it?
That doesn’t happen, I’ve never heard of it happening so it’s probably not my link but you. If you could get me a screen shot of the error I’ll send it to the admin.
Sorry, had to do it.
But seriously, it’s just a photobucket link, you’ve probably got some malware on your computer.
FWIW, I was able to view it from both my work and home computers with no issue.
The two hardest problems in computer science are cache invalidation, naming things, and off-by-one errors.
I was going to correct you by changing that to ‘the 10 hardest things…’ then I read the last one again.
I’ll mention it to Jerry. Haven’t seen this message with “new posts” before, but if you think about it, "show me all the new posts"is a search.
Again, we’re getting a lot of heavy traffic these days, I would bet the servers are a bit taxed. Sorry for your inconvenience.
I know. In fact, I’ve explained to many of the people over the years that complain that they can’t use the New Posts button as often as they’d like that after reading a post, to just hit the back button instead.
I was just posting this because of the 121 second thing. I’ve never seen that. I’m not that concerned about it, it was just strange.
It is annoying though when I get the error when I hit the button and I haven’t done a search (New Posts or otherwise) any time recently. But that’s pretty rare and not really worth looking into. It probably happens 2 or 3 times a week (not counting when I double click it by accident) and I probably hit that New Posts button hundreds of times each week.
I have to wonder if this is somehow related to SiamSam’s zapping problem. The server obviously thought it got two search queries and kicked back what it thought was the second one with the wait. Maybe both of these are related to an overloaded network connection somewhere (maybe on the SDMB server side?) and relate to TCP retries or something. If the server got what it thought were two login requests from SiamSam it could end up with zero seconds between them, which might cause a divide by zero exception which the system handles by zapping him.
Just a wild guess, and just throwing this out there in case it triggers anyone else’s ideas.
The problem there to me is that the zap, at least in my experience, isn’t immediate. It’s a minute or so after I open the first tab. I start at the main list, and control-click on the various links to open some of the fora. The zapping is often around the third one.
It might be something like one minute after I start.
I haven’t been able to use the “New Posts” search in the last day or so either. It keeps telling me to wait, even if it’s the first time I’ve clicked it that day.
Very clever. Now explain this one.
The server sentenced you to serve your delays consecutively, not concurrently. Take the plea bargain next time.
I have asked Jerry to inquire the server people to see if something’s going on. Or not.
