> I suppose we should put this in the FAQ if it's not already there. Running > your own node is NOT about giving your resources to the network. Will it > is, but even if you don't care at all about the network, it's for YOUR > security and even if you're running on a 2400 baud modem it's better to > run your own node. If you are routing other people's traffic, you might > not be responsible for what's on your computer. If you are running a node, > telling the difference between your traffic and other people's is hard. If > you are running a client, it is easy.
I'm not suggesting that users shouldn't run their own nodes. Just that most users wont have their own nodes simply because of the relative difficulty in setting one up. In fact I'm advocating setting up your own node when you can. (I'll add this to the readme when i get around to it) The current url scheme encourages people to run their own nodes. (You simply get to type less =) ) Sure, security is an issue. But for most users, having a trusted server is enough. Most of the time the users wont need the extra security. How often are you getting illegal information? How often is it not illegal enough for law enforcement to care? The freenet protocol already provides a good deal of protection and anonymity. Only the most paranoid will *need* to run their own nodes because of security. One of the first things freenet should host is the Linux kernel. It's a great way to let people make use freenet and make their first freenet experience a legal one ;) It'll also help us test the server under heavy loads with large files. Back to detecting a client: The library will hopefully be accepting connections by 1.0 and will eventually be a full node. I'll work towards making the node indistinguishable from a java node. Thoughts? Comments? -Larry _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
