> On this I agree. But I think the implementation of the netscape integrated > client should spawn a node. The node should stick around for some sort of > reasonable/configurable amount of time. Like until netscape closes, the > web page is closed, 5 minutes. I'm not sure. And it should be a pretty > standard node implementation. The client can be tweaked a lot, but the > spawned node should be an out-of-the-box vanilla node so the network sees > a bunch of nodes with small uptimes, not a bunch of netscape clients.
Interesting. It wouldn't be too hard to do assuming we already have a working server. But we'll still haveta write a pure client (linked into the browser) even if we're going to spawn a node. > I was speaking of encryption of data before it enters the network. Could you sum up the current plan to do this? > Very true. I have http://uts.cc.utexas.edu/~blanu/freenet/, which is a > list of all of _my_ proposed proposals. There is also a part of the web > page, somewhere, but it is not updated that often. Can we get it all hosted on sourceforge? Start a precedent ;) > > I see two divergent roads: > > 1. Majority of major browser makers embrace freenet and allow for the web > > browser to be a full fledged node, serving data off of cache. Of course > > this feature can be turned off, but is by default on (hopefully). If this > > happens, freenet will be big. > > Ah, what a grand dream. On that day we will wave the Freenet flag > over...um...over our workstations and drink margaritas (except for those > that don't like margaritas, of course, but _I_ will be drinking a > margarita) Hey, this thing could just be a year down the road. (Depending on how much help i get... *hint* *hint*) > > We'll probably have a full lynx node (official or unofficial). > > Netscape is a maybe. Mozilla, probably. IE is a wildcard. > > If this happens, the state of freenet in 3-5 years is unpredictable. > > The day a Microsoft product incorporates my code, is the day I buy a pet > fish. That's all I have to say about that. They'll probably just create their own extension of the freenet protocol and call it not-so-free-net. ;) -Larry _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
