Article View: cle.config
Article #51Re: Proposal: stop the leaks
From: Mark W. Schumann
Date: Wed, 05 Jun 1996 00:00
Date: Wed, 05 Jun 1996 00:00
61 lines
2957 bytes
2957 bytes
In article <Hw6rx0E6AJhW090yn@mome.apk.net>, Sysop <MarchHare@mome.apk.net> wrote: >In article <4oghan$9qe@junior.wariat.org>, >catfood@junior.wariat.org (Mark W. Schumann) wrote: >>In article <GViqx47UlR2N090yn@mome.apk.net>, >>March Hare <sysop@mome.apk.net> wrote: >>>Hmmmm, well I thought we were talking about managing it, just that >>>we differ in the approach. >> >>No, it's *really* easy to manage velveeta. So easy that limiting >>the distribution of cle.* is irrelevant to stopping velveeta. You >>can do it yourself without involving other news admins. > >Huh? If you're going to quote me, at least don't get me confused >with the other guy. I spent a week (silly, I know) trying to figure out what you mean. Are you saying you didn't write that? >>If velveeta wastes your disk space, it's your problem, not the net's. > >Velveeta wastes everyone's disk space. I'd say it is a net problem. >I'm not the one suggesting a net solution. I'm not the one proposing >closing off cle.* groups, I'm the one that is suggesting that there is >another totally voluntary solution. Uh, yeah, whatever. Your news software is still broken. >>>So, went to the spool of c.o.o.a, pulled up article 68515. Sure enough, >>>the entire article is on the hard drive twice, not some pointer to the >>>other. >> >>And therefore...[drumroll]... YOUR software is broken! > >Well, duh. You having an off day, or what? I was responding to the >assertion that UUPC does not keep more than one copy of the article >on disk. I don't recall anyone asserting that either. Whatever. >It does. It is irrelevant to what I was saying, which I'll >state again that even one copy is a waste of resources. Let's not >get stuck on side issues. Deal. >I don't buy the argument that you should >have to crosspost to 400 newsgroups before getting cancelled, period. >The BI is a good measure overall, but it falls flat on this count. You can't even fit 400 newsgroups in a header anyway. See, velveeta is extremely easy to avoid. It is so easy that it doesn't require any solution at all, IMHO. Just apply the all-purpose bozo filter in your killfile and voila, it's gone. You can even (as someone here may have suggested, and heck, it might have been you) easily filter it out of your incoming or outgoing feeds, because of what velveeta is. -- Mark W. Schumann | ObCDA: Rep. Martin Hoke is a poopy-head.
Technical Details
Message-ID:
<4p5k19$83d@junior.wariat.org>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<4na8nl$89@madeline.INS.CWRU.Edu> <4nagtd$b3t@junior.wariat.org> <Hw6rx0E6AJhW090yn@mome.apk.net>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103394,b4524586926531f8 X-Google-Attributes: gid103394,public From: catfood@junior.wariat.org (Mark W. Schumann) Subject: Re: Proposal: stop the leaks Date: 1996/06/05 Message-ID: <4p5k19$83d@junior.wariat.org> X-Deja-AN: 158772763 references: <4na8nl$89@madeline.INS.CWRU.Edu> <4nagtd$b3t@junior.wariat.org> <Hw6rx0E6AJhW090yn@mome.apk.net> organization: Akademia Pana Kleksa, Public Access Uni* Site newsgroups: cle.config