From yesterday's FF: -- Recent changes to Freenet configuration mean that everybody needs to update their configuration file or lose fproxy access. I haven't updated my main node recently so I'm not exactly sure of the changes required, but anybody worried about upgrading is advised to check out the Freenet development mailing list archives for further information. Also, the Windows installer apparently no longer works, so a reinstall won't fix any update woes either. --
We need to address this problem ASAP, probably by modifying the Java to deal with this (if only temporarily). In future, we should be careful of modifications which could stop people's nodes from working on an upgrade without modifications to freenet.conf. Perhaps we need a more generic way to handle this type of situation. Suggestions are welcome. Ian. -- Ian Clarke [EMAIL PROTECTED] Founder & Coordinator, The Freenet Project http://freenetproject.org/ Chief Technology Officer, Uprizer Inc. http://www.uprizer.com/ Personal Homepage http://locut.us/
msg04034/pgp00000.pgp
Description: PGP signature
