Sebastian, As you all know, I'm busily writing a Java client for Freenet. Installation on Windows is something I am taking very seriously. There is no reason, apart from download time of the JRE, why the Java client can't fill the role you mention until such time as there's a full native code implementation for Windows (EZFreenet + Whiterose).
I am not using Windows, but I can write a good client (in Java). I have Windows NT and Windows 98 and the will to make it work well on both. It might be worth considering using one of those Java -> Native Code compiler thingies for the Windows binary install. I think they're all proprietary, but there shouldn't be any licensing issues, in theory. I'm not philosophically opposed to such a thing. Steve On Mon, 14 Aug 2000, Sebastian [iso-8859-1] Sp?th wrote: > Which in turn leads to the really last topic: Windoze > I know you guys are not using it and (partially correct) don't like it. > Nevertheless Freenet is never going to be as popular a Napster or > Gnutella if it doesn't offer some nice looking, easily to handle GUI > clients or web proxies. > Since Freenet 0.2 I "never" got a Freenet node on Windows to run > smoothlessly. Is *anybody* succesfully running a recent node on Windows? > Please contact me, I'd like to share the experience and I am no Newbie. > You'll need a running windows node to get Windows clients, so it *is* > important. > Although there are some nice tries to a GUI client EZ-Freenet, FNC, they > are not yet something I'd recommend an average Windows user. As you UNIX > guys aren't able to program some nice Win GUI client (no offence > intended), you should at least provide a central, well-organized > description of Freenet nodes, and it's protocol specification (maybe > including a sample conversation between node/node, node/client). Steve _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
