I'm glad to see that the subject of complexity has come up, and if I can speak to in a more general way...
Complexity is insidious - you start with a simple idea, the creativity flows and over time, you are wedded to a highly coupled, inflexible and obscure beast that is hard to distance yourself from and see for what it is - due for a rewrite and an infusion of new and current tools and techniques. With current tools and understanding way ahead of where they were a decade ago, perhaps it is time to distill the knowledge gained so far and pour it into a more modular build based on test driven development, where the potentially highly valuable learning that Freenet can offer could also potentially be reused by other projects, if the want exists, for example to release Freenet from the server/pc realm and out to be used in the current decade of mobile and tablet devices. With a robust framework for modeling real-world activity that can be directed at portions of the Freenet app, such as load management, used to drive demonstrable unit, functional and performance testing, the volatility of the app can be reduced, as would be the need the incessant, off-schedule mode of releasing updates. I am sure that a more measured and planned mode of building out the app, as is seen in the well regarded projects from the Apache foundation for example, would reduce the pain and stress for developer and user alike, and extend the life and impact of the project. With the utmost regard for everyone who contributes to the project, Sebastian Weetabix.
