> All I'm expecting from users is the ability to open up a web browser and > type in a URL into netscape/ie. This should be our goal.
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. > > We can't take this attitude or else encryption == illegality in the eyes > > of the persecutors. By encrypting everything we avoid making the paranoid > > persecuted. > Sorry, I'm a bit lost in the encryption deal. Isn't it transparent > between nodes? I was speaking of encryption of data before it enters the network. > We really need a single place to keep all protocol proposals and a list of > ones that are going to be implemented. 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. > Hopefully by 1.0 the lines between client and full fledged node will go > away. Idea: Theoretically we could use the browser's cache to serve as > the datastore. That would be quite interesting. That would be very good. It's good to blur lines. What would be *really* interesting would be if we used the browser's cache as a publically (anonymously) accessible store. Then whatever you downloaded from web pages would be accessible via Freenet, automatically. This is, of course, a bad idea in many ways and I'm just being silly, but it would be really cool anyway. > 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) > 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. _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
