On Fri, Oct 31, 2003 at 03:06:04PM +0000, Toad wrote: > > Everyone already uses relative links because many users have nodes on > different ports. But I don't see how this solves the SSKs problem. > DBRs, NIM forms and so on require that we just have > SSK@<opaque fixed string>/<human readable string> > > Having said that, that is not strictly true... on NIM forms, you could > precompute the hashcash. DBRs would initially have to be computed by the > node at request time, which would really slow down requesting TFE... > *but* TUKs would solve that problem. Edition sites could easily > precompute the hashcash for the next edition. So I don't see a real > problem here. And we wouldn't even need to break the network storage or > routing... but we probably want to hold off for TUKs first...
Formatting would be a bit of an issue. I suggest, for an SSK with hashcash already calculated: SSK@<pubkey hash>,<entropy>,<hashcash>/<filename> Where we provide a tool to calculate the hashcash, and document it somewhere (an authoring tips document or something). And incorrect hashcash is ignored and recalculated by the node. -- Matthew J Toseland - [EMAIL PROTECTED] Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so.
signature.asc
Description: Digital signature
_______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
