We're back on but for how long I do not know.

[Guest guest]

Dear Group,

 

We're back on but for how long I do not know. Our group was shut down

from this morning to this afternoon.

 

It said temporarily unavailable to requests for archives or messages.

 

I couldn't find any others that also we're " unavailable " so the

" technical glitz " seems to be us.

 

F.

[Guest guest]

Frank,

 

That's the message you get if you view too many messages per hour, no

matter what group you're in. It locks your IP out and gives you that

message. It clears after a few hours.

 

When running the archiving script I had to set it to read a message once

every 3 minutes or else it would hit the wall in about 60 seconds if I

continually viewed pages one right after another.

 

Although it is intended to stop abuse from scripts, I've run into the exact

same thing while browsing through archives of multiple groups. It's

possible with a high-speed connection and fast reading (skimming) by a

regular person to hit 's limit of message reads per hour.

 

I wouldn't suspect anything bad going on. It's just 's sensitive

automated self-defense mechanism.

 

David

 

 

(Answer to David)

 

Hi David,

 

The only thing is that I didn't read any messages,

so why would it lock me out?

 

 

Frank

 

 

 

 

At 06:10 PM 8/17/2004, Frank wrote:

 

>We're back on but for how long I do not know. Our group was shut down

>from this morning to this afternoon.

>

>It said temporarily unavailable to requests for archives or messages.

>

>I couldn't find any others that also we're " unavailable " so the

> " technical glitz " seems to be us.

[Guest guest]

At 07:34 PM 8/17/2004, Frank wrote:

>Hi David,

>

>The only thing is that I didn't read any messages,

>so why would it lock me out?

>

>Frank

 

Humm.... could be just some other network error. Working with web systems

and unix systems from experience, such glitches are a fact of life. Or it

could all be a great big conspiracy :-) I'll put my bets on the simpler

explanation - a technical glitch.