Re: Asynchronous hashcash.el

[Dan Christensen <jdc@uwo.ca>]

Thanks a lot for implementing this.  It makes hashcash much more
usable.  I have a few comments/questions:

1) If I call mail-add-payment-async while a previous async payment is
   being calculated, I end up with redundant hashcash headers and
   wasted cpu time.  Could this function keep a list of calculations
   in progress, and not start redundant calculations (same # of bits
   and same key)?

2) Could a key binding ("C-c C-h"?) and menu item be created for
   mail-add-payment-async?

3) I'd like async payments to be calculated even for recipients I add
   to the To/Cc lists, without manually having to call
   mail-add-payment-async.  Any suggestions on how best to do this?

4) I think the documentation could say a bit more about how this
   works.  E.g. the section:

     If you wish to generate hashcash for each message you send, you can
     customize `message-generate-hashcash' (*note Mail Headers:
     (message)Mail Headers.), as in:
  
       (setq message-generate-hashcash t)
  
     You will need to set up some additional variables as well:

   could instead read:

     If you wish to generate hashcash ..., as in:     [no change here]
  
       (setq message-generate-hashcash t)

     This will cause Gnus to start asynchronously calculating hashcash
     payments for addresses that it put in the To and Cc lines while
     you compose your message.  If you add other addresses manually, a
     payment will be generated for them when you send the message.  If
     you wish to have payments generated asynchronously for these
     messages, you can manually invoke mail-add-payment-async
     (keystroke/menu...)   [New paragraph.]
  
     You may wish to set up some additional variables as well:
     [Note change to this phrasing.]
    
Thanks again!

Dan