🚀 go-pugleaf

In article <GViqx47UlR2N090yn@mome.apk.net>,
March Hare <sysop@mome.apk.net> wrote:
>In article <4o1k8t$i6g@junior.wariat.org>,
>catfood@junior.wariat.org (Mark W. Schumann) wrote:
>>Well, yeah, but the point is that /your/ host got one copy of the
>>article and turned it into <n> copies, and it is within your power
>>to make it stop doing that.  It doesn't become "spam" until you make
>>it so.  The massively crossposted article is just "velveeta" until
>>then, and velveeta is a lot easier to manage.
>
>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.

If velveeta wastes your disk space, it's your problem, not the net's. 

>>BTW, check your facts on UUPC.  I used that here for /years/ and am
>>quite certain that UUPC hands one and only one copy of a crossposted
>>article to the news spool, and it is SNEWS's unbatcher (if you're
>>using that) that makes the <n> copies.
>
>Nope, not using SNEWS.  Not even sure I know how :)  However, I checked 
>the news spool and found a crossposted article in comp.os.os2.misc with:
>
>Xref: mome comp.os.os2.misc:48273 comp.os.os2.advocacy:68515
>
>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!

-- 
Mark W. Schumann  | ObCDA: Rep. Martin Hoke is a poopy-head.