1997-01-08 - Re: Sandy and I will run a cypherpunks “moderation” experiment in Jan

Header Data

From: Sandy Sandfort <sandfort@crl.com>
To: Black Unicorn <unicorn@schloss.li>
Message Hash: f99e716698b0061590d7e24425b063f0f7f54c1eb7ab781b00b945a9cfc26c42
Message ID: <Pine.SUN.3.91.970108130901.28929H-100000@crl.crl.com>
Reply To: <Pine.SUN.3.94.970105222016.23091B-100000@polaris>
UTC Datetime: 1997-01-08 21:32:54 UTC
Raw Date: Wed, 8 Jan 1997 13:32:54 -0800 (PST)

Raw message

From: Sandy Sandfort <sandfort@crl.com>
Date: Wed, 8 Jan 1997 13:32:54 -0800 (PST)
To: Black Unicorn <unicorn@schloss.li>
Subject: Re: Sandy and I will run a cypherpunks "moderation" experiment in Jan
In-Reply-To: <Pine.SUN.3.94.970105222016.23091B-100000@polaris>
Message-ID: <Pine.SUN.3.91.970108130901.28929H-100000@crl.crl.com>
MIME-Version: 1.0
Content-Type: text/plain


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                          SANDY SANDFORT
 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C'punks,

On Sun, 5 Jan 1997, Black Unicorn wrote:

> How will borderline posts be dealt with?  Posts that contain a great deal
> of content and thoughful discussion and still manage to contain flames?
> 
> Will flames be an automatic boot for a post (zero tolerance), or will they
> be balanced against post content?

Zero tolerance will be my first approximation.  I may modify 
that as I see how things really work out.  So far, though, I
don't recall see any of those "high content with flames" animals.
Most posts are one or the other.
 
> What is the threshold which, for example, constitutes an "insult" ?
> 
> "Louis Freeh couldn't identify a directed well managed crypto policy if it
> bit him on his pimple speckled ass."

Truth (and relevance) are a defense.  :-)
 
> "You are so turned around on this issue one is prompted to wonder if you
> have any background in higher education at all."
> 
> "For the new members of the list, [insert list member here] has a history
> of posting idiotic and useless posts, and generally wasting the list's
> time like an asshole."
> 
> All of the above?  None of the above?

Sorry Black Unicorn, no declaratory judgments.  Everything gets
posted one way or another.  Let's see how it works in the real
world.
 
> I believe the "flames" list should be maintained as long as possible.
> Continuing checks on the moderator (whoever it may be) are necessary and
> appropriate.  What better way than to directly provide a means to identify
> what the moderator has excluded?

This is my opinion as well.  However, John makes the very good
point that the unedited list has one very important advantage--
timeliness.  The other two lists (polite and flames) have a 
build in delay time because of the moderation.  I don't see it
as a problem, but John feels that quick turnaround is an 
advantage that some list members would prefer.
 
> A diversity of moderators makes a detailed stated policy on moderation an
> absolute must.

I agree.  We are not at that stage yet, however.  We are still
finding our sea legs for now.
 

 S a n d y

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~







Thread
https://mailing-list-archive.cryptoanarchy.wiki/archive/1997/01/f99e716698b0061590d7e24425b063f0f7f54c1eb7ab781b00b945a9cfc26c42/
mailing-list-archive.cryptoanarchy.wiki
CC-MAIN-2024-26
20442
application/http; msgtype=response
sha1:7VZ7JF2QK67SA2AQZCIKBLPDOVEACRIT
<urn:uuid:db40c1c5-f805-4a98-b001-9acbecbb73d4>
2024-06-18T05:37:03Z
185.199.110.153
text/html
sha1:RVYXXFXDP3PZ4K6WNTD34SUIDPDF7AIR
<urn:uuid:11030bd7-8622-4d16-afa9-8bfb4a1b83a2>
https://mailing-list-archive.cryptoanarchy.wiki/archive/1997/01/f99e716698b0061590d7e24425b063f0f7f54c1eb7ab781b00b945a9cfc26c42/
response
<urn:uuid:13b512e9-e8e8-4ef7-9f67-d2d37236b342>
isPartOf: CC-MAIN-2024-26
publisher: Common Crawl
description: Wide crawl of the web for June 2024
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-251
software: Apache Nutch 1.20 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.5-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/