From: gdt@work.lexort.com
Cc: ding@gnus.org
Subject: Re: Hashcash on by default?
Date: Tue, 18 Apr 2006 09:59:44 -0400 [thread overview]
Message-ID: <smu8xq30ysv.fsf@linuxpal.mit.edu> (raw)
In-Reply-To: <8764l72e6f.fsf@latte.josefsson.org> (Simon Josefsson's message of "Tue, 18 Apr 2006 15:42:16 +0200")
Simon Josefsson <jas@extundo.com> writes:
> gdt@work.lexort.com writes:
>
>> Simon Josefsson <jas@extundo.com> writes:
>>
>> It would be neat to begin generating hashcash once the user has
>> stopped editing the To:/CC: fields for a few seconds, and regenerate
>> any missing entries after the next edit/pause cycle, and then do a
>> final insert/generate on sending. This would always be correct, and
>> minimize delays - but sounds like a lot of work, especially for
>> something that could be done in the background as part of sending.
>
> Yup. I don't think it can be done in background though, ^C^C must be
> able to report errors to the user, and if the sending process is
> asynchronous, this will be more difficult.
>
> However, having it notice changes in the To/Cc fields would be good
> enough, I think. Do you want to work on it?
I probably won't have spare time, and there's the assignment issue to
be worked through. But I'll send a patch for todo describing the idea.
--
Greg Troxel <gdt@work.lexort.com>
next prev parent reply other threads:[~2006-04-18 13:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-15 13:22 Lars Magne Ingebrigtsen
2006-04-15 23:42 ` Miles Bader
2006-04-16 0:38 ` Adam Sjøgren
2006-04-17 3:54 ` Manoj Srivastava
2006-04-18 10:47 ` Simon Josefsson
2006-04-18 12:24 ` gdt
2006-04-18 13:42 ` Simon Josefsson
2006-04-18 13:59 ` gdt [this message]
2006-04-18 19:37 ` Raymond Scholz
2006-04-18 20:20 ` Lars Magne Ingebrigtsen
2006-04-18 20:30 ` Ted Zlatanov
2006-04-18 21:00 ` Reiner Steib
2006-04-18 22:28 ` Steve Youngs
2006-04-19 13:03 ` Reiner Steib
2006-04-18 22:32 ` Simon Josefsson
2006-04-21 23:50 ` Lars Magne Ingebrigtsen
2006-04-25 15:50 Reiner Steib
2006-04-30 10:26 ` Lars Magne Ingebrigtsen
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=smu8xq30ysv.fsf@linuxpal.mit.edu \
--to=gdt@work.lexort.com \
--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).