(plz feel free to flame and correct me if i said something wrong or stupid :)
ifaik fred relies on having as much potential nodes to connect to as possible, so it can always be on-air and finds the best route to data the user looks for. it does this by collecting any node reference it stumbles across (e.g. "sniffing passing freenet messages and extracting noderefs"), so the local seednodes.ref will increase both in size and #of noderefs. this is the reason fred needs to run some time and the user has to grab some data, so that other nodes catch up the user's local fred node reference and enroll that node to their potential routing nodes. so every node has it's own unique noderef-collection, with some standard noderefs of the meaner machines (or by initial seednodes.ref) but also with exotic noderefs the majority of other freds does not have (e.g. nodes that just connected to the freenet or are low-traffic) >This is not the latest build, but it should work if you can get >some working node references. Mine are at ><http://wooledge.org/~greg/seednodes.ref> -- stop your node, download >that, replace your current seednodes.ref file with mine, and restart >the node. Give it a moment to catch its breath, then try the four >keys on the gateway page again. this is the topic about this mail: seenodes.ref-bashing *grin* "kill your noderefs by overwriting with my file" - destorying some of these rare noderefs. the nodes belonging to these refs are cut-off more and more if their noderefs become deleted on more machines (or by ds-bugs or reinitializind seednodes.ref by overwriting with the standard file) of course, nodes wich become removes from node A still have the chance to resubmit their noderef or contact other nodes, so these will store the noderef again. what i am thinking of is a simple-to-use "import another seednodes.ref to your node". this can be done in different ways: a) you can d/l a different seednodes.ref file from someone to a folder (without overwriting yours) and click on a button at the fproxy site, wich will happyly pop up a new site and asks for the filename of the seednodes.ref to insert b) have unique names for your seednodes.ref - file, e.g. ("seednodes.dfg34534dfgNodeReferenceHeeeFGsdf�$%.ref"). so other users can d/l your file and put it into their freenet-directory (or a special "./seednodes"-directory). now fred will import these files, either by b1) checking every 30 seconds for a new seed-files and importing the new nodes within by itself (userfriends but may need one thread more, does not need a modified fproxy) b2) hitting a button in fproxy "check for new seednode.refs", which wil initiate a search in the seednodes-directory for new and unknown noderefs this way, no noderefs will be deleted by accidenr and can be distibuted really nice between computers without killing noderefs, so it is possible to gather immense amounts of noderefs (the seednodes.ref file stores the fred-version to check if this is a usable ref, right?) illegal refs or nodes wich are just too old to contact to (do not use lastgoodbuild=, better make a new backwardscompatibleto= field) can be dropped so thes e do not swamp the file with useless refs also, the standard seednodes.ref-file can easily be replaced with a seednodes.ref, that has imported some seednodes.ref already (from hawk or another "trusted" source) every fresh node will then have nearly all available and relieable refs right away, without the long initial propagation delay thanks for your time ;) --> so what are your thoughts? ____________________________________________________________ The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. _______________________________________________ support mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support
