> 1. Presumably we're wanting old versions of the documents to expire. If > document 1 keeps getting requested, then the network will think it's > popular, and it'll never expire. > > 2. Freenet doesn't guarantee that you'll be able to find a document, so > surely this means that the algorithm you describe might fail sometimes, > especially if you have some old documents expiring and others not. > > I quite like the timestamp option, because it's guaranteed to work. All > nodes could be programmed to clear out anything that has expired. The > biggest downfall I can see is that it requires foresight. And, it's not > much use if you want to keep your traffic to a minimum to reduce the > chance that someone will discover that you are the anonymous poster. When we say timestamp, we mean timestamp that has *no* control by the nodes.
This updating scheme is only a temporary one until real updating is implemented. We don't want to code in any crutches. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20000815/3aca9640/attachment.pgp>
