1997-04-09 - Re: Anti-Spambot: what algorithm should be used?

Header Data

From: dlv@bwalk.dm.com (Dr.Dimitri Vulis KOTM)
To: freedom-knights@jetcafe.org
Message Hash: 8bcf47cb742bd7d5526c0ef99ab60f7cf03900a0d36de1d2636660643ebb6b7f
Message ID: <62aw5D4w165w@bwalk.dm.com>
Reply To: <3.0.1.32.19970409133818.009f7360@localhost>
UTC Datetime: 1997-04-09 15:13:38 UTC
Raw Date: Wed, 9 Apr 1997 08:13:38 -0700 (PDT)

Raw message

From: dlv@bwalk.dm.com (Dr.Dimitri Vulis KOTM)
Date: Wed, 9 Apr 1997 08:13:38 -0700 (PDT)
To: freedom-knights@jetcafe.org
Subject: Re: Anti-Spambot: what algorithm should be used?
In-Reply-To: <3.0.1.32.19970409133818.009f7360@localhost>
Message-ID: <62aw5D4w165w@bwalk.dm.com>
MIME-Version: 1.0
Content-Type: text/plain


Michael Johnson <Michael.Johnson@mejl.com> writes:

> Dr.Dimitri Vulis KOTM wrote:
> >One problem is that a lot of people put fake addresses in the from:
> >fields. Why waste good e-cash on e-mail to addresses that bounce?
> 
> That's the best kind for the payer, because ecash(tm) is not lost once you
> send it. You can cancel the payment if it bounces or after a specified
> amount of time. That's the double spending protection in ecash(tm), the
> first person to deposit a specific coin gets the money.

That's a good feature.  Other than raw e-cash, Alice could be sending out
messages like "Here's a random token: return this token to redeem your
cash". Also instead of general-purpose cash, Alice could be sending out
soft tokens only usable at her site: mention Alice's 900 number, receive
an e-mail with a secret code that allows you to FTP a single x-rated
picture from Alice's Web site.

---

Dr.Dimitri Vulis KOTM
Brighton Beach Boardwalk BBS, Forest Hills, N.Y.: +1-718-261-2013, 14.4Kbps





Thread