Category: Windows / Internet

License: Freeware

Limitations :

OS: Windows All/Unix

Size: 15.47 MB (16,219,083 bytes)

Introduction: Freenet is a large-scale peer-to-peer network application which pools the power of member PCs around the world to create a massive virtual information store, much like a global hard drive. The network is built first and foremost with anonymity in mind. Communications by the nodes are encrypted and are "routed-through" other nodes to make it more difficult to determine who is requesting the information and what its content is. Users contribute to the network by giving bandwidth and a portion of their hard drive for storing files. Unlike other peer-to-peer file sharing networks, this does not let the user control what is stored in the data store. Instead, files are kept or deleted depending on how popular they are, with the least popular being discarded to make way for newer or more popular content. Files in the data store are encrypted to reduce the likelihood of prosecution by persons wishing to censor Freenet content. If you have a firewall or a NAT box click here for some info. Freenet contains NO spyware or adware , it's Free Software! When you first start Freenet your node will know very little about the network, meaning that it could take several minutes or longer to retrieve a web page. Please be patient since Freenet will learn how to find information more effectively over time and its speed will gradually improve with use. What's New in This Release: · Removed the (primary) failure table. This may have been causing many fast DNFs recently on files that may well actually be available, but which through getting requests and failing have gotten into the failure tables on many nodes. There is a risk that removing the failure table may increase network load; if this happens, we have various options for dealing with it. Until recently there were very few files blocked by the failure table, but there have been recent reports of large numbers of blocks, possibly caused by increased node specialization. · Minor client-layer bugfixes - NullPointerExceptions in SegmentOutputStream turned into error messages. I haven't fixed the underlying cause of the error messages yet, but things should work better with the errors than with the NPEs (which were also errors!).