Ok, I'm going to keep reiterating the concerns of myself, jrand0m, and many others until something is done about them. (Some of these might just be mine, however. I speak for myself right now.)
Freenet will not work in a hostile environment currently, because it's busy being prettified for our comfy homes with fast computers and cable modems. This is bad. I'd like to see you hike over to Tunisia or something, hook it up to a computer and modem there, and make Freenet work. Doesn't work? Didn't think so. (Ok, so Tunisia's a bit too developed, but try rural parts of Cuba, etc.)
User modes == more options == more likely to break != KISS
Don't place all these images in the default builds for the error pages. It shouldn't be up to a browser to cache them. Certainly, someone should not have to risk their ass trying to get a more minimal page if they are in a hostile environment.
Don't log stuff like keys. Even if the person didn't request it, you shouldn't be logging the names of keys.
Adopt the same deprecation method as Python. One build, the feature is normal, the next is might be deprecated, and in the next build, it's gone. Don't keep deprecated features forever, like it seems you do.
Make sure you try as hard as you can to break Freenet. Don't simply use it normally. For instance, I do my browsing and publishing, but I'm also working on what I believe to be a possible remote exploit or varying seriousness in Fred.
I'm not saying toad isn't working hard, but I think his effort is rather misguided at times. He has done a lot, I admit that, but now we need to focus on making it work where it would do the most good.
