Re: The issue of mime parsing

Stefan Karrmann <[email protected]>:

> The data of an ISP-IM2000 for a message should be similar to
>
> list of
>    addressee                     (mandatory)
>    ISP of addressee              (mandatory)
>    public key of addressee       (optional)  -\
>    public key of addressee's ISP (optional)  --+-- one of both is recommended
>    list of                       (optional)
>       cash descriptor               (mandatory, e.g. hashcash, etc.)
>       cash value                    (optional, maybe by challenge response)
        ^^^^
i have also a big problem with this:  i do not believe that
communication should be anything but the cheapest resource available
to the human race.  spam, flodding and harassment are part of
electronic, cheap communication that have to be dealt with, but with
currently available techniques, this is more server load than
annoyance, at least for me.  i run rblsmtpd (in a modified version
that tags connections from open relays and -proxies) and a bayesian
classifier, and i report _every_ spam that get through (five a day
maximum!).

but think of future developments in democracy, where e-government
will be a fact of daily life.  there will be only small parliaments,
and "representative democracy" will be abolished, because _every_
citizen will vote directly on topics that interest him.  do you want
to give this technology only to those who can afford it?  no!

also, just because a disgruntled wizard like dan bernstein thinks he
can charge people for the honor of contacting him, i will never pay a
dime for his time, and i will not participate in a project im2000
that implements it.

> sender                        (mandatory on the sender's ISP to report success)
> char notice [NOTICELEN]       (global fixed length, e.g. NOTICELEN=256)
> body_size                     (mandatory, unlimited)
> body                          (mandatory)
> deadline                   (mandatory, tai-label, cf. <http://cr.yp.to/proto/utctai.html>)

  clemens