there has been some discussion and some action[1] on building a seperate network using freenet - not rolling back the codebase itself, but merely using a build that has historically been "good enough" for use. to clarify, the goal isn't to fork fred, but merely to get something usable while development progresses. we all want unstable and stable to have high throughput, search with low latency, provide high anonymity, and solve world hunger, but right now (and for the past weeks/months) there has been a degradation in performance, to the point where many cannot insert or fetch freesites reliably. there seems to be some value in having a parallel production vs development network - people using production would still have whatever bugs there are in the build production uses, but it would be consistent and reliable. In addition, developers using the development network would be able to know that all nodes on the network are actively being upgraded, so that network related bugs can be tracked down and improvements made more easily. Does that make sense? If so, the question to the nebulus "you" is what build should a production network use? This build should be reliable, consistent, and most of all, functional. Currently, some people on IIP are trying out a seperate network using build 692 (yikes) - modified with a different protocol version so things stay seperate. This build was chosen largely arbitrarily, harkening back to a time when freenet inserts and fetches worked pretty much across the board, but there were still overload issues. What build should be used for a production network? Or should people really just shut up and deal with the way things are in the normal freenet network? We want freenet to improve, but we don't all have the time to do dev on it and simply just want to use it. We know it works to some degree, but we know it used to work better. What does devl@ think is the best way to go? -jrandom [1] http://mids.student.utwente.nl:8891/Y0fg5IG4LLk/
!+!+!+!+!+!+!+!+!+!+!+!+!+!+!+!+!+!+!+!+!+!+!+!+!+!+!+ CryptoMail provides free end-to-end message encryption. http://www.cryptomail.org/ Ensure your right to privacy. Traditional email messages are not secure. They are sent as clear-text and thus are readable by anyone with the motivation to acquire a copy. !+!+!+!+!+!+!+!+!+!+!+!+!+!+!+!+!+!+!+!+!+!+!+!+!+!+!+ _______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
