From: Karl Chen <quarl@cs.berkeley.edu>
Subject: Re: hashcash - buffer modification
Date: Wed, 15 Nov 2006 00:37:11 -0800 [thread overview]
Message-ID: <quack.20061115T0037.lthfyclt8aw@roar.cs.berkeley.edu> (raw)
In-Reply-To: <b4mbqn9uwvx.fsf@jpl.org> (Katsumi Yamaoka's message of "Wed, 15 Nov 2006 14:00:50 +0900")
>>>>> On 2006-11-14 21:00 PST, Katsumi Yamaoka writes:
Katsumi> I see no oddness there. I'll install the following
Katsumi> change in the trunk if no objection
Looks good; thanks.
Katsumi> BTW, how do you add hashcash headers when you write a
Katsumi> mail from scratch (i.e., the case where To and Cc
Katsumi> have not been filled yet)? I use `mail-add-payment',
Katsumi> not `mail-add-payment-async'.
We could add an overlay on the headers with modification-hooks
that adds asynchronous payment for valid email addresses if the
user hasn't modified headers for (configurable) 30 seconds.
--
Karl 2006-11-15 00:31
next prev parent reply other threads:[~2006-11-15 8:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-14 23:48 Karl Chen
2006-11-15 5:00 ` Katsumi Yamaoka
2006-11-15 8:37 ` Karl Chen [this message]
2006-11-15 14:22 ` gdt
2006-11-16 2:16 ` Katsumi Yamaoka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=quack.20061115T0037.lthfyclt8aw@roar.cs.berkeley.edu \
--to=quarl@cs.berkeley.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).