1997-12-03 - hashcash spam throttle

Header Data

From: Adam Back <aba@dcs.ex.ac.uk>
To: pooh@efga.org
Message Hash: 9c5ca6a08b7e07137bfc54d5c612c6cddb0bbaf8f645f006d8898e09eae4d128
Message ID: <199712030044.AAA01172@server.test.net>
Reply To: <3.0.3.32.19971202094253.037e0654@mail.atl.bellsouth.net>
UTC Datetime: 1997-12-03 01:23:50 UTC
Raw Date: Wed, 3 Dec 1997 09:23:50 +0800

Raw message

From: Adam Back <aba@dcs.ex.ac.uk>
Date: Wed, 3 Dec 1997 09:23:50 +0800
To: pooh@efga.org
Subject: hashcash spam throttle
In-Reply-To: <3.0.3.32.19971202094253.037e0654@mail.atl.bellsouth.net>
Message-ID: <199712030044.AAA01172@server.test.net>
MIME-Version: 1.0
Content-Type: text/plain




Robert A. Costner <pooh@efga.org> writes:
> It's much like spam.  It's a very shortsighted view when a user says "why
> can't you just hit the delete button?"  This is an incorrect answer for a
> user who received one piece of spam, but whose small ISP, being the relay,
> lost all mail services for two days.

See HashCash: http://www.dcs.ex.ac.uk/~aba/hashcash/

Hashcash ensures that the would be spammer has to consume more
resources than you do.  Hashcash is arbitrarily expensive to create
and cheap to verify.  It's also decentralised and anonymous.

Adam






Thread