1997-08-06 - Re: JYA Up

Header Data

From: dlv@bwalk.dm.com (Dr.Dimitri Vulis KOTM)
To: cypherpunks@toad.com
Message Hash: 0cb575e6d44e81ca0dab9805647001179672d4d953b5dc8b73f69bc7ba9e211b
Message ID: <LJVZae1w165w@bwalk.dm.com>
Reply To: <1.5.4.32.19970806003415.00689254@pop.pipeline.com>
UTC Datetime: 1997-08-06 07:05:17 UTC
Raw Date: Wed, 6 Aug 1997 15:05:17 +0800

Raw message

From: dlv@bwalk.dm.com (Dr.Dimitri Vulis KOTM)
Date: Wed, 6 Aug 1997 15:05:17 +0800
To: cypherpunks@toad.com
Subject: Re: JYA Up
In-Reply-To: <1.5.4.32.19970806003415.00689254@pop.pipeline.com>
Message-ID: <LJVZae1w165w@bwalk.dm.com>
MIME-Version: 1.0
Content-Type: text/plain



John Young <jya@pipeline.com> writes:

> AOL/PrimeHost has reactivated JYA.
>
> AOL's story for the takedown is that our seldom used ftp
> component was being used by unidentified parties to traffic in
> warez and that it had nothing to do with the http part, "whose
> content does not concern us."
>
> Still, it's odd we did not get a call about the problem as was done
> a few weeks ago for a similar warez invasion. At that time, we
> offered to close our ftp, but the PrimeHost rep said no, we'll monitor
> it, as we do other ftps. I specifically asked to be notified if it
> happened again, but wasn't. And it's not clear why it took a
> week for me to find out what was what. Or why not AOL did not
> just close the ftp and leave the http operating.
>
> 'Course, maybe the  takedown was signal of distrust of JYA
> innocence. And a warning.
>
> Thanks to the folks who offered more help than the teapot
> tempest seems to have warranted -- so far.

Sounds like bullshit.

I urge you to find a more honorable upstream provider.
Preferrably someone who gets connectivity off of AGIS, who doesn't
censor content.

---

Dr.Dimitri Vulis KOTM
Brighton Beach Boardwalk BBS, Forest Hills, N.Y.: +1-718-261-2013, 14.4Kbps






Thread