Re: [FreeNet-chat] Yet another damn 'permanence' proposal
McMeikan, Andrew ([EMAIL PROTECTED]) wrote: with technocash/digicash/digigold there is no problems the value can be encrypted and sent with the spenders id unrevealed, Yes, but how do you prevent a replay attack? Either by the person who was supposed to receive the payment (what stops them from deducting a larger amount than they're supposed to by simply using your signed payment multiple times); or by an eavesdropper who intercepts the signed payment? (I'm not saying it can't be done; just playing devil's advocate. If you implement a system that involves real money, you'd better be *damned* sure you've got all these details taken care of!) for easier currencies like e-gold/paypal you need a third party that changes these to a more anonymous payment (any one who likes that idea pleas feel free to join up at http://www.egroups.com/group/goldenagents ) ; several already exist This is a slightly more serious issue. Do you trust this third party not to reveal your identity? How stable is this third party, financially -- will they go bankrupt next year? -- Greg Wooledge | Truth belongs to everybody. [EMAIL PROTECTED] |- The Red Hot Chili Peppers http://wooledge.org/~greg/ | PGP signature
Re: [freenet-chat] Yet another damn 'permanence' proposal
This idea might seem nutty to some, but I think it is a good idea, especialy since one might want to keep files on freenet simply so that they can access it later on another machine. But I think it might just be easier to setup a program that automaticaly reinserts certian files that a particular user would like to keep available on freenet for his/her own selfish reasons. And if more than one person is doing this with the same file, good, that just means the file will be more readily available. So, for instance, a porn freak might want to keep varios favorite porn files available on the net, so, he/she reinserts the files under his/her own private subspace and keeps that entire subspace actively updated often enough for the files to stay readily available whereever he/she goes. But the CHK would be identical to any other copy of the file on freenet and therefore no extra data is being added, no matter how many people are trying to keep a particular file on freenet. It doesn't matter how many SSKs are posting a particular file, as long as the file NAME remains the same, that way you can do a search and easily find what you are looking for. A more socialy acceptable use would be a system backup which is encrypted and inserted with a CHK. Then you just have a program that reinserts that file regularly useing the CHK. As long as you know the CHK of the file you can go to any computer, download the file to that computer, and set up an updater there too. This way an old backup that would only be used by ONE user on the entire freenet could be kept on freenet permanently for as long as there are active updaters running. Perhaps nice people might be persuaded to setup updaters for other people's files, for no other reason than to be charitable. :) Who knows. I hope the file spliting thing gets implemented soon on freenet. Then a huge file can stick around longer. :) On Sat, 19 May 2001 07:23:57 +1200 David McNab [EMAIL PROTECTED] writes: OK - I *do* know that the whole Freenet architecture is dependent on ephemeral storage, and the ability of nodes to purge older less popular files. But an idea came to me for how *some* files could be kept available permanently. The idea would require that some people anonymously volunteer to work as 'Freenet archivists'. All this would require is: 1) For archivists - using an 'archive' program which copies retrieved keys into a 'permanent cache' directory on their hard disk, and also maintains a database of such keys. This is simple - archivist is browsing, and thinks 'i feel this should be permanently available'; (s)he then runs: freenet_archive key_uri [-scomment] 2) For clients - anyone who requests a key and fails, can run an 'archive request' client which simply writes an archive request to a keyindex: freenet_archive_request key_uri 3) For archivists - run an 'archive server' program which regularly harvests the 'archive request' keyindex and re-inserts any requested files which are found on the archivist's permanent store, also logging such re-insertions to another 'archive response' key index. 4) For clients - 'archive request' client can check the 'archive response' key index (say over the last 2 days) and see if their request has attracted a response: freenet_archive_status This won't guarantee permanence of all material, but it does give individuals the power to guarantee that materials of their choice will always be available within a (say) 48 hour window. Summary - software required: 1) client - send archive request to key index, log this in local database 2) server - add files to archive, browse archive, prune archive 3) server - daemon - read archive requests, reinsert keys found in archive, log successful reinsertions to an 'archive response' key index. 4) client - daemon which periodically peruses 'archive response' and seek items previously logged to local database. If no-one has any objection to this, I'd like to make it my next project once FreeWeb goes beta. If someone beats me to it, I'll support totally. Suggestions - very welcome and appreciated. Cheers David ___ Chat mailing list [EMAIL PROTECTED] http://lists.freenetproject.org/mailman/listinfo/chat GET INTERNET ACCESS FROM JUNO! Juno offers FREE or PREMIUM Internet access for less! Join Juno today! For your FREE software, visit: http://dl.www.juno.com/get/tagj. ___ Chat mailing list [EMAIL PROTECTED] http://lists.freenetproject.org/mailman/listinfo/chat
Re: [freenet-chat] Yet another damn 'permanence' proposal
On Sat, May 19, 2001 at 01:34:22PM -0700, [EMAIL PROTECTED] wrote: why not add a property to every key that says: pls do not remove me from your cache unless you 1st try to republish me to freenet? Because then a file would never get deleted, and the network would simply fill up. Ian. PGP signature
[freenet-chat] Yet another damn 'permanence' proposal
OK - I *do* know that the whole Freenet architecture is dependent on ephemeral storage, and the ability of nodes to purge older less popular files. But an idea came to me for how *some* files could be kept available permanently. The idea would require that some people anonymously volunteer to work as 'Freenet archivists'. All this would require is: 1) For archivists - using an 'archive' program which copies retrieved keys into a 'permanent cache' directory on their hard disk, and also maintains a database of such keys. This is simple - archivist is browsing, and thinks 'i feel this should be permanently available'; (s)he then runs: freenet_archive key_uri [-scomment] 2) For clients - anyone who requests a key and fails, can run an 'archive request' client which simply writes an archive request to a keyindex: freenet_archive_request key_uri 3) For archivists - run an 'archive server' program which regularly harvests the 'archive request' keyindex and re-inserts any requested files which are found on the archivist's permanent store, also logging such re-insertions to another 'archive response' key index. 4) For clients - 'archive request' client can check the 'archive response' key index (say over the last 2 days) and see if their request has attracted a response: freenet_archive_status This won't guarantee permanence of all material, but it does give individuals the power to guarantee that materials of their choice will always be available within a (say) 48 hour window. Summary - software required: 1) client - send archive request to key index, log this in local database 2) server - add files to archive, browse archive, prune archive 3) server - daemon - read archive requests, reinsert keys found in archive, log successful reinsertions to an 'archive response' key index. 4) client - daemon which periodically peruses 'archive response' and seek items previously logged to local database. If no-one has any objection to this, I'd like to make it my next project once FreeWeb goes beta. If someone beats me to it, I'll support totally. Suggestions - very welcome and appreciated. Cheers David ___ Chat mailing list [EMAIL PROTECTED] http://lists.freenetproject.org/mailman/listinfo/chat
Re: [freenet-chat] Yet another damn 'permanence' proposal
DM == David McNab [EMAIL PROTECTED] writes: DM OK - I *do* know that the whole Freenet architecture is DM dependent on ephemeral storage, and the ability of nodes to DM purge older less popular files. DM But an idea came to me for how *some* files could be kept DM available permanently. Zzz. ~Mr. Bad -- ~ Mr. Bad [EMAIL PROTECTED] | Pigdog Journal | http://pigdog.org/ freenet:MSK@SSK@u1AntQcZ81Y4c2tJKd1M87cZvPoQAge/pigdog+journal// Statements like this give the impression that this article was written by a madman in a drug induced rage -- Ben Franklin ~ ___ Chat mailing list [EMAIL PROTECTED] http://lists.freenetproject.org/mailman/listinfo/chat
Re: [freenet-chat] Yet another damn 'permanence' proposal
If I understand this correctly, this is actually a combination of in- freenet key indexes and in-freenet request-lists, right ? (which is actually a good idea) I don't really see what the connection with permanence is. Clearly, the only way to make something permanent is to get it and keep it. Also, if you would implement this and make it automatic (in some feeble attempt to incorporate permanence, conveniently forgetting that the permanent servers would have also have to forget stuff, unless they were REALLY BIG :-)), it would probably mess up the anonymity because of the adaptive routing. uXs -- What our ancestors would really be thinking, if they were alive today, is: Why is it so dark in here? -- (Terry Pratchett, Pyramids) ___ Chat mailing list [EMAIL PROTECTED] http://lists.freenetproject.org/mailman/listinfo/chat
