From: gdt@work.lexort.com
Cc: Andreas Seltenreich <andreas+ding@gate450.dyndns.org>, ding@gnus.org
Subject: Re: why does message-generate-headers take so long?
Date: Wed, 23 Aug 2006 11:34:01 -0400 [thread overview]
Message-ID: <smuk64zcvpy.fsf@linuxpal.mit.edu> (raw)
In-Reply-To: <87mz9vh49p.fsf@latte.josefsson.org> (Simon Josefsson's message of "Wed, 23 Aug 2006 17:15:46 +0200")
[-- Attachment #1: Type: text/plain, Size: 519 bytes --]
With async payments, the pain of hashcash is very low. And, this only
affects people with hashcash installed on their systems. So, I think
it's reasonable to keep it. What would be nice (I don't have the clue
level and my papers aren't in order...) would be to be able to rerun
the async payment processsing (that starts when a reply is created)
whenever there are addresses in the header (perhaps starting a few
seconds after the cursor is not in a header line).
--
Greg Troxel <gdt@work.lexort.com>
[-- Attachment #2: Type: application/pgp-signature, Size: 185 bytes --]
next prev parent reply other threads:[~2006-08-23 15:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-22 22:41 Ted Stern
2006-08-23 4:24 ` Andreas Seltenreich
2006-08-23 8:43 ` Simon Josefsson
2006-08-23 13:47 ` Wes Hardaker
2006-08-23 15:15 ` Simon Josefsson
2006-08-23 15:34 ` gdt [this message]
2006-08-23 8:34 ` Elias Oltmanns
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=smuk64zcvpy.fsf@linuxpal.mit.edu \
--to=gdt@work.lexort.com \
--cc=andreas+ding@gate450.dyndns.org \
--cc=ding@gnus.org \
/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).