[hashcash] Re: new format tweak coming...

Adam Back wrote:

> I tend to think human readability is an important consideration so
> putting a \ in front of such chars still retains readability.  eg:
> 
> eg \: \, \; \: and \\
> 
> 
> Perhaps another more readable alternative would be to use "s, eg:
> 
> name1="val1","val2";name2="val3"
> 
> Actually I like that better I think.  Then the only escape code
> necessary is \".

which means the only thing you really need to quote is the quote 
character itself.  I was thinking that it might be possible to instead 
use something like two types of quotes so that you could have quoted 
strings within using the "other" form but then you could have both 
quotes within a quoted strings if you were truly unlucky.  so I think 
it's best to go simple as well as readable which means the "\"type of 
string\"" method of producing a quoted string within a quoted string is 
probably a good technique.


> 
> 
> Another thing one could do is make the existing resource just another
> extension field, eg to="foo@xxxxxxx".
> 
> This would allow people who were interested to extend in this
> direction to include from="bar@xxxxxxx", and multiple recipients
> to="foo@xxxxxxx","abc@xxxxxxx", subject="hello world".
> 
> Of course we still need some minimal interoperable behavior, also and
> that is one argument for keeping a separate resource string.
> 

assuming I'm not misunderstanding you, I would argue against the 
multiple recipients in one stamp technique because it makes things 
easier for spammers.  They could just list the whole bunch of names, 
generate one 23 bit stamp and mail is delivered very inexpensively which 
is not what we want.

--- eric

Other related posts: