The error message you guys are getting is the 90 second warning. I think I mentioned in another post that we would have to see whether SMF would properly display the new 90 second message I created. Clearly, it doesn't. I'll try to make some time today to create a new, shorter message. I'll also be turning the 90 second flood control back to 30 seconds after Draft night. The waiting will all but disappear then.
As for this other thing...
Can you make an exception to the 90 second rule for certain IP addresses? That is, IP addresses that are proxy servers for companies that have 50,000+ employees, of which there are more than one celtics fan logged in here posting at any given time??
and
Based off what Roy said earlier, yes, which means that when you have two (or more) people on the same IP, they keep locking each other out and resetting each others' timer...quite annoying.
Brick James, this problematic scenario you mentioned here about how people logging into CelticsBlog from a common intranet behind a common firewall step all over each other simply doesn't happen. This website tracks not only a main IP address but also individual machine addresses coming from that IP. The site also uses unique login sessions for each logged in user. Thus, the site keeps the activities of all users separate from one another -- even ones coming through proxy server setups.
So individuals connecting here from intranets from home or work are all tracked individually and all use individual login session authentication. This is not only how CelticsBlog works, it is how ALL login sessions work. How else would more than one person on a LAN or coming from a proxy connection such as what AOL uses that is constantly changing IP addresses during sessions be able to login here at the same time or stay logged in otherwise? How would the site be able to manage your posts properly, track what you've read and what you've not read and so on?
There is nothing wrong with how CelticsBlog is currently running. The site and its database are fine and our enterprise-class server's health is good and we have Tier One level connectivity to the internet. I do know that subscribers with at least one and possibly more ISPs in the Eastern United States have recently experienced severe slow downs in their high-speed services from home and office due to upstream problems encountered by those service providers.
One CelticsBlog member contacted me just a few days ago experiencing this very issue. His home computer was connecting to CB very slowly. However, his laptop which used different upstream connectivity dished up CB just fine. The difference was that for whatever reason, his home computer was having trouble connecting to CB because of the path of upstream service providers it was using whereas the laptop wasn't. Had the home computer used a path like the laptop, he wouldn't have experienced the slow down with it. Anyway, no big deal. Service problems like that are usually very short-lived.