-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > > Maybe this has been hashed out before, but why does any of this > meta-data actually need to be stored with the data? If clients simply > use a convention like "appending '.sig' to the plaintex key gets a file > containing the plaintext signature," and "appending '.type' gets the > MIME type," this whole problem of meta-data goes away. The clients > are the ones that care about it, and the clients are the ones that get > to manipulate it. Encrypting the meta-data becomes a non-issue, as > the nodes have no way to associate the signature or mime type with the > actual data -- it's just data hidden under SHA1-hashed keys. Because these keys would likely be stored on different servers than the data, and might be requested less often, causing the data to either not be found due to a low HTL even when the document itself could be, or those co-documents might disappear from disuse or continue to exist even after the document dissapears. These things *should* be linked so that they behave consistently.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.1 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE4/ys9pXyM95IyRhURAqalAKDVyAiTBouL3ln5bZF4/bEWcbI0MwCgiNv9 uuAOA87Mn5hA6ozgOr5DgG0= =74HB -----END PGP SIGNATURE----- _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
