Re: Hashcash on by default?

[gdt@work.lexort.com]

Simon Josefsson <jas@extundo.com> writes:

> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>
>> I just switched on async hashcash generation:
>>
>> (setq message-generate-hashcash t)
>>
>> I think it's kinda neat how those payment lines appear in the buffer
>> asynchronously.  :-)  But perhaps we should just switch this on by
>> default?  I mean, if you don't have hashcash installed, it won't do
>> anything, and if you do have hashcash installed, you probably want to
>> use it.  And since the impact now is so low (what with it being
>> asynchronous and all), I think it makes sense.
>
> I like that.  I've changed the default.

I just updated and tested this.  When following up to an article in
nnimap, I got two hashcash lines inserted (correctly) after a few
seconds.

When sending mail by typing 'm' in *Group*, and then entering a name,
I found that hashcash was generated non-async when I hit ^C^C.  Is
this the intended behavior?

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.

-- 
	Greg Troxel <gdt@work.lexort.com>