>Hmm, this presents a problem for those of us with public nodes, but publicNode set to false. I set it to false because I use it too, and it's a pain. I don't mind people changing some settings >in there, but changing the modes so that other people don't have full access is kinda bad for me. I want to run it as full access, but if i do, now, someone can make it so that other people can't have full access.
*sigh*, well latest cvs is right now as I described in my last mail (except for the actaul persisting of the value which I have asked toad to handle since I don't know how to do it). Unless I get a bunch of solid and doable suggestions I'll leave it be as outlined in that mail.. I am getting a little bit tired of all these conflicting mindsets now... Wants sessions but no cookies, wants no sessions, wants per user setting, wants not per user setting, wants it in publicNode but still doesn't want it there and so on, wants two modes, wants 'explain more..', wants don't explain mode.. Maybe we should leave it as it was in the beginning? I personally is pro per-session stuff with a default value since that would solve everything just nicely in my opinion, but then again, I am not afraid of cookies. What about making a boolean config value which either uses this mode or else disables the whole of it? /N _______________________________________________ devl mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl
