From owner-freebsd-isp Fri Apr 18 17:43:30 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA16926 for isp-outgoing; Fri, 18 Apr 1997 17:43:30 -0700 (PDT) Received: from pinky.junction.net (pinky.junction.net [199.166.227.12]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id RAA16912 for ; Fri, 18 Apr 1997 17:43:26 -0700 (PDT) Received: from sidhe.memra.com (sidhe.memra.com [199.166.227.105]) by pinky.junction.net (8.6.12/8.6.12) with ESMTP id RAA01000 for ; Fri, 18 Apr 1997 17:43:24 -0700 Received: from localhost (michael@localhost) by sidhe.memra.com (8.6.12/8.6.12) with SMTP id RAA22726 for ; Fri, 18 Apr 1997 17:38:22 -0700 Date: Fri, 18 Apr 1997 17:38:21 -0700 (PDT) From: Michael Dillon To: freebsd-isp@freebsd.org Subject: Re: News... In-Reply-To: <199704181636.JAA23603@charmed.wilshire.net> Message-ID: Organization: Memra Software Inc. - Internet consulting MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 18 Apr 1997, Riley J. McIntire wrote: > And the gun is at the ISP's head: Subscribe (or provide) > these groups, or become liable for content I don't believe this is true. ISP's can drop any newsgroups they want or drop messages due to non-content related criteria, such as encoded files or large messages, and still not be liable for content. You become liable for content when you examine the content and drop messages based on that or when you edit the content. But encoded files are not truly messages and could be dropped safely, IMHO. Of course I am not a lawyer and I have not yet asked any telecom lawyers to consider this idea of eliminating files from USENET. > So, change how large binaries are distributed. Use web push > tecnology. Use ftp. Use news for what it was intended: text > messages and discussion. And incidently put the onus of content > responsibility at the source. Exactly! Michael Dillon - Internet & ISP Consulting Memra Software Inc. - Fax: +1-250-546-3049 http://www.memra.com - E-mail: michael@memra.com