So, I have been thinking about a reasonably secure way to provide a convenient list of seednodes to new Freenet nodes. Yes, obviously it would be better if people got a seednode from someone obsure (their friend, next-door neighbor etc) but I just don't think this is realistic for the vast majority of potential Freenet users.
My suggestion therefore is to have a central machine harvest seednodes from nodes in the network which dump references they have found to be reliable (ie. with a CP above a certain threshold) into a DBR SSK which they insert into Freenet, perhaps daily. These harvested references are placed in a database where they are periodically tested. A node can request references from this database via HTTP and will be given a random selection from the database. A node requesting twice from the same IP address will get the same random selection each time. So, what are the required components of this? Well, firstly there is the node-side stuff to extract the references, this could be a combination of a new FCP command, and some client stuff to take this and insert it into Freenet. Secondly there is the harvester-side stuff, this could be a PHP script with a database back-end, along with a cron job to periodically test the references using another new FCP command where you can ask a node to test a reference. So, any volunteers for either component of this? The node stuff would require some reasonably simple FCP hacking along with an understanding of the DataStore class, it would be a good way to get more involved in Freenet internals. The other would be relatively simple PHP-database stuff. Comments? Ian. -- Ian Clarke ian at freenetproject.org Founder & Coordinator, The Freenet Project http://freenetproject.org/ Chief Technology Officer, Uprizer Inc. http://www.uprizer.com/ -------------- 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/20011111/e2b51768/attachment.pgp>
