Re: Asynchronous hashcash.el

[Simon Josefsson <jas@extundo.com>]

asjo@koldfront.dk (Adam Sjøgren) writes:

> On Mon, 15 Nov 2004 00:35:16 +0100, Simon wrote:
>
>> asjo@koldfront.dk (Adam Sjøgren) writes:
>
>>> (setq hashcash-in-news t)
>
>> Ah, thanks, now enabled. However, the cookie generated for this
>> message doesn't really make sense, does it?
>
>> I guess what I meant was that hashcash cookies aren't generated
>> properly for mailing lists gateway:ed into news. The resource to
>> mint for should be the mailing list address, not the news group
>> name, I think. Or am I missing something?
>
> I won't pretend to be trying to understand how these things fit
> together the best... Perhaps gmane (c|w)ould use the hashcash-token
> with the newsgroup-name as a clue as to whether a posting, being
> posted via gmane, is spam or not.

Ah, that's a possibility.  But typically hashcash on mailing lists are
minted to the mailing list address, so that 1) the mailing list
software itself can look at the hash coin, and 2) members of the
mailing list can also verify that the coin is minted for the mailing
list address.

So while gmane could use a hash coin for the news group name, gmane
could equally well use a hash coin for the mailing list address, which
would then also be usable in 1) and 2) above.

The to-list solution do work, but it makes posts go via mail instead
of via news.  Original-To might be unreliable.

Hm. What if gmane added a header with the e-mail address of all
mailing lists corresponding to the Newsgroups: header?  E.g.:

Newsgroups: gmane.emacs.gnus.general, gmane.emacs.devel
X-List-To: ding@gnus.org, emacs-devel@gnu.org

Then Gnus could mint a coin for those two lists, and everything will
work.

Perhaps there are simpler solutions... ideas welcome.