Tavin Cole <tcole at espnow.com> wrote: > Allright people. Who is really and truly going to be working on the 0.4 > fproxy? Theo? David? the other David? > > I am going to finish off that nasty AutoClient (kept hoping someone else > would ;-) .. and I mean to cause fproxy to fall into place shortly > thereafter. > > I'd appreciate it if anyone who wants to work on fproxy would collaborate > with me on the design. There are certain things that must be done right, > such as juggling AutoClient, InternalClient, and the plug-in API correctly. > > Also, what kinds of new features do we want? I'm thinking a nice insert > wizard, maybe some simple diagnostics and node control modules..
I do want to do stuff on it, though perhaps not at the rate that you want, I don't know. I'm certainly happy to collaborate with others, of course. New features - I think the biggest thing it needs right now is some sort of progress indication to tell you just what the heck is going on back there. It's not really acceptable to have to look at the logs to figure this out. Second, I'd like to do hyperlink rewriting before we build up too much content hardwired to "http://localhost:8081/";. It's just poor practice. We ought to author hyperlinks as "freenet:xxx" and rewrite them to whatever port you have fproxy on, or https if you do that. Third, SSL with null encryption, if that's possible. theo -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 174 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20010625/02415e55/attachment.pgp>
