response 45 of 176:

Apr 27 00:32 UTC 2001

resp:44

(you're joking, right?)

response 47 of 176:

Apr 27 02:38 UTC 2001

It doesn't normally take 30 seconds for me to move from one item to 
another in Backtalk.  The speed of web browsing on Grex is about what 
I've come to expect from other sites.  Maybe I'm just too used to my 
28.8 modem connection, and when I've had more bandwidth for a while I'll 
start to get annoyed with sites that don't load instantaneously.

response 49 of 176:

Apr 27 12:55 UTC 2001

resp:46

(from Arbornet's "support" command):


                           Patron       Member       Guest

Inbound telnet ports        64           56     48 from Michigan,
                                                  28 otherwise


(again, you're joking, right?)

response 51 of 176:

Apr 27 15:06 UTC 2001

resp:50

("As a current Board member and former staff member, I am pretty 
convinced I know more about what is going on that you do?"  that's 
just *too* easy.)  :P

(again, you're joking, right?  I haven't even addressed site-bans 
yet.)  ;)

response 53 of 176:

Apr 27 15:33 UTC 2001

Site-bans are also "normal": grex uses them as well..
Any admin uses them.
Only an idiot would NOT use them.
(For what and why is your issue).

response 55 of 176:

Apr 27 16:32 UTC 2001

resp:52

(so you admit that such limitations had been implemented?  I'll 
grant that the text I cited was revised only as recently as March 18, 
2000, so if Arbornet has moved away from limiting tty allocations 
based on donor status [of which I was aware] and IP address [of which 
I was not aware] since that time because of the actions of a script 
kiddie from Brighton and a rogue staff member, then cheers to them.  
that doesn't explain away the xenophobic attitude apparently supported 
by most of Arbornet.)

(then again, you seem to think that Chinet moved to NT along with 
CBBS.  ;P  you might want to look at the finger output from 
chinet.chinet.com again.)  

resp:53

(in the interest of clarifying the misinformation you seem to provide 
so willingly, I'll note that Grex used a site ban once, as previously 
posted in the Coop conference, when contact with a particular site's 
sysadmins failed to yield productive results.  it was a big deal then,
and was lifted fairly shortly thereafter.  if you're aware of any 
other time Grex has used a site ban, feel free to point it out.)  :P

---

(frankly, if the only things people can pick out about resp:37 are
the mentions of port allocations and Backtalk, then I'm pribly very
much on the mark.)

(jep, out of curiosity, what sort of net connection are you using?  
I'm currently using a cable modem, and never have to wait more than 
a minute for a page to load, even with a full 20 responses.  I had
similar response times while in Québec, using whatever connection
Université Laval had at the time.  have you considered that perhaps
the delays in Backtalk aren't necessarily on Grex's end?)

response 59 of 176:

Apr 30 01:42 UTC 2001

Grex does "block sites" (using tcpd) with some frequency.  Usually these
attract no notice and generate no complaints because they involve sites
*only* used by a vandal.  The most recent case involved a mail bomber
from Poland who liked to running a mail based DOS attack involving us
and about 2-3 other "free" Unix sites.

response 61 of 176:

Apr 30 07:42 UTC 2001

Well yeah, it probably would have to be cleaned up and rack mounted.  It would
have to be moved as well, meaning that it wouldn't be much more work for Grex
to rack mount its stuff than it would be for anybody moving into a colo
facility.  Grex even has that rack mount Sun 690 case sitting in the Pumpkin.

Anyhow, Grex's current cabling mess is not a feature.  Stuff would be much
more managable even wehre it currently is if that were cleaned up.

response 63 of 176:

May 2 23:28 UTC 2001

I'd be interested in seeing photos of the existing wiring mess if anyone
wanted to take the time to put them on the web.

I think if Grex could find the right friendly colo provider, colo would
be a good way to go, but my experience also indicates that if you don't
personally know some of the people at the colo facility, life can be painful.
(At one point, I was working for a company that hosted its web server at Level
3.  On two occasions, they lost our network connection.  I physically went
over there, since it took all of ten minutes to walk from the office to the
colo facility, and then got to call the people in Denver to get the problem
fixed, and the folks in Denver just didn't seem to care all that much.
In spite of the fact that we were paying like $1200/mo for the rack and
bandwidth.)

response 65 of 176:

May 5 05:00 UTC 2001

$1200/mo is a lot more than we pay now.  If that's the going rate,
switching won't save us any $.  Another factor to consider is: right
now, the pumpkin has extra storage space for spares, future development,
etc., essentially "for free".  A colo deal is *very* unlikely to include
such space.  That means any spares, development work, etc., would have
to take place "elsewhere" - either in space we rent for the purpose (in
which case we're right back to the pumpkin case), or in people's private
homes.  We've had a policy in the past of avoiding using people's
private homes for storage - and in the cases where grex has violated
this (including the CE warehouse which we got "for free") it has never
worked well in the long run.

An additional factor to consider is "who" has "what" kind of access.
What we'd like to have is unlimited 24 hr access for about 6-8 staff
members.  Most of the work done will be after hours or weekends, because
that's when our volunteer staff has time.  What we found is that colo
deals typically only include access during "business" hours, and usually
want to limit access to the smallest # of people possible -- 1-2.  This
is very similar to the type of access we had at CE.  This works great,
as long as the equipment works and no upgrades are done (or are planned
*very* carefully in advance).  It also works well for most commercial
businesses, which have full-time staff during regular hours, and enough
budget to replace any or all hardware if it's even remotely suspected of
being flakey.  It works terribly if something goes flakey and one is
trying to conserve money and not replace things until proven guilty, and
it really sucks when something goes dead at the start of a long weekend.
We had both of these problems at CE.

response 67 of 176:

May 6 01:42 UTC 2001

There are rare cases of people staying at ISP jobs consistently.  However,
I don't know of any such people around Ann Arbor.