1996-12-31 - Re: Hardening lists against spam attacks

Header Data

From: Alan Bostick <abostick@netcom.com>
To: ichudov@algebra.com
Message Hash: 4254bb6fa176f0e79c6fa11fad4106f6c65f1cf20df237f24e959ffc44745737
Message ID: <Pine.3.89.9612310958.A19648-0100000@netcom16>
Reply To: <199612310833.CAA03527@manifold.algebra.com>
UTC Datetime: 1996-12-31 17:43:37 UTC
Raw Date: Tue, 31 Dec 1996 09:43:37 -0800 (PST)

Raw message

From: Alan Bostick <abostick@netcom.com>
Date: Tue, 31 Dec 1996 09:43:37 -0800 (PST)
To: ichudov@algebra.com
Subject: Re: Hardening lists against spam attacks
In-Reply-To: <199612310833.CAA03527@manifold.algebra.com>
Message-ID: <Pine.3.89.9612310958.A19648-0100000@netcom16>
MIME-Version: 1.0
Content-Type: text/plain





On Tue, 31 Dec 1996 ichudov@algebra.com wrote:

> Send a number of unique tokens to each subscriber each day.  Enforce a
> rule that only posts with valid current tokens may be accepted. The
> number of tokens should initially be very small (say, one per day) and
> then should be quickly increased to a sufficient number, like 10 or 20,
> as the subscriber shows a record of using tokens properly (as defined by
> acceptable content rules).
> 
> A database is kept as to who was issued which tokens.
> 
> If tokens are used improperly (to post off-topic materials) the 
> offending subscriber is denied any further tokens.
> 
> The problem of this scheme is (besides its cost) that anonymous users
> will not be truly anonymous.

This scheme wouldn't necessarily map True Names to tokens; merely
list subscriptions.  If an account at a nymserver were to subscribe,
there would be no way to identify the account holder.

The real problem is that there could be a lot of subscriptions
from a site like  nymserver.bwalk.com . . . .

Alan Bostick               | I'm not cheating; I'm *winning*!
mailto:abostick@netcom.com |      Emma Michael Notkin
news:alt.grelb             | 
http://www.alumni.caltech.edu/~abostick






Thread