On Sun, Oct 12, 2003 at 10:01:29AM -0700, Reskill wrote: > Hi, > > I believe this email to be extremely accurate and well written. It echos > many of the calls we have been making over the last few days regarding > a production network, and I would particularly like to draw attention > to: > >2) Users migrate to a new, separate production network. Current > >Freenet > >becomes test network. > >- - pro: rapid performance improvement for user base. Clean start > >for > >production network. Minimal effort for developers. > >- - con: users need to actively migrate. Test network is cluttered > >with > >versions. Psychological effort of "giving up" current Freenet and > >"giving in" to dissident users. > > I believe that without a clear definition between testing and stable > networks, recent occurrences regarding network degradation are bound > to happen again, sooner rather than later. Much better, then, to push > to a stable "clean slate" with the next well-tested stable build, and > always maintain this migration step with each significant new stable > release.
Oh yeah, 'cos we're gonna change the routing algorithm every 3 months now. > > It is definitely time that new procedures were put into place to safeguard > network performance and the freenet userbase, especially if any truly > worthwhile content is to surface in our network. See my reply to the other mail. > > --Reskill > Run your own fork of freenet if you like, but you will not be able to enforce everyone running recent stable builds, and if you succeed in getting 90% of users onto it, development will suffer. -- Matthew J Toseland - [EMAIL PROTECTED] Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so.
signature.asc
Description: Digital signature
_______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
