Comment: I die, and my computer shuts down, destroying a Freenet hub. A user at a government agency thinks he's clicking the button to search for new Freenet hubs, but instead he is pressing The Button. Nuclear war begins, and all die. Oh, the embarrassment.
These pages are intended to give a top-down overview of Fred's architecture. Before reading this you should become familiar with Freenet's architecture by reading this paper. If you require more detailed information than is provided here you should refer to the Javadocs that are part of Fred's source code.
At the simplest level, Fred is a piece of software which people can run on their computer which will allow them to both request from, and insert information into, a global information store, while allowing their computer to form a part of that store. To request or insert a piece of information a key is required, such keys are somewhat analogous to a URL for a piece of information on the world wide web. Freenet does not guarantee that it will find a piece of information, even if it exists on the network, but it is reliable enough to be very useful for a diverse number of applications.
To contribute to the freenet project, you don't have to hack java on fred. There's an easy to use interface to the java node called the FreenetClientProtocol that allows an external program to do inserts and requests.
These can reside either in the configuration file or be given as command line arguments.
Name:
ipAddress (--ipAddress)
Arguments:
xxx.xxx.xxx.xxx
Default val:
Description:
The IP address of this node as seen by the public internet. This is
needed in order for the node to determine its own node reference.
If you have a dynamic IP address, you may enter a host name in this
field (assuming you have a dynamic DNS service). If this is a
transient node, you can leave this blank.
Name:
listenPort (--listenPort)
Arguments:
<port no.>
Default val:
62680
Description:
The port to listen for incoming FNP (Freenet Node Protocol) connections on.
Name:
clientPort (--clientPort)
Arguments:
<port no.>
Default val:
8481
Description:
The port to listen for local FCP (Freenet Client Protocol) connections on.
Name:
fcpHosts (--fcpHosts)
Arguments:
<host list>
Default val:
Description:
A comma-separated list of hosts that may connect to the FCP port
(clientPort). If left blank, only the localhost will be allowed.
May be given as IP addresses or host names.
Name:
adminPassword (--adminPassword)
Arguments:
<string>
Default val:
Description:
If this is set then users that can provide the password can
can have administrative access. It is recommended that
you do not use this without also using adminPeer below
in which case both are required.
If this is set, then users that are authenticated owners
of the given PK identity can have administrative access.
If adminPassword is also set both are required.
Name:
transient (--transient)
Arguments:
yes|no
Default val:
false
Description:
Transient nodes do not give out references to themselves, and should
therefore not receive any requests. Set this to yes if you cannot
receive incoming connections, or cannot keep the computer continuously
online.
Name:
doAnnounce (--doAnnounce)
Arguments:
yes|no
Default val:
true
Description:
If this is true, the node will automatically announce to all nodes in
the file, as specified by , etc.
Name:
seedFile (--seedFile)
Arguments:
<file>
Default val:
seednodes.ref
Description:
A file containing one or more node references which will be incorporated
into the node's routing table on startup. A reference is only added if
there is no previously existing reference to that node. When this node
announces, it will announce to the nodes listed in this file.
Name:
doDiagnostics (--doDiagnostics)
Arguments:
yes|no
Default val:
true
Description:
The diagnostics module receives and aggregates statistics about
Freenet's performance. This will eat some gratuitous memory and
CPU time but may let you provide valuable data to the project.
Name:
diagnosticsPath (--diagnosticsPath)
Arguments:
<dir>
Default val:
stats
Description:
The directory in which to save diagnostics data. Defaults to
/stats if left blank.
Name:
nodeFile (--nodeFile)
Arguments:
<file>
Default val:
Description:
The path to the file containing the node's private key, DSA group,
cipher key, etc. Defaults to node_ in the current directory.
Name:
storeFile (--storeFile)
Arguments:
<file>[,..]
Default val:
Description:
The path to a single file, or a comma-separated list of files,
containing the data store. The size of each file is given by
.
Name:
storeSize (--storeSize)
Arguments:
<bytes>
Default val:
209715200
Description:
The byte size of each data store file. If there is more than one
file, the total size of the store is the product of the number of
files and .
Name:
storeCipherName (--storeCipherName)
Arguments:
<string>
Default val:
Twofish
Description:
The name of a symmetric cipher algorithm to encrypt the datastore
contents with. Supported algorithms are "Twofish", "Rijndael",
and "null", "none", or "void" (for no encryption).
Name:
storeCipherWidth (--storeCipherWidth)
Arguments:
<integer>
Default val:
128
Description:
The width in bits of the cipher key to use for the datastore.
The allowed values for this will depend on the cipher algorithm.
Twofish allows 64, 128, 192, or 256, while Rijndael allows
128, 192, or 256.
Name:
bandwidthLimit (--bandwidthLimit)
Arguments:
<bytes/sec>
Default val:
100000
Description:
The maximum number of bytes per second to transmit, totaled between
incoming and outgoing connections. Ignored if either inputBandwidthLimit
or outputBandwidthLimit is nonzero.
Name:
inputBandwidthLimit (--inputBandwidthLimit)
Arguments:
<bytes/sec>
Default val:
0
Description:
If nonzero, specifies an independent limit for incoming data only.
(overrides bandwidthLimit if nonzero)
Name:
outputBandwidthLimit (--outputBandwidthLimit)
Arguments:
<bytes/sec>
Default val:
0
Description:
If nonzero, specifies an independent limit for outgoing data only.
(overrides bandwidthLimit if nonzero)
Name:
maxNodeConnections (--maxNodeConnections)
Arguments:
<int>
Default val:
60
Description:
The maximum number of incoming and outgoing connections to allow
at the same time.
Name:
logLevel (--logLevel)
Arguments:
<word>
Default val:
normal
Description:
The error reporting threshold, one of:
Error: Errors only
Normal: Report significant events
Minor: Report minor events
Debug: Report events only of relevance when debugging
Name:
logFile (--logFile)
Arguments:
<filename>|NO
Default val:
freenet.log
Description:
The name of the log file (`NO' to log to standard out)
Name:
logFormat (--logFormat)
Arguments:
<tmpl.>
Default val:
d (c, t): m
Description:
A template string for log messages. All non-alphabet characters are
reproduced verbatim. Alphabet characters are substituted as follows:
d = date (timestamp), c = class name of the source object,
h = hashcode of the object, t = thread name, p = priority,
m = the actual log message
The number of references allowed per node in the routing table.
This should not be set too high.
Name:
rtMaxNodes (--rtMaxNodes)
Arguments:
<integer>
Default val:
100
Description:
The number of unique nodes that can be contained in the routing table.
Name:
messageStoreSize (--messageStoreSize)
Arguments:
<integer>
Default val:
500
Description:
The number of outstanding message replies the node will
wait for before it starts to abandon them.
Name:
routeConnectTimeout (--routeConnectTimeout)
Arguments:
<millis>
Default val:
10000
Description:
The time to wait for connections to be established and
authenticated before passing by a node while routing out.
Connections that are by passed are still finished and cached
for the time set by (in milliseconds).
Name:
maxHopsToLive (--maxHopsToLive)
Arguments:
<integer>
Default val:
15
Description:
When forwarding a request, the node will reduce the HTL to this value
if it is found to be in excess.
Name:
announcementPeers (--announcementPeers)
Arguments:
<integer>
Default val:
15
Description:
An announcement must visit announcementPeers nodes to be successful.
If there is more than one seed node, announcements will be sent to
them all, and the HTL of each announcement will be given by:
HTL = announcementPeers / (no. of seed nodes)
Name:
announcementAttempts (--announcementAttempts)
Arguments:
<integer>
Default val:
10
Description:
The number of attempts to make at announcing this node per
initial peer. Zero means the node will not announce itself
Name:
announcementDelay (--announcementDelay)
Arguments:
<integer>
Default val:
1800000
Description:
The amount of time to wait before initially announcing the node,
and to base the time the time between retries on. In milliseconds.
Name:
announcementDelayBase (--announcementDelayBase)
Arguments:
<integer>
Default val:
2
Description:
The value to mutliply the last delay time with for each retry.
That is, for try N, we weight *^N
before starting.
Name:
initialRequests (--initialRequests)
Arguments:
<integer>
Default val:
10
Description:
The number of keys to request from the returned close values
after an Announcement (this is per announcement made).
Name:
initialRequestHTL (--initialRequestHTL)
Arguments:
<integer>
Default val:
15
Description:
The hops that initial requests should make.
Name:
fproxy.class (--fproxy.class)
Arguments:
<class name>
Default val:
freenet.client.http.FproxyServlet
Description:
The Java class for the fproxy HttpServlet?. You shouldn't need to change this.
Name:
fproxy.port (--fproxy.port)
Arguments:
<port number>
Default val:
8888
Description:
The port that fproxy listens for HTTP requests on.
Set true to allow polling for dropped requests during SplitFile? download.
Name:
services (--services)
Arguments:
service_0,service_1,...
Default val:
fproxy,nodestatus
Description:
A comma delimited list of services that are run when the node starts. Enter 'fproxy' here to start fproxy automatically.
Name:
nodestatus.class (--nodestatus.class)
Arguments:
<class name>
Default val:
freenet.client.http.NodeStatusServlet
Description:
The Java class for the NodeStatusServlet?. You shouldn't need to change this.
Name:
nodestatus.port (--nodestatus.port)
Arguments:
<port number>
Default val:
8889
Description:
The port that the node status servlet listens for HTTP requests on.
Name:
authTimeout (--authTimeout)
Arguments:
<millis>
Default val:
30000
Description:
How long to wait for authentication before giving up (in milliseconds)
Name:
connectionTimeout (--connectionTimeout)
Arguments:
<millis>
Default val:
15000
Description:
How long to listen on an inactive connection before closing
(if reply address is known)
Name:
hopTimeExpected (--hopTimeExpected)
Arguments:
<millis>
Default val:
12000
Description:
The expected time it takes a Freenet node to pass a message.
Used to calculate timeout values for requests.
Name:
hopTimeDeviation (--hopTimeDeviation)
Arguments:
<millis>
Default val:
12000
Description:
The expected standard deviation in hopTimeExpected.
Name:
maximumThreads (--maximumThreads)
Arguments:
<integer>
Default val:
120
Description:
Should we use thread management? If this number is defined and non-zero,
this specifies the max number of threads in the pool. If this is overrun
connections will be rejected and events won't execute on time.
Name:
blockSize (--blockSize)
Arguments:
<bytes>
Default val:
4096
Description:
What size should the blocks have when moving data?
Name:
streamBufferSize (--streamBufferSize)
Arguments:
<bytes>
Default val:
65536
Description:
The default size of stream buffers.
Name:
maximumPadding (--maximumPadding)
Arguments:
<bytes>
Default val:
65536
Description:
The maximum number of bytes of padding to allow between messages
and in Void messages.
Name:
logInboundContacts (--logInboundContacts)
Arguments:
true/false
Default val:
false
Description:
Set true to enable inbound contact monitoring.
Name:
logOutboundContacts (--logOutboundContacts)
Arguments:
true/false
Default val:
false
Description:
Set true to enable outbound contact monitoring.
Name:
logInboundRequests (--logInboundRequests)
Arguments:
true/false
Default val:
false
Description:
Set true to enable per host inbound request monitoring.
We have set-up a non-profit corporation to advance the interests of the Freenet project. The mission statement of Freenet Project
Inc is as follows:
The specific purpose of this corporation is to assist in developing and disseminating technological solutions to further the open and democratic distribution of information over the Internet or its successor electronic communication networks or organizations. It is also the purpose of this organization to guarantee consenting individuals the free, unmediated and unimpeded reception and impartation of all intellectual, scientific, literary, social, artistic, creative, human rights, and cultural expressions, opinions and ideas without interference or limitation by or service to state, private, or special interests. It is also the purpose of this organization to educate the world community and be an advocate of these purposes.
We are now able to accept donations via PayPal. Monies received will only be utilized to advance our Mission Statement, and are administered at the direction of the Freenet Project Board. Monies received may be used to hire a full time programmer, purchase a dedicated server, cover incidental administrative/legal costs, and, if it becomes necessary, to fund legal defense.
We have set up a PayPal account through which you can conveniently make donations to the non-prof.
Please click on this button to donate:
Mailing Donations
Alternatively you can make donations by mail. Checks should be made
payable to "Freenet Project Inc". The address for
donations is:
Freenet Project Inc.
2554 Lincoln Blvd #712
Venice, CA 90291
Please download and test a snapshot of the current development version. The next version 0.5 is expected to be completed soon - check back at this site for updates or join the announcements list to be notified when it is ready.
Freenet requires that Java is installed on your computer. While we are working to ensure that Freenet can work with free JVMs such as Kaffe, currently we suggest that users download Sun's 1.4 JVM from here for reliability, speed, and stability reasons.
Download the latest Linux snapshot from here, it will be in the form freenet-YYYYMMDD.tgz where YYYYMMDD is the date the snapshot was created. Uncompress the snapshot as follows:
> tar xfz freenet-YYYYMMDD.tgz
This will create a directory called "freenet-YYYYMMDD", change into this directory, and follow the instructions in the file "README".
Download the latest Unix snapshot from here, it will be in the form freenet-YYYYMMDD.tgz where YYYYMMDD is the date the snapshot was created. If you're using Internet Explorer, or most other web browsers, Stuffit Exander will be launched immediately, and will uncompress to the Desktop folder (unless you've set it to download somewhere else). Open a terminal (under Applications:Utilities:Terminal) and type:
cd Desktop/freenet-YYYYMMDD
Hit return, and then type:
./start-freenet.sh
And Hit return again. This will begin the configuation process. For most questions you can just hit return, but make sure when it asks what your IP is that it's correct. If you have any questions, please contact Tom Longson at tlongson@socal.rr.com.
Sign up for the Support mailing list here and send an email asking for help to support@freenetproject.org. Remember that by contacting us, not only do you help yourself, but you can also help us to make Freenet better and more user friendly.
Internet Relay Chat (IRC)
If you have an Internet Relay Chat client (we suggest XChat which is available for Windows and Linux), you can often find some helpful Freenet developers on the #freenet channel on irc.openprojects.net, or if you are using a browser which supports IRC URLs, click here.
An emergent behavior is a behavior exhibited by a system consisting of a large number of simple and similar (or identical) components, which is surprisingly complex given the simplicity of the individual components of the system.
Emergent behavior is frequently observed in biology, for example, the human brain consists of a large number of relatively simple cells called neurons, yet the brain exhibits very complex behavior. Another example might be a flock of birds, where even though each individual bird follows quite simple rules, the flock as a whole can exhibit complex and sophisticated behavior.
Emergent behavior has the advantage that systems which rely on it often lack centralized control, and tend to be quite robust, but it is rather difficult to design such a system. Freenet is perhaps one of the first artificially created systems which takes advantage of emergent behavior.
An excellent and non-technical book on this and other related subjects is "Out of Control" by Kevin Kelly (Amazon.com, BarnesAndNobel.com).
Comment: I'm pretty newbish freenet-wise, but I am interested in helping document how to use freenet with FreeBSD? and keeping current newbie questions in the FAQ.
Important notice: These answers are provided by a variety of people involved in the Freenet project, however they should not be taken as the official position of the project. If you require a position statement on a particular issue you should contact
Ian Clarke.
Freenet is free software designed to ensure true freedom of communication over the Internet. It allows anybody to publish and read information with complete anonymity. Nobody controls Freenet, not even its creators, meaning that the system is not vulnerable to manipulation or shutdown. Freenet is also very efficient in how it deals with information, adaptively replicating content in response to demand. For more information please read What is Freenet?.
Freenet grew out of a design for an anonymous publication system created by Ian Clarke while a student at the University of Edinburgh, Scotland. Since then many other people have contributed towards making Ian's proposal a reality.
Because we can't find a way to do this without compromizing Freenet's other goals. For example, people often suggest that someone's node could just never drop data they want to cache permenantly. This, however, won't work because even if the data is still available on their node, there is no way to ensure that requests for that data will be routed to that node.
We have considered many other ways that Freenet could store data permenantly, but they either won't work, or compromize Freenet's core goals of anonymity, and scalability.
If by legal you mean not illegal, then yes it is. Of course, anything can be found to be illegal at some point in the future, and the law can be an ass sometimes, so we can make no guarantee about Freenet's future legality other than it should be legal in any fair and just society.
This is related to the previous question. We have done everything we can to make it extremely difficult for any sane legal system to justify punishing someone for running a Freenet node, and there is little precedent for such action in today's developed countries. Many legal systems recognise the importance of freedom of speech, which is Freenet's core goal. Having said that, there is risk in doing anything that your government might not agree with, you should make an informed decision as to whether to take that risk.
The Freenet Project has notified the US authorities (since the files are hosted on SourceForge, which is on US soil) that it will be exporting crypto. As long as your country doesn't prohibit the use of encryption you are fine.
While most people wish that child pornography and terrorism did not exist, humanity should not be deprived of their freedom to communicate just because of how a very small number of people might use that freedom.
The true test of someone who claims to believe in Freedom of Speech is whether they tolerate speech which they disagree with, or even find disgusting. If this is not acceptable to you, you should not run a Freenet node.
There is another thing you can do. Since content in Freenet is available as long as its popular, you can help limit the popularity of whatever information you do not like. For example, if you do not want a file to spread you should not request it and tell everyone you know not to request that specific key.
The current 0.4 version will soon evolve into a 0.5 version that will improve perfomance significantly, so stay in touch. In the meantime you may try donating more disk space and bandwith and making your node permanent. It is very important to always keep your node up to date, so download the latest snapshot often.
You aren't really donating in the sense that you lose the disk space and the bandwith; but you aren`t really sharing either (at least not the same way as with filesharing programs). It is more like pitching in to the common Freenet resource pool.
If you are happy with what you are getting then no. But if you want more you should consider donating more, making your node permanent and you should ask your friends to do the same.
Your experience will definitely get better, but for a really great improvement we need more people to start thinking like you. Bandwith counts more than diskspace.
God only knows. For a possible business model for rewarding artists see FairShare ; for a business solution with characteristics similar to Freenet see this place.
Yes, in fact even without the anonymity feature Freenet is very useful because of its unique way it handles content distribution and information load. In simple terms that means you can publish a website without worrying about how big the site will be and without having to put someone elses ad banners on it. Over time that site may very well become more accessible and faster to load than a site on the ordinary web. For more info see Publishing.
The most useful component of the FCPTools is ezFCPlib, a portable ANSI-C based Freenet Client Library. It's been written to make writing Freenet clients as easy as possible.
In addition, the FCPTools include command line utilities to insert and retrieve files (fcpput, fcpputsplit, fcpget) as well as entire freesites (fcpputsite) via ezFCPlib.
Contents of FCPTools:
ezFCPlib - the engine that drives the tools. Draft API doc included under ./ezFCPlib/doc.
fcpget - a key request utility.
fcpput - a key insert utility.
fcpputsite - a freesite insertion utility.
fcpputsplit - a splitfile insertion utility.
Download the latest source snapshot from here. Uncompress the snapshot as follows:
>tar xfz fcptools-latest.tgz
This will create a directory called "fcptools-YYYYMMDD", where YYYYMMDD is the date the snapshot was created. Change into this directory, and follow the instructions in the INSTALL and README files.
Download the latest MS-Windows pre-compiled binaries from here. Since not everyone has MS Visual C++ installed on their machine, Windows users have the added luxury of downloading pre-compiled versions of fcpget, fcpput, fcpputsite, fcpputsplit and ezFCPlib.
With advances in communication technology, such as the Internet, and
systems like Freenet, comes
the realization that copyright law is increasingly unenforceable
without seriously curtailing people's freedom to communicate. It
has also raised questions about the validity of copyright law
itself, and the ideas upon which it is founded, particularly the
idea that information is property.
This raises the obvious question of how to enable people to earn a
living from the creation of useful information in the absence of
copyright law. One obvious solution is to allow those who value a
creative work to voluntarily contribute to its creator. The
Internet makes such a solution much more likely to be effective,
given the ease with which an artist can receive contributions
through companies such as PayPal and
Amazon. Many people, however,
do not believe that such a mechanism will be effective since it
relies on people having a wider sense of self interest (if they
don't contribute to the artist, then it is less likely that the
artist will continue to create). While my personal belief is that
this simple voluntary payment approach can work, there are also ways
that it can be enhanced to answer this criticism.
Everybody can be the record label
Consider a simplistic view of how a record label operates. They
find early-stage bands who are yet to have a wide audience, but who
they consider to have the potential to be very successful. They
invest money in that band, and if that band does indeed become a
success they make a return on their investment. FairShare essentially democratizes this process. Anybody can
"invest" in an artist, and if that artist goes on to be a success,
then the person is reward in proportion to their investment and how
early they made it.
But where does this return on investment come from? The answer is
that it comes from subsequent investors. For example, lets say that
you invest $10. $4.50 might go straight to the band, $1 might go to
the operator of the system, and the remaining $4.50 would be
distributed among previous investors in the band, those who invested
more early would get a bigger proportion than those who invested
less, later-on.
Of course, most people will not make a profit, but they are rewarded
by knowing that they contributed towards an artist that they liked,
and helped reward others who believed in that artist, and who may
have brought the artist to their attention.
Collaborative Filtering
One of the positive aspects of what record labels claim to do is to
filter out the "noise", and present the public with the best of what
is available. Of course, this aspect can be mirrored in our
scheme. A FairShare operator could provide a randomized list of
artists, biased towards those who have recieved more contributions,
but with the occasional new act to give them some exposure.
I don't think so although I am not a lawyer. The problem with
Pyramid Schemes is that they give the impression that you are
guaranteed a return, which is simply a lie. In the case of
FairShare, we are completely honest about the fact that most people
will not make a profit, but those people benefit by rewarding
artists they like.
Might there be other reasons why this is illegal?
Of course, any new idea could be illegal (just ask Napster!),
it is impossible to tell until it is challenged in court. Having
said that, I can't think of any reason why this should be
illegal provided that those who contribute to artists are not
mislead as to the nature of the system.
How will the maths work?
Good question. There are actually many choices as to how funds can
be distributed to investors in an artist. Some of these will allow
early-investors to make more of a profit, and some will distribute
funds more evenly. We will let the market decide as to which is
best.
Won't FairShare operators just become another monopoly?
Hopefully not. We would discourage artists from using a FairShare
operator who insisted on an exclusive relationship for this reason.
Provided that there is sufficient competition, it will keep margins
down, and the free market should lead to the evolution of optimal
approaches.
Who thought of this?
This mechanism was developed by
Steven Starr, Rob Kramer,
and myself as a response to the impossibility of enforcing copyright
law without restricting people's ability to communicate. The name
"FairShare" is due to Steven Starr. I am not aware of any similar
approaches currently in existence.
What has this got to do with Freenet?
Not much, except that the amount of feedback we received in the
press concerning Freenet's effect on copyright got us thinking about
this problem.
What has this got to do with Uprizer?
Absolutely nothing.
I am keen to discuss this further, what do I do?
I have created a mailing list called
fairshare@freenetproject.org
for discussion of this document. You can subscribe to it
here. All comments should be directed to that mailing list.
Each topic can have files attached to it, similar to an email attachment. Use your browser to upload or download a file.
Attachments are stored under revision control, so uploads can never be lost, and files changes can be made with a rollback option that lets you retrieve all previous versions.
You can use Attachments to store and retrieve documents (in any format, with associated graphics, and other media files); attach documents to specific TWiki topics; collaborate on documents with full revision control; distribute documents on a need-to-know basis using; create a central reference library that's easy to access and manage by an entire user group.
For file sharing, FileAttachments on a series of topics can be used to quickly create a well-documented, categorized digital download center for all types of files: documents; graphics and other media; drivers and patches; applications; anything you can safely upload!
Through your Web browser, you can easily upload graphics (or sound files, or anything else you want to embed on a page) and place them anywhere in on a single page, or for use across a web, or site-wide.
NOTE: You can also add graphics - any files - directly, typically by FTP upload. This requires server access, and may be more convenient if a large number of files, or a particular directory location, is required. These files can't be managed using browser-based Attachment controls.
To upload: Click on the Attach link at the bottom of each page. A form is shown where you can browse for a file and upload it. The uploaded file will show up in the File Attachment table.
Files of any type can be uploaded. Some files that might impose a security risk are renamed, ex: *.php files are renamed to *.php.txt.
Currently there is no file size limit besides the disk space on the server.
The previous upload path is retained for convenience. In case you make some changes to the local file and want to upload it, again you can copy the previous upload path into the Local file field.
NOTE: There is no access control on individual attachments. If you need this type of control, create separate topics and define access restrictions? per topic.
An attachement can be moved between topics. To do this click Action on the attachment to be moved. On the control page, select the new web and topic, the click Move. The attachment and its version history are moved. The original location is stored as topic Meta Data?.
It is not possible to delete attached files with the current TWiki implementation. However, they can be moved to another topic. You may care to have a topic Trash.TrashAttachments - move attachments that are no longer wanted here.
Files attached to a topic are displayed in a directory table, displayed at the bottom of the page, or optionally, hidden and accessed when you click Attach.
Clicking on an Action link takes you to a new page that looks like this:
The first table is a list of all attachments, including their attributes. An h means the attachment is hidden, it isn't listed when viewing a topic.
The second table is all the versions of the attachment. Click on View to see that version. If it's the most recent version, you'll be taken to an URL that always displays the latest version, which is usually what you want.
To change the comment on an attachment, enter a new comment and then click Change properties. Note that the comment listed against the specific version will not change, however the comment displayed when viewing the topic does change.
To hide/unhide an attachment, enable the Hide file checkbox, then click Change properties.
Unlike topics, attachments are not locked during editing. As a workaround, you can change the comment to indicate an attachment file is being worked on - the comment on the specific version isn't lost, it's there when you list all versions of the attachment.
You will need a copy of CVS, this comes as standard with most Unix and Linux based operating systems.
At the moment there are two modules used for Freenet development, the most important one is freenet with the source of the core Freenet system and the node servlets (FProxy, Nodestatus).
The second module is called Contrib and it contains external contributions as well as the sources for the Windows installer. To check this out replace co freenet with co Contrib.
To check out the Freenet source code type:
cvs -d:pserver:anonymous@cvs.freenet.sourceforge.net:/cvsroot/freenet login
cvs -z3 -d:pserver:anonymous@cvs.freenet.sourceforge.net:/cvsroot/freenet co freenet
Sourceforge has some documents describing how to get CVS working with its CVS repositories.
Even more information is available here in the sections "6. CVS - General Information" and "7. CVS - OS Specific Information".
The FreenetClientProtocol (FCP) is designed to abstract the basics of Freenet so that client developers do not have to track the main Freenet protocol. FCP should be the bare bones of Freenet - metadata handling is not included in FCP though an extension to FCP may come about at a later date to avoid writing metadata handling libraries in many languages.
This protocol is never meant to go across a network - only via the loopback. Nodes should not accept FCP connections from hosts other than localhost by default.
By default FCP is port 8481, but any client that uses FCP should leave this configurable, because this may be changed in the node's configuration file or by some future FCP revision.
FCP follows the FNP setup for session and presentation.
In the following, numbers are always hex-encoded and fields in square-brackets are optional.
FCP allows one transaction per connection, after which the connection is torn down. At the beginning of each connection, the client must send these 4 bytes:
00 00 00 02
These are the 2-byte session identifier and the 2-byte presentation identifier. In the future, different identifiers may be used to allow alternate syntaxes or encrypted FCP connections from remote hosts, for example.
After sending the session and presentation identifiers, the client sends a message to initiate the transaction, then waits for one or more messages from the node until the transaction is complete. Messages are a series of lines terminated by LF or CRLF, in this form:
This is the complete set of client to node messages, with the possible node to client responses (only the headers are listed).
ClientHello
NodeHello
ClientGet
URIError
Restarted
DataNotFound
RouteNotFound
DataFound
DataChunk
ClientPut
URIError
Restarted
RouteNotFound
KeyCollision
Pending
Success
GenerateCHK
Success
GenerateSVKPair
Success
ClientDelete
Success
Additionally, the node may respond to any client message with a FormatError, meaning the command was not understood, and the node may responsd at any time with a Failed, indicating a fault in the node itself:
Failed and FormatError will not be discussed in the remainder of this document. Clients should be prepared to handle a Failed at any time, and a FormatError as teh response to any client message. Either of these messages terminates the transaction and the connection.
(Client -> Node)
ClientGet
URI=<string: fully specified URI, such as freenet:KSK@gpl.txt>
HopsToLive=<number: hops to live>
EndMessage
The client is now in the waiting state. The node may return one of the following messages:
URIError: Invalid Freenet URL. The transaction is terminated.
Restarted: The client should continue waiting.
DataNotFound: The transaction is terminated due to not being able to find data.
RouteNotFound: The transaction is terminated due to not being able to find a route.
Otherwise a DataFound message is returned:
(Node -> Client)
DataFound
DataLength=<number: number of bytes of metadata + data>
[MetadataLength=<number: default = 0, number of bytes of metadata>
EndMessage
After a DataFound message the data itself is sent in chunks:
(Node -> Client)
DataChunk
Length=<number: number of bytes in trailing field>
Data
<@Length bytes of data>
At any time when the full payload of data has not been sent a Restarted message may be sent. This means that the data to verify and the transfer will be restarted. The client should return to the waiting state, and if a DataFound is then received, the data transfer will start over from the beginning. Otherwise, when the final DataChunk is received, the transaction is complete and the connection dies.
(Client->Node)
ClientPut
HopsToLive=<number: hops to live>
URI=<string: fully specified URI, such as freenet:KSK@gpl.txt>
DataLength=<number: number of bytes of metadata + data>
[MetadataLength=<number: default = 0, number of bytes of metadata>]
Data
<@DataLength number of bytes>
If the client is inserting a CHK, the URI may be abbreviated as just CHK@. In this case, the node will calculate the CHK. The node must get all of the trailing field before it can start the insert into Freenet. The node may reply with one of the following messages:
URIError: Invalid Freenet URL. The transaction is terminated.
Restarted: The client should continue waiting.
RouteNotFound: The transaction is terminated due to not being able to find a route.
KeyCollision: The transaction is terminated due to a document with the same key already existing in Freenet. This message contains a URI field with the Freenet URI of the document.
SizeError: The transaction is terminated due to the data being too large for the key type; all non-CHK keys have a limit of 32 kB of data.
During an insertion, multiple Pending messages may be returned. These messages signal that the data is being successfully inserted, but insertion is not complete, and the node has not received a StoreData message yet:
(Node -> Client)
Pending
URI=<string: fully specified URI, such as freenet:KSK@gpl.txt>
[PublicKey=<string: public key>]
[PrivateKey=<string: private key>]
EndMessage
When the node receives a StoreData message (and thus insertion is complete), a Success message is returned with the Freenet URI of the new document and possibly a private/public keypair, if the inserted document was an SVK. See the section on key generation about this.
(Node -> Client)
Success
URI=<string: fully specified URI, such as freenet:KSK@gpl.txt>
[PublicKey=<string: public key>]
[PrivateKey=<string: private key>]
EndMessage
These messages allow a client to generate keys. This does not affect Freenet at all - the calculations are carried out at the node.
Key generation requests are done via a GenerateKey message. Either a CHK or an SVK keypair can be generated:
(Client -> Node)
GenerateCHK
DataLength=<number: number of bytes of data + metadata>
[MetadataLength=<nubmer: defaul = 0, number of bytes of metadata>]
Data
<@DataLength number of bytes>
The node calculates the CHK as it would do if inserting, but instead returns it. This completes the transaction:
(Node -> Client)
Success
URI=<string: fully specified URI, such as freenet:KSK@gpl.txt>
EndMessage
The format for generating SVKs is very similar but generates a pair of keys (public and private) which are independent of any data. This is generally used for setting up SSKs:
I (TravisBemann) originally transcribed this document from a converted to HTML version of an SGML document by Adam Langley which originally documented FCP, along with a few changes to document the introduction of the Pending message, and changing wording and formatting in some circumstances. Thus I will credit Adam Langley with the majority of the content in this. However, someome else (DeltaFourOhSeven) attempted to take credit for this by deleting my signature and date stamp and replacing it with his or her own (without making any other significant modifications or additions, and if he or she did he or she should have just put his or her signature and date stamp by his or her modifications). I personally regard this as a major breach of etiquette. To the best of my knowledge this person is not Adam Langley, so I am removing this person's signature and date stamp from its position and just leaving it below mine for the reader to read.
-- TravisBemann - 05 Jan 2002, 07 Jan 2002
This person attempted to take credit for putting this on freenetproject.org, dishonestly:
-- DeltaFourOhSeven - 06 Jan 2002
No, I made a few corrections and decided to sign it with my name to, among other things, update the revision date. I apologize for removing your name, I was not attempting to "steal credit"; but by the same token, I don't know that it's a good idea to keep a full changelog here either.
-- DeltaFourOhSeven - 13 Jan 2002
Ian Clarke
Uprizer, Inc.
1007 Montana Ave., #323
Santa Monica, CA 90403
USA ian@octayne.com
Oskar Sandberg
Department of Numerical Analysis and Computer Science
Royal Institute of Technology
SE-100 44 Stockholm
Sweden md98-osa@nada.kth.se
Brandon Wiley
College of Communication
University of Texas at Austin
Austin, TX 78712
USA blanu@uts.cc.utexas.edu
Theodore W. Hong
Department of Computing
Imperial College of Science, Technology and Medicine
180 Queen's Gate, London SW7 2BZ
United Kingdom t.hong@doc.ic.ac.uk
We describe Freenet, an adaptive peer-to-peer network application that
permits the publication, replication, and retrieval of data while
protecting the anonymity of both authors and readers. Freenet
operates as a network of identical nodes that collectively pool their
storage space to store data files and cooperate to route requests to
the most likely physical location of data. No broadcast search or
centralized location index is employed. Files are referred to in a
location-independent manner, and are dynamically replicated in
locations near requestors and deleted from locations where there is no
interest. It is infeasible to discover the true origin or destination
of a file passing through the network, and difficult for a node
operator to determine or be held responsible for the actual physical
contents of her own node.
Networked computer systems are rapidly growing in importance as the medium
of choice for the storage and exchange of information. However, current
systems afford little privacy to their users, and typically store any given
data item in only one or a few fixed places, creating a central point
of failure. Because of a continued desire among individuals to
protect the privacy of their authorship or readership of various types
of sensitive information[28], and the undesirability of central
points of failure which can be attacked by opponents wishing to remove
data from the system[11,27] or simply overloaded by
too much interest[1], systems offering greater security and
reliability are needed.
We are developing Freenet, a distributed information storage and
retrieval system designed to address these concerns of privacy and
availability. The system operates as a location-independent
distributed file system across many individual computers that allows
files to be inserted, stored, and requested anonymously. There are
five main design goals:
Anonymity for both producers and consumers of information
Deniability for storers of information
Resistance to attempts by third parties to deny access to information
Efficient dynamic storage and routing of information
Decentralization of all network functions
The system is designed to respond adaptively to usage patterns,
transparently moving, replicating, and deleting files as necessary to
provide efficient service without resorting to broadcast searches or
centralized location indexes. It is not intended to guarantee
permanent file storage, although it is hoped that a sufficient number of
nodes will join with enough storage capacity that most files will be able to
remain indefinitely. In addition, the system operates at the
application layer and assumes the existence of a secure transport
layer, although it is transport-independent. It does not seek to
provide anonymity for general network usage, only for Freenet file
transactions.
Freenet is currently being developed as a free software project on
Sourceforge, and a preliminary implementation can be downloaded from
http://www.freenetproject.org/. It grew out of work originally
done by the first author at the University of Edinburgh[12].
Several strands of related work in this area can be distinguished.
Anonymous point-to-point channels based on Chaum's mix-net
scheme[8] have been implemented for email by the Mixmaster
remailer[13] and for general TCP/IP traffic by onion
routing[19] and Freedom[32]. Such channels are not in
themselves easily suited to one-to-many publication, however, and are best
viewed as a complement to Freenet since they do not provide file access and
storage.
Anonymity for consumers of information in the web context is provided by
browser proxy services such as the Anonymizer[6], although
they provide no protection for producers of information and do not protect
consumers against logs kept by the services themselves. Private
information retrieval schemes[10] provide much stronger guarantees
for information consumers, but only to the extent of hiding which piece of
information was retrieved from a particular server. In many cases, the
fact of contacting a particular server in itself can reveal much about the
information retrieved, which can only be counteracted by having every server
hold all information (naturally this scales poorly). The closest work to
our own is Reiter and Rubin's Crowds system[25], which uses a
similar method of proxying requests for consumers, although Crowds does not
itself store information and does not protect information producers.
Berthold et al. propose Web MIXes[7], a stronger system
that uses message padding and reordering and dummy messages to increase
security, but again does not protect information producers.
The Rewebber[26] provides a measure of anonymity for producers
of web information by means of an encrypted URL service that is
essentially the inverse of an anonymizing browser proxy, but has the same
difficulty of providing no protection against the operator of the service
itself. TAZ[18] extends this idea by using chains of nested
encrypted URLs that successively point to different rewebber servers to be
contacted, although this is vulnerable to traffic analysis using replay.
Both rely on a single server as the ultimate source of information.
Publius[30] enhances availability by distributing files as
redundant shares among n webservers, only k of which are needed
to reconstruct a file; however, since the identity of the servers
themselves is not anonymized, an attacker might remove information by
forcing the closure of n-k+1 servers. The Eternity
proposal[5] seeks to archive information permanently and
anonymously, although it lacks specifics on how to efficiently locate
stored files, making it more akin to an anonymous backup service. Free
Haven[14] is an interesting anonymous publication system that
uses a trust network and file trading mechanism to provide greater server
accountability while maintaining anonymity.
distributed.net[15] demonstrated the concept of pooling
computer resources among multiple users on a large scale for CPU cycles;
other systems which do the same for disk space are Napster[24]
and Gnutella[17], although the former relies on a central server
to locate files and the latter employs an inefficient broadcast search.
Neither one replicates files. Intermemory[9] and
India[16] are cooperative distributed fileserver systems intended
for long-term archival storage along the lines of Eternity, in which files
are split into redundant shares and distributed among many participants.
Akamai[2] provides a service that replicates files at locations
near information consumers, but is not suitable for producers who are
individuals (as opposed to corporations). None of these systems attempt to
provide anonymity.
Freenet is implemented as an adaptive peer-to-peer network of nodes
that query one another to store and retrieve data files, which are
named by location-independent keys. Each node maintains its own local
datastore which it makes available to the network for reading and
writing, as well as a dynamic routing table containing addresses of
other nodes and the keys that they are thought to hold. It is
intended that most users of the system will run nodes, both to provide
security guarantees against inadvertently using a hostile foreign node
and to increase the storage capacity available to the network as a
whole.
The system can be regarded as a cooperative distributed filesystem
incorporating location independence and transparent lazy replication.
Just as systems such as distributed.net[15] enable
ordinary users to
share unused CPU cycles on their machines, Freenet enables users to
share unused disk space. However, where distributed.net uses those
CPU cycles for its own purposes, Freenet is directly useful to users
themselves, acting as an extension to their own hard drives.
The basic model is that requests for keys are passed along from node
to node through a chain of proxy requests in which each node makes a
local decision about where to send the request next, in the style of
IP (Internet Protocol) routing. Depending on the key requested,
routes will vary. The routing algorithms for storing and retrieving
data described in the following sections are designed to adaptively
adjust routes over time to provide efficient performance while using only
local, rather than global, knowledge. This is necessary since nodes
only have knowledge of their immediate upstream and downstream
neighbors in the proxy chain, to maintain privacy.
Each request is given a hops-to-live limit, analogous to IP's
time-to-live, which is decremented at each node to prevent infinite
chains. Each request is also assigned a pseudo-unique random
identifier, so that nodes can prevent loops by rejecting requests they
have seen before. When this happens, the immediately-preceding node
simply chooses a different node to forward to. This process continues
until the request is either satisfied or exceeds its hops-to-live
limit. Then the success or failure result is passed back up the
chain to the sending node.
No node is privileged over any other node, so no hierarchy or central
point of failure exists. Joining the network is simply a matter of
first discovering the address of one or more existing nodes through
out-of-band means, then starting to send messages.
Keys and searching
Files in Freenet are identified by binary file keys obtained by
applying a hash function. Currently we use the 160-bit SHA-1[4]
function as our hash. Three different types of file keys are used,
which vary in purpose and in the specifics of how they are constructed.
The simplest type of file key is the keyword-signed key (KSK),
which is derived from a short descriptive text string chosen by the user
when storing a file in the network. For example, a user inserting a
treatise on warfare might assign it the description,
text/philosophy/sun-tzu/art-of-war.
This string is used as input to deterministically generate a public/private
key pair. The public half is then hashed to yield the file key.
The private half of the asymmetric key pair is used to sign the file,
providing a minimal integrity check that a retrieved file matches its
file key. Note however that an attacker can use a dictionary attack
against this signature by compiling a list of descriptive strings.
The file is also encrypted using the descriptive string itself as a
key, for reasons to be explained in section 3.4.
To allow others to retrieve the file, the user need only publish
the descriptive string. This makes keyword-signed keys
easy to remember and communicate to others. However, they form a
flat global namespace, which is problematic. Nothing prevents two
users from independently choosing the same descriptive string for
different files, for example, or from engaging in
``key-squatting''--inserting junk files under popular descriptions.
These problems are addressed by the signed-subspace key (SSK),
which enables personal namespaces. A user creates a namespace by
randomly generating a public/private key pair which will serve to
identify her namespace. To insert a file, she chooses a short
descriptive text string as before. The public namespace key and
the descriptive string are hashed independently, XOR'ed together,
and then hashed again to yield the file key.
As with the keyword-signed key, the private half of the asymmetric
key pair is used to sign the file. This signature, generated from
a random key pair, is more secure than the signatures used for
keyword-signed keys. The file is also encrypted by the descriptive
string as before.
To allow others to retrieve the file, the user publishes the
descriptive string together with her subspace's public key. Storing
data requires the private key, however, so only the owner of a
subspace can add files to it.
The owner now has the ability to manage her own namespace. For
example, she could simulate a hierarchical structure by creating
directory-like files containing hypertext pointers to other
files. A directory under the key text/philosophy could contain a list of keys such as text/philosophy/sun-tzu/art-of-war, text/philosophy/confucius/analects,
and text/philosophy/nozick/anarchy-state-utopia,
using appropriate syntax interpretable by a client. Directories
can also recursively point to other directories.
The third type of key is the content-hash key (CHK), which
is useful for implementing updating and splitting. A content-hash
key is simply derived by directly hashing the contents of the
corresponding file. This gives every file a pseudo-unique file key.
Files are also encrypted by a randomly-generated encryption key.
To allow others to retrieve the file, the user publishes the
content-hash key itself together with the decryption key. Note that
the decryption key is never stored with the file but is only published
with the file key, for reasons to be explained in section 3.4.
Content-hash keys are most useful in conjunction with signed-subspace
keys using an indirection mechanism. To store an updatable file, a
user first inserts it under its content-hash key. She then inserts
an indirect file under a signed-subspace key whose contents are the
content-hash key. This enables others to retrieve the file in
two steps, given the signed-subspace key.
To update a file, the owner first inserts a new version under its
content-hash key, which should be different from the old version's
content hash. She then inserts a new indirect file under the
original signed-subspace key pointing to the updated version. When the
insert reaches a node which possesses the old version, a key collision
will occur. The node will check the signature on the new version, verify
that it is both valid and more recent, and replace the old version.
Thus the signed-subspace key will lead to the most recent version
of the file, while old versions can continue to be accessed
directly by content-hash key if desired. (If not requested, however,
these old versions will eventually be removed from the network--see
section 3.4.) This mechanism can be used to
manage directories as well as regular files.
Content-hash keys can also be used for splitting files into multiple
parts. For large files, splitting can be desirable because of storage
and bandwidth limitations. Splitting even medium-sized files into
standard-sized parts (e.g. 2n kilobytes) also has
advantages in combating traffic analysis. This is easily accomplished
by inserting each part separately under a content-hash key, and
creating an indirect file (or multiple levels of indirect files) to
point to the individual parts.
All of this still leaves the problem of finding keys in the first place.
The most straightforward way to add a search capability to Freenet
is to run a hypertext spider such as those used to search the web.
While an attractive solution in many ways, this conflicts with the
design goal of avoiding centralization. A possible alternative is to
create a special class of lightweight
indirect files. When a real file is inserted, the author could also
insert a number of indirect files each containing a pointer to the
real file, named according to search keywords chosen by her. These
indirect files would differ from normal files in that multiple files
with the same key (i.e. search keyword) would be permitted to exist,
and requests for such keys would keep going until a specified number
of results were accumulated instead of stopping at the first file found.
Managing the likely large volume of such indirect files is an open problem.
An alternative mechanism is to encourage individuals to create
their own compilations of favorite keys and publicize the keys of these compilations.
This is an approach also in common use on the world-wide web.
Retrieving data
To retrieve a file, a user must first obtain or calculate its
binary file key. She then sends a request message to her own
node specifying that key and a hops-to-live value. When a node
receives a request, it first checks its own store for the data and
returns it if found, together with a note saying it was the source of
the data. If not found, it looks up the nearest key in its routing
table to the key requested and forwards the request to the
corresponding node. If that request is ultimately successful and
returns with the data, the node will pass the data back to the
upstream requestor, cache the file in its own datastore, and create a
new entry in its routing table associating the actual data source with
the requested key. A subsequent request for the same key will be
immediately satisfied from the local cache; a request for a
``similar'' key (determined by lexicographic distance) will be
forwarded to the previously successful data source. Because
maintaining a table of data sources is a potential security concern,
any node along the way can unilaterally decide to change the reply
message to claim itself or another arbitrarily-chosen node as the data
source.
If a node cannot forward a request to its preferred downstream node
because the target is down or a loop would be created, the node having
the second-nearest key will be tried, then the third-nearest, and so
on. If a node runs out of candidates to try, it reports failure back
to its upstream neighbor, which will then try its second choice, etc.
In this way, a request operates as a steepest-ascent hill-climbing
search with backtracking. If the hops-to-live limit is exceeded, a
failure result is propagated back to the original requestor without
any further nodes being tried. Nodes may unilaterally curtail excessive
hops-to-live values to reduce network load. They may also forget
about pending requests after a period of time to keep message memory
free.
Figure 1 depicts a typical sequence of request
messages.
The user initiates a request at node a. Node a forwards the
request to node b, which forwards it to node c. Node c
is unable to contact any other nodes and returns a backtracking ``request
failed'' message to b. Node b then tries its second choice,
e, which forwards the request to f. Node f forwards the
request to b, which detects the loop and returns a backtracking
failure message. Node f is unable to contact any other nodes and
backtracks one step further back to e. Node e forwards the
request to its second choice, d, which has the data. The data is
returned from d via e and b back to a, which sends
it back to the user. The data is also cached on e, b, and a.
Figure 1:
A typical request sequence.
This mechanism has a number of effects. Most importantly, we
hypothesize that the quality of the routing should improve over time,
for two reasons. First, nodes should come to specialize in locating
sets of similar keys. If a node is listed in routing tables under a
particular key, it will tend to receive mostly requests for keys
similar to that key. It is therefore likely to gain more ``experience''
in answering those queries and become better informed in its routing
tables about which other nodes carry those keys. Second, nodes should
become similarly specialized in storing clusters of files having
similar keys. Because forwarding a request successfully will result
in the node itself gaining a copy of the requested file, and most
requests will be for similar keys, the node will mostly acquire files
with similar keys. Taken together, these two effects should improve
the efficiency of future requests in a self-reinforcing cycle, as
nodes build up routing tables and datastores focusing on particular
sets of keys, which will be precisely those keys that they are asked
about.
In addition, the request mechanism will cause popular data to be
transparently replicated by the system and mirrored closer to
requestors. For example, if a file that is originally located in
London is requested in Berkeley, it will become cached locally and
provide faster response to subsequent Berkeley requests. It also
becomes copied onto each computer along the way, providing redundancy
if the London node fails or is shut down. (Note that ``along the way''
is determined by key closeness and does not necessarily have
geographic relevance.)
Finally, as nodes process requests, they create new routing table
entries for previously-unknown nodes that supply files, increasing
connectivity. This helps new nodes to discover more of the network
(although it does not help the rest of the network to discover them; for that, the announcement mechanism described in section 3.5
is necessary). Note that direct links to data sources are created,
bypassing the intermediate nodes used. Thus, nodes that successfully
supply data will gain routing table entries and be contacted more often
than nodes that do not.
Since keys are derived from hashes, lexicographic closeness of keys does not
imply any closeness of the original descriptive strings and presumably, no
closeness of subject matter of the corresponding files. This lack of
semantic closeness is not important, however, as the routing algorithm is
based on knowing here keys are located, not where subjects are located.
That is, supposing a string such as text/philosophy/sun-tzu/art-of-war
yields a file key AH5JK2, requests for this file can be routed more
effectively by creating clusters containing AH5JK1, AH5JK2, and
AH5JK3, not by creating clusters for works of philosophy. Indeed,
the use of hashes is desirable precisely because philosophical works will
be scattered across the network, lessening the chances that failure of a
single node will make all philosophy unavailable. The same is true for
personal subspaces--files belonging to the same subspace will be scattered
across different nodes.
Storing data
Inserts follow a parallel strategy to requests. To insert a file, a
user first calculates a binary file key for it, using one of the procedures
described in section 3.1. She then sends an insert
message to her own node specifying the proposed key and a hops-to-live
value (this will determine the number of nodes to store it on). When
a node receives an insert proposal, it first checks its own store to
see if the key is already taken. If the key is found, the node
returns the pre-existing file as if a request had been made for it.
The user will thus know that a collision was encountered and can try
again using a different key. If the key is not found, the node looks
up the nearest key in its routing table to the key proposed and
forwards the insert to the corresponding node. If that insert causes
a collision and returns with the data, the node will pass the data
back to the upstream inserter and again behave as if a request had
been made (i.e. cache the file locally and create a routing table
entry for the data source).
If the hops-to-live limit is reached without a key collision being
detected, an ``all clear'' result will be propagated back to the
original inserter. Note that for inserts, this is a successful
result, in contrast to situation for requests. The user then sends
the data to insert, which will be propagated along the path
established by the initial query and stored in each node along the
way. Each node will also create an entry in its routing table
associating the inserter (as the data source) with the new key. To
avoid the obvious security problem, any node along the way can
unilaterally decide to change the insert message to claim itself or
another arbitrarily-chosen node as the data source.
If a node cannot forward an insert to its preferred downstream node
because the target is down or a loop would be created, the insert
backtracks to the second-nearest key, then the third-nearest, and so
on in the same way as for requests. If the backtracking returns all
the way back to the original inserter, it indicates that fewer nodes
than asked for could be contacted. As with requests, nodes may
curtail excessive hops-to-live values and/or forget about pending
inserts after a period of time.
This mechanism has three effects. First, newly inserted files are
selectively placed on nodes already possessing files with similar
keys. This reinforces the clustering of keys set up by the request
mechanism. Second, new nodes can use inserts as a supplementary
means of announcing their existence to the rest of the network.
Third, attempts by attackers to supplant existing files by inserting
junk files under existing keys are likely to simply spread the
real files further, since the originals are propagated on collision.
(Note, however, that this is mostly only relevant to keyword-signed
keys, as the other types of keys are more strongly verifiable.)
Managing data
All information storage systems must deal with the problem of finite
storage capacity. Individual Freenet node operators can configure the
amount of storage to dedicate to their datastores. Node storage is
managed as an LRU (Least Recently Used) cache[29] in which
data items are kept sorted in decreasing order by time of most recent
request (or time of insert, if an item has never been requested).
When a new file arrives (from either a new insert or a successful
request) which would cause the datastore to exceed the designated
size, the least recently used files are evicted in order until there
is room. The resulting impact on availability is mitigated by the fact
that the routing table entries created when the evicted files first
arrived will remain for a time, potentially allowing the node to later
get new copies from the original data sources. (Routing table entries
are also eventually deleted in a similar fashion as the table fills
up, although they will be retained longer since they are smaller.)
Strictly speaking, the datastore is not a cache, since the set of
datastores is all the storage that there is. That is, there is no
``permanent'' copy which is being replicated in a cache. Once all the
nodes have decided, collectively speaking, to drop a particular file,
it will no longer be available to the network. In this respect,
Freenet differs from systems such as Eternity and Free Haven which
seek to provide guarantees of file lifetimes.
The expiration mechanism has an advantageous aspect, however, in that
it allows outdated documents to fade away naturally after being
superseded by newer documents. If an outdated document is still used
and considered valuable for historical reasons, it will stay alive
precisely as long as it continues to be requested.
For political or legal reasons, it may be desirable for node operators
not to explicitly know the contents of their datastores. This is why
all stored files are encrypted. The encryption procedures used are not
intended to secure the file--that would be impossible since a requestor
(potentially anyone) must be capable of
decrypting the file once retrieved. Rather, the objective is that the
node operator can plausibly deny any knowledge of the contents of her
datastore, since all she knows a priori is the file key, not the
encryption key. The encryption keys for keyword-signed and signed-subspace
data can only be obtained by reversing a hash, and the encryption keys for
content-hash data are completely unrelated. With effort, of course,
a dictionary attack will reveal which keys are present--as it must in
order for requests to work at all--but the burden such an effort would
require is intended to provide a measure of cover for node operators.
Adding nodes
A new node can join the network by discovering the address of one
or more existing nodes through out-of-band means, then starting to
send messages. As mentioned previously, the request mechanism
naturally enables new nodes to learn about more of the network over
time. However, in order for existing nodes to discover them,
new nodes must somehow announce their presence. This process is complicated
by two somewhat conflicting requirements. On one hand, to promote efficient
routing, we would like all the existing nodes to be consistent in
deciding which keys to send a new node (i.e. what key to assign it
in their routing tables). On the other hand, it would cause a security
problem if any one node could choose the routing key, which rules out
the most straightforward way of achieving consistency.
We use a cryptographic protocol to satisfy both of these requirements.
A new node joining the network chooses a random seed and sends an
announcement message containing its address and the hash of that seed
to some existing node. When a node receives a new-node announcement,
it generates a random seed, XOR's that with the hash it received and
hashes the result again to create a commitment. It then forwards the
new hash to some node chosen randomly from its routing table. This
process continues until the hops-to-live of the announcement runs out.
The last node to receive the announcement just generates a seed. Now
all nodes in the chain reveal their seeds and the key for the new
node is assigned as the XOR of all the seeds. Checking the commitments
enables each node to confirm that everyone revealed their seeds
truthfully. This yields a consistent random key which cannot be
influenced by a malicious participant. Each node
then adds an entry for the new node in its routing table under that key.
Protocol details
The Freenet protocol is packet-oriented and uses self-contained
messages. Each message includes a transaction ID so that nodes can
track the state of inserts and requests. This design is intended to
permit flexibility in the choice of transport mechanisms for messages,
whether they be TCP, UDP, or other technologies such as packet radio.
For efficiency, nodes using a persistent channel such as a TCP connection
may also send multiple messages over the same connection. Node
addresses consist of a transport method plus a transport-specific
identifier such as an IP address and port number, e.g. tcp/192.168.1.1:19114. Nodes which change addresses frequently
may also use virtual addresses stored under address-resolution keys
(ARK's), which are signed-subspace keys updated to contain the current
real address.
A Freenet transaction begins with a Request.Handshake message from one
node to another, specifying the desired return address of the
sending node. (The sender's return address may be
impossible to determine automatically from the transport layer, or the
sender may wish to receive replies at a different address from that
used to send the message.) If the remote node is
active and responding to requests, it will reply with a
Reply.Handshake specifying the protocol version number that it
understands. Handshakes are remembered for a few hours, and
subsequent transactions between the same nodes during this time may
omit this step.
All messages contain a randomly-generated 64-bit transaction ID, a
hops-to-live limit, and a depth counter. Although the ID cannot be
guaranteed to be unique, the likelihood of a collision occurring during the
transaction lifetime among the limited set of nodes that it sees is
extremely low. Hops-to-live is set by the originator of a message and is
decremented at each hop to prevent messages being forwarded indefinitely.
To reduce the information that an attacker can obtain from the hops-to-live
value, messages do not automatically terminate after hops-to-live reaches 1
but are forwarded on with finite probability (with hops-to-live again 1).
Depth is incremented at each hop and is used by a replying node to set
hops-to-live high enough to reach a requestor. Requestors should
initialize it to a small random value to obscure their location. As with
hops-to-live, a depth of 1 is not automatically incremented but is passed
unchanged with finite probability.
To request data, the sending node sends a Request.Data message
specifying a transaction ID, initial hops-to-live and depth, and a search
key. The remote node will check its datastore for the key and if not
found, will forward the request to another node as described in
section 3.2. Using the chosen hops-to-live limit, the
sending node starts a timer for the expected amount of time it
should take to contact that many nodes, after which it will assume
failure. While the request is being processed, the remote node may
periodically send back Reply.Restart messages indicating that messages
were stalled waiting on network timeouts, so that the sending node knows
to extend its timer.
If the request is ultimately successful, the remote node will reply with a
Send.Data message containing the data requested and the address of the node
which supplied it (possibly faked). If the request is ultimately
unsuccessful and its hops-to-live are completely used up trying to satisfy
it, the remote node will reply with a NotFound?. The sending node
will then decrement the hops-to-live of the Send.Data (or NotFound?)
and pass it along upstream, unless it is the actual originator of the
request. Both of these messages terminate the transaction and release any
resources held. However, if there are still hops-to-live remaining,
usually because the request ran into a dead end where no viable non-looping
paths could be found, the remote node will reply with a Request.Continue
giving the number of hops-to-live left. The sending node will then try to
contact the next-most likely node from its routing table. It will also
send a Reply.Restart upstream.
To insert data, the sending node sends a Request.Insert message
specifying a randomly-generated transaction ID, an initial hops-to-live
and depth, and a proposed key. The remote node will check its datastore
for the key and if not found, forward the insert to another node as
described in section 3.3. Timers and Reply.Restart messages
are also used in the same way as for requests.
If the insert ultimately results in a key collision, the remote node
will reply with either a Send.Data message containing the existing
data or a NotFound? (if existing data was not actually found, but
routing table references to it were). If the insert does not
encounter a collision, yet runs out of nodes with nonzero hops-to-live
remaining, the remote node will reply with a Request.Continue. In
this case, Request.Continue is a failure result meaning that not as
many nodes could be contacted as asked for. These messages will be passed
along upstream as in the request case. Both messages
terminate the transaction and release any resources held. However, if
the insert expires without encountering a collision, the remote node
will reply with a Reply.Insert, indicating that the insert can go
ahead. The sending node will pass along the Reply.Insert upstream and
wait for its predecessor to send a Send.Insert containing the data.
When it receives the data, it will store it locally and forward the
Send.Insert downstream, concluding the transaction.
We performed simulations on a model of this system to give some
indications about its performance. Here we summarize the most
important results; for full details, see [21].
To test the adaptivity of the network routing, we created a test
network of 1000 nodes. Each node had a datastore size of 50 items and
a routing table size of 250 addresses. The datastores were
initialized to be empty, and the routing tables were initialized to
connect the network in a regular ring-lattice topology in which each
node had routing entries for its two nearest neighbors on either side.
The keys associated with these routing entries were set to be hashes
of the destination nodes' addresses. Using hashes has the useful
property that the resulting keys are both random and consistent (that
is, all references to a given node will use the same key).
Inserts of random keys were sent to random nodes in the network,
interspersed randomly with requests for randomly-chosen keys known to
have been previously inserted, using a hops-to-live of 20 for both.
Every 100 timesteps, a snapshot of the network was taken and its
performance measured using a set of probe requests. Each probe consisted
of 300 random requests for previously-inserted keys, using a hops-to-live
of 500. We recorded the resulting distribution of request
pathlengths, the number of hops actually taken before finding
the data. If the request did not find the data, the pathlength was
taken to be 500.
Figure 2 shows the evolution of the first, second,
and third quartiles of the request pathlength over time, averaged over
ten trials.
Figure 2:
Time evolution of the request pathlength.
We can see that the initially high pathlengths decrease rapidly over
time. In the beginning, few requests succeed at all, but as the network
converges, the median request pathlength drops to just six.
Next, we examined the scalability of a growing network. Starting from
a small network of 20 nodes initialized in the same manner as the previous
section, we added new nodes over time and measured the change in the request
pathlength.
Inserts and requests were simulated randomly as before. Every five
timesteps, a new node was created and added to the network by
simulating a node announcement message with hops-to-live of 10 sent
from it to a randomly-chosen existing node. The key assigned by this
announcement was taken to be the hash of the new node's address. Note
that this procedure does not necessarily imply a linear rate of
network growth, but rather a linear relationship between the request
rate and the growth rate. Since it seems likely that both rates will
be proportional to network size (yielding an exponential growth rate
in real, as opposed to simulated, time), we believe that this model is
justifiable.
Figure 3 shows the evolution of the first, second,
and third quartiles of the request pathlength versus network size, averaged
over ten trials.
Figure 3:
Request pathlength versus network size.
We can see that the pathlength scales approximately logarithmically,
with a change of slope near 40,000 nodes. We posit that the slope
change is a result of routing tables becoming filled and could be
improved by adding a small number of nodes with larger routing tables.
Section 5.4 discusses this issue in more depth.
Where our routing tables were limited to 250 entries by the memory
requirements of the simulation, real Freenet nodes should easily be
able to hold thousands of entries. Nonetheless, even this limited
network appears capable of scaling to one million nodes with a median
pathlength of just 30. Note also that the network was grown continuously,
without any steady-state convergence period.
Finally, we considered the fault-tolerance of the network. Starting
with a network grown to 1000 nodes by the previous method, we
progressively removed randomly-chosen nodes from the network to simulate
node failures. Figure 4 shows the resulting
evolution of the request pathlength, averaged over ten trials.
Figure 4:
Change in request pathlength under network failure.
The network is surprisingly robust against quite large failures. The median
pathlength remains below 20 even when up to 30% of nodes fail.
Small-world model
The scalability and fault-tolerance characteristics of Freenet can be
explained in terms of a small-world network
model[<a
HREF="#Milgram">23,<a
HREF="#Watts">31,<a
HREF="#Huberman">22,<a
HREF="#Albert">3]. In a small-world network,
the majority of nodes have only relatively few, local, connections to other
nodes, while a small number of nodes have large, wide-ranging sets of
connections. Small-world networks permit efficient short paths
between arbitrary points because of the shortcuts provided by the
well-connected nodes, as evidenced by examination of Milgram's letter-passing
experiment[<a
HREF="#Milgram">23] and the Erdös number game cited by Watts
and Strogatz[<a
HREF="#Watts">31].
Is Freenet a small world? A key factor in the identification of a
small-world network is the existence of a scale-free power-law
distribution of links within the network, as the tail of such
distributions provides the highly-connected nodes needed to create
short paths. Figure 5 shows the average
distribution of links (i.e. routing table entries) in the 1000-node
Freenet networks used in the previous section.
Figure 5:
Distribution of link number among Freenet nodes.
We see that the distribution closely approximates a power law, except
for the anomalous point representing nodes with filled 250-entry
routing tables. When we used differently-sized routing tables, this
cutoff point moved but the power-law character of the distribution
remained the same.
In addition to providing short paths, the power-law distribution also
gives small-world networks a high degree of fault-tolerance. Random
failures are most likely to knock out nodes from the majority that
possess only a small number of connections. The loss of
poorly-connected nodes will not greatly affect routing in the network.
It is only when the number of random failures becomes high enough to
knock out a significant number of well-connected nodes that routing
performance will be noticeably affected.
Security
The primary goal for Freenet security is protecting the anonymity of
requestors and inserters of files. It is also important to protect
the identity of storers of files. Although trivially anyone can turn
a node into a storer by requesting a file through it, thus
``identifying'' it as a storer, what is important is that there remain
other, unidentified, holders of the file so that an adversary cannot
remove a file by attacking all of the nodes that hold it. Files must
be protected against malicious modification, and finally, the system
must be resistant to denial-of-service attacks.
Reiter and Rubin[<a
HREF="#Reiter">25] present a useful taxonomy of anonymous
communication properties on three axes. The first axis is the type of
anonymity: sender anonymity or receiver anonymity, which mean
respectively that an adversary cannot determine either who originated
a message, or to whom it was sent. The second axis is the adversary
in question: a local eavesdropper, a malicious node or collaboration
of malicious nodes, or a web server (not applicable to Freenet). The
third axis is the degree of anonymity, which ranges from absolute
privacy (the presence of communication cannot be perceived) to beyond
suspicion (the sender appears no more likely to have originated the
message than any other potential sender), probable innocence (the
sender is no more likely to be the originator than not), possible
innocence, exposed, and provably exposed (the adversary can prove to
others who the sender was).
As Freenet communication is not directed towards specific receivers,
receiver anonymity is more accurately viewed as key anonymity, that
is, hiding the key which is being requested or inserted.
Unfortunately, since routing depends on knowledge of the key, key
anonymity is not possible in the basic Freenet scheme (but see the
discussion of ``pre-routing'' below). The use of hashes as keys
provides a measure of obscurity against casual eavesdropping, but is
of course vulnerable to a dictionary attack since their unhashed
versions must be widely known in order to be useful.
Freenet's anonymity properties under this taxonomy are shown in
Table 1.
Table 1:
Anonymity properties of Freenet.
System
Attacker
Sender anonymity
Key anonymity
Basic Freenet
local eavesdropper
exposed
exposed
collaborating nodes
beyond suspicion
exposed
Freenet + pre-routing
local eavesdropper
exposed
beyond suspicion
collaborating nodes
beyond suspicion
exposed
Against a collaboration of malicious nodes, sender anonymity is preserved
beyond suspicion since a node in a request path cannot tell whether its
predecessor in the path initiated the request or is merely forwarding it.
[<a
HREF="#Reiter">25] describes a probabilistic attack which might compromise
sender anonymity, using a statistical analysis of the probability that a
request arriving at a node a is forwarded on or handled directly, and
the probability that a chooses a particular node b to forward
to. This analysis is not immediately applicable to Freenet, however, since
request paths are not constructed probabilistically. Forwarding depends on
whether or not a has the requested data in its datastore, rather than
chance. If a request is forwarded, the routing tables determine where it
is sent to, and could be such that a forwards every request to b, or never forwards any requests to b, or anywhere in between.
Nevertheless, the depth value may provide some indication as to how many
hops away the originator was, although this is obscured by the random
selection of an initial depth and the probabilistic means of incrementing
it (see section 4). Similar considerations apply to
hops-to-live. Further investigation is required to clarify these issues.
Against a local eavesdropper there is no protection on messages
between the user and the first node contacted. Since the first node
contacted can act as a local eavesdropper, it is recommended
that the user only use a node on her own machine as the first point of
entry into the Freenet network. Messages between nodes are encrypted
against local eavesdropping, although traffic analysis may still be
performed (e.g. an eavesdropper may observe a message going out
without a previous message coming in and conclude that the target
originated it).
Key anonymity and stronger sender anonymity can be achieved by adding
mix-style ``pre-routing'' of messages. In this scheme, basic Freenet
messages are encrypted by a succession of public keys which determine
the route that the encrypted message will follow (overriding the
normal routing mechanism). Nodes along this portion of the route are
unable to determine either the originator of the message or its
contents (including the request key), as per the mix-net anonymity
properties. When the message reaches the endpoint of the pre-routing
phase, it will be injected into the normal Freenet network and behave
as though the endpoint were the originator of the message.
Protection for data sources is provided by the occasional resetting of the
data source field in replies. The fact that a node is listed as the data
source for a particular key does not necessarily imply that it actually
supplied that data, or was even contacted in the course of the request. It
is not possible to tell whether the downstream node provided the file or
was merely forwarding a reply sent by someone else. In fact, the very act
of successfully requesting a file places it on the downstream node if it
was not already there, so a subsequent examination of that node on
suspicion reveals nothing about the prior state of affairs, and provides a
plausible legal ground that the data was not there until the act of
investigation placed it there. Requesting a particular file with a
hops-to-live of 1 does not directly reveal whether or not the node was
previously storing the file in question, since nodes continue to forward
messages having hops-to-live of 1 with finite probability. The success of
a large number of requests for related files, however, may provide grounds
for suspicion that those files were being stored there previously.
Modification of requested files by a malicious node in a request chain is
an important threat, and not only because of the corruption of the files
themselves. Since routing tables are based on replies to requests, a node
might attempt to steer traffic towards itself by pretending to have
files when it does not and simply returning fictitious data. For data
stored under content-hash keys or signed-subspace keys, this is
not feasible since inauthentic data can be detected unless a node
finds a hash collision or successfully forges a cryptographic
signature. Data stored under keyword-signed keys, however,
is vulnerable to dictionary attack since signatures can be made by
anyone knowing the original descriptive string.
Finally, a number of denial-of-service attacks can be envisioned. The
most significant threat is that an attacker will attempt to fill all
of the network's storage capacity by inserting a large number of
junk files. An interesting possibility for countering this attack
is a scheme such as Hash Cash[<a
HREF="#Hash">20]. Essentially, this scheme
requires the
inserter to perform a lengthy computation as ``payment'' before an
insert is accepted, thus slowing down an attack. Another alternative
is to divide the datastore into two sections, one for new inserts and
one for ``established'' files (defined as files having received at
least a certain number of requests). New inserts can only displace
other new inserts, not established files. In this way a flood of
junk inserts might temporarily paralyze insert operations but would
not displace existing files. It is difficult for an attacker to
artificially legitimize her own junk files by requesting them
many times, since her requests will be satisfied by the first node to
hold the data and not proceed any further. She cannot send requests
directly to the other downstream nodes holding her files since their
identities are hidden from her. However, adopting this scheme may
make it difficult for genuine new inserts to survive long enough to be
requested by others and become established.
Attackers may attempt to displace existing files by inserting alternate
versions under the same keys. Such an attack is not possible against a
content-hash key or signed-subspace key, since it requires finding a
hash collision or successfully forging a cryptographic signature. An
attack against a keyword-signed key, on the other hand, may result in
both versions coexisting in the network. The way in which nodes react to
insert collisions (detailed in section 3.3) is intended to
make such attacks more difficult. The success of a replacement attack can
be measured by the ratio of corrupt versus genuine versions resulting in
the system. However, the more corrupt copies the attacker attempts to
circulate (by setting a higher hops-to-live on insert), the greater the
chance that an insert collision will be encountered, which would cause an
increase in the number of genuine copies.
The Freenet network provides an effective means of anonymous
information storage and retrieval. By using cooperating nodes spread
over many computers in conjunction with an efficient adaptive routing
algorithm, it keeps information anonymous and available while
remaining highly scalable. Initial deployment of a test version is
underway, and is so far proving successful, with tens of thousands of
copies downloaded and many interesting files in circulation. Because
of the anonymous nature of the system, it is impossible to tell exactly how
many users there are or how well the insert and request mechanisms are
working, but anecdotal evidence is so far positive. We are working on
implementing a simulation and visualization suite which will enable
more rigorous tests of the protocol and routing algorithm. More
realistic simulation is necessary which models the effects of nodes
joining and leaving simultaneously, variation in node capacity and bandwidth,
and larger network sizes. We would also like to implement a public-key
infrastructure to authenticate nodes and create a searching mechanism.
American National Standards Institute, American National Standard
X9.30.2-1997: Public Key Cryptography for the Financial Services
Industry - Part 2: The Secure Hash Algorithm (SHA-1) (1997).
R.J. Anderson, ``The Eternity service,'' in Proceedings of the 1st
International Conference on the Theory and Applications of Cryptology
(PRAGOCRYPT '96), Prague, Czech Republic (1996).
O. Berthold, H. Federrath, and S. Köpsell, ``Web MIXes: a system
for anonymous and unobservable Internet access,'' in Proceedings
of the Workshop on Design Issues in Anonymity and Unobservability,
Berkeley, CA, USA. Springer: New York (2001).
Y. Chen, J. Edler, A. Goldberg, A. Gottlieb, S. Sobti, and
P. Yianilos, ``A prototype implementation of archival intermemory,''
in Proceedings of the Fourth ACM Conference on Digital Libraries (DL
'99), Berkeley, CA, USA. ACM Press: New York (1999).
I. Clarke, ``A distributed decentralised information storage and
retrieval system,'' unpublished report, Division of
Informatics, University of Edinburgh (1999). Available at
http://www.freenetproject.org/ (2000).
R. Dingledine, M.J. Freedman, and D. Molnar, ``The Free Haven project:
distributed anonymous storage service,'' in Proceedings of the
Workshop on Design Issues in Anonymity and Unobservability, Berkeley,
CA, USA. Springer: New York (2001).
D. Goldschlag, M. Reed, and P. Syverson, ``Onion routing for anonymous and
private Internet connections,'' Communications of the ACM42(2), 39-41 (1999).
M. Waldman, A.D. Rubin, and L.F. Cranor, ``Publius: a robust,
tamper-evident, censorship-resistant, web publishing system,'' in Proceedings of the Ninth USENIX Security Symposium, Denver, CO, USA
(2000).
Note: We constantly get requests of people who want to become
unsubscribed. YOU have to do that yourself! Just click on the www
link provided at the bottom of every mail, enter your e-mail address
in the text field in section "Subscribers" and provide
your password under the unsubscribe option. (You can get your
password here as well, in case you forgot it.)
Please sign up here to be notified of major Freenet developments, such
as announcements of new releases or important bugfixes. This list is
very low traffic (less than one message per month).
Asking for or giving advice relating to getting Freenet working, bug
reports, and suggestions on improving the user experience. Requests
for help are more likely to be heard here than in the other mailing
lists.
Discussion pertaining to the next release of Freenet. What features
should and shouldn't go in, how things should be implemented,
etc. Discussions about how Freenet should be in general (as opposed to
in the very next release) should go to the technical list. If you
think you have a great idea for a feature or attack, read all of the
documentation first, espcially the Frequently Asked Questions. The
developers have little patience for repeated suggestions.
Technical Discussion
(archive)
Technical issues related to Freenet, not specifically tied to
day-to-day implementation. Cryptography, packet radio, related
projects, suggestions for future versions, attacks on the design, etc.
Anything which deals with technology and relates to Freenet should go
here.
Comment: I tried using your site to publish a web site but gave up after 2 hours. Is this site for computer boffins? I note that there is no email address for comments on the home page. Is that why the site is very un-user friendly. When trying to download all the software I was bounced from site to site and the links eventually crashed when I was told I did not have the right java sun executable script. What ever that is. Anyhow can you reccomend a site that will allow me to publish my web site without any hassle. Cheers Mike Liberty through technology yeh right I give this email 90:10 chance of response against.
To work correctly, Freenet requires that other Freenet nodes can establish TCP connections with your node, typically a NAT or a Firewall will prevent this, however there may be ways around it if you can modify the NAT or Firewall settings. Here is how:
Install Freenet as normal, taking note of which port it is listening on for external connections (the listenPort parameter in freenet.conf or freenet.ini will tell you this). You should then edit your firewall settings and configure it to allow incoming TCP connections on that port.
If your computer is on a network that is behind a NAT or Firewall
Install Freenet as normal, except instead of giving it the IP address of your computer, give it the IP address of the NAT or Firewall.
Edit the configuration of your NAT or Firewall and set it to forward incoming TCP connections on that port to the IP address of your computer.
If you do not have the ability to do this, contact your network administrator, they may be able to help you (and if they can't or won't, do your very best to get them fired, they are either unqualified, or don't respect your freedom of speech ;-).
Note: This may be an incomplete list, a large number of people have contributed to the project. Contributors are responsible for adding themselves along with a brief biography to this list.
Freenet is based on Ian's paper "A Distributed Decentralised Information Storage and Retrieval System". Ian started the Freenet Project around July of 1999, and continues to coordinate the project.
Brandon was the first to contribute to the Freenet project, and is responsible for much of the code that went into Freenet 0.1. Brandon has since moved on to pastures new, and is no longer directly involved in Freenet.
Tavin is the most recent addition to the Freenet core development team. He is responsible for much of how Freenet stores files efficiently and securely on the users computer.
There are many reasons why people get involved in the Freenet Project. Some share the views outlined in this document; some share variations of these views, which are also served by what we are trying to achieve; and some just enjoy the technical challenge. These are the ideas which motivated me to architect the system in the first place, but not necessarily the views that everyone involved in the Freenet project holds.
Freedom of speech, in most western cultures, is generally considered to be one of the most important rights any individual might have. Why is the freedom to share ideas and opinions so important? There are several ways to answer this question.
One of the most obvious differences between mankind and the rest of the animal kingdom is our ability to communicate sophisticated and abstract concepts. While we constantly discover that animal's communication ability is more sophisticated than previously assumed, it is unlikely that any other animal approaches our own level of ability in this area.
Most people, given the option of knowing something and not knowing something, will choose to have more information rather than less. Wars have been won and lost over who was better-informed. This is because being better-informed allows us to make better decisions, and generally improve our ability to survive and be successful.
Many people today live under democratic governments, and those who don't, probably want to. Democracy is an answer to the question of how to create leaders, while preventing them from abusing that power. It achieves this by giving the population the power to regulate their government through voting, yet the ability to vote does not necessarily mean that you live in a democratic country. For a population to regulate their government effectively it must know what their government is doing, they must be well informed. It is a feedback loop, but this loop can be broken if the government has the power to control the information the population has access to.
Everyone values their freedom, in fact, many consider it so important that they will die for it. People like to think that they are free to form and hold whatever opinions they like, particularly in western countries. Consider now that someone had the ability to control the information you have access to. This would give them the ability to manipulate your opinions by hiding some facts from you, by presenting you with lies and censoring anything that contradicted those lies. This is not some Orwellian fiction, it is standard practice for most western governments to lie to their populations, so much so, that people now take it for granted, despite the fact that this undermines the very democratic principals which justify the government's existence in the first place.
The only way to ensure that a democracy will remain effective is to ensure that the government cannot control its population's ability to share information, to communicate. So long as everything we see and hear is filtered, we are not truly free. Freenet's aim is to allow two or more people who wish to share information, to do so.
Of course no issue is black and white, and there are many who feel that censorship is a good thing in some circumstances. For example, in some European countries propagating information deemed to be racist is illegal. Governments seek to prevent people from advocating ideas which are deemed damaging to society. There are two answers to this however. The first is that you can't allow those in power to impose "good" censorship, without also enabling them to impose "bad" censorship. To impose any form of censorship a government must have the ability to monitor and thus restrict communication. There are already criticisms that the anti-racism censorship in many European countries is hampering legitimate historical analysis of events such as the second world war.
The second argument is that this "good" censorship is counter-productive even when it does not leak into other areas. For example, it is generally more effective when trying to persuade someone of something to present them with the arguments against it, and then answer those arguments. Unfortunately, preventing people from being aware of the often sophisticated arguments used by racists, makes them vulnerable to those arguments when they do eventually encounter them.
Of course the first argument is the stronger one, and would still hold-true even if you didn't accept the second. Basically, you either have censorship, or you don't. There is no middle-ground.
You cannot have freedom of speech without the option to remain anonymous. Most censorship is retrospective, it is generally much easier to curtail free speech by punishing those who exercise it afterward, rather than preventing them from doing it in the first place. The only way to prevent this is to remain anonymous. It is a common misconception that you cannot trust anonymous information. This is not necessarily true, using digital signatures people can create a secure anonymous pseudonym which, in time, people can learn to trust. Freenet incorporates a mechanism called "subspaces" to facilitate this.
Of course much of Freenet's publicity has centered around the issue of copyright, and thus I will speak to it briefly. The core problem with copyright is that enforcement of it requires monitoring of communications, and you cannot be guaranteed free speech if someone is monitoring everything you say. This is important, most people fail to see or address this point when debating the issue of copyright, so let me make it clear:
You cannot guarantee freedom of speech and enforce copyright law
It is for this reason that Freenet, a system designed to protect Freedom of Speech, must prevent enforcement of copyright.
Firstly, even if copyright were the only way that artists could be rewarded for their work, then I would contend that freedom is more important than having professional artists (those who claim that we would have no art do not understand creativity: people will always create, it is a compulsion, the only question is whether they can do it for a living).
Secondly, it could be questioned whether copyright is effective even now. The music industry is one of the most vocally opposed to enhancements in communication technology, yet according to many of the artists who should be rewarded by copyright, it is failing to do so. Rather it has allowed middle-men to gain control over the mechanisms of distribution, to the detriment of both artists and the public.
Fortunately it won't come to this. There are many alternative ways to reward artists. The simplest is voluntary payment. This is an extension of the patronage system which was frequently used to reward artists prior to copyright, where a wealthy person would fund an artist to allow them to create full-time. The Internet permits an interesting extension of this idea, where rather than having just one wealthy patron, you could have hundreds of thousands, contributing small amounts of money over the Internet.
We actually practice what we preach in this regard too, on the 15th of March 2001 the Freenet Project started taking donations, and within a week we had collected over $1000.
Of course some people ridicule this idea on the basis (I assume) that nobody would ever pay for something unless forced to do so (despite significant evidence to the contrary). While I disagree with their rather depressing outlook on humanity, there are more sophisticated mechanisms which do appeal to people's self-interest, such as "Fairshare", where people can buy in to artists much as a venture capitalist will buy into an idea they like, and if that artist is successful they will be rewarded in proportion to their original contribution. This has the nice effect of encouraging people to give more money to obscure artists who they believe have potential. If their investment doesn't pay-off, then they still have the satisfaction that they contributed to an artist whose work they enjoy.
Over the past few months, most will have noticed a frustrating bug which caused the node to lock-up, and to fail to start until the datastore had been cleared or reset. This became known as the "datastore bug", and remained the primary obsticle to release of the stable 0.5 version.
Tavin Cole realised months ago that the datastore bug was symptomatic of some fundamental flaws in the implementation of the datastore, and set about a lenghtly rewrite.
In the mean-time, other developers continued to refine other aspects of the code base, making it actually quite usable despite the crippling datastore bug. Probably the most obvious such improvement is reworking the way Freenet handled other nodes in the network which were unreliable. We have also refined some other aspects of how Freenet handles communication with other nodes in the network.
Third-party developers have also been hard at work, Frost being a particularly good example.
A few weeks before Christmas Tavin unveiled the new datastore code, and in the intervening few weeks we have been working to reintegrate it into the main Freenet codebase. That process is nearing completion now, to the point that the node is working (and apparently free of any datastore bug!).
There are, however, a few remaining issues, the most visible being that the node occasionally returns random rubbish instead of data, this can be cured by re-requesting the data. Tavin is confident that he will be able to locate and fix the problem within the next few days.
We are also reorganising the code, the intention being to make life easier for both developers and users, and to bring the layout in-line with what is becomming standard practice with Java software.
Anyway, things are really starting to come together, after a couple of weeks of testing my hope is that we can release Freenet 0.5. Impatient users should be able to start downloading snapshots containing the new datastore code in the next couple of days.
- Ian.
As of today Tavin thinks he has fixed the data corruption bug which was causing serious problems for Freenet since the introduction of the new datastore code. Basically the bug caused data to be corrupted the first time it was requested, but subsequent requests would be fine. It is likely that this was causing many nodes to be dereferenced (if a node returns bogus data it is assumed to be broken and a node will not communicate with it any more). This bug was perhaps most obvious to Frost users.
Sebastian continues to work on the updated Windows installer. The plan is to make it download the latest version of Freenet, so that Windows users can also ensure that they are using the latest snapshot of the code just like Linux users.
We are planning to revive the custom bug tracking system, FBS, which was originally written by Adam Langley as a response to criticism of Sourceforge's bug tracker.
To conclude, bugs are being squashed in the new datastore and surrounding code at a reassuring rate, users should try to keep up-to-date with the latest Freenet snapshots.
Symmetric cryptography is the variety of cryptography most people are familiar with. There is a key which only the sender and receiver know, the crypto algorithm allows the sender to encrypt a message into a garbled "cyphertext" message that only someone else who knows the key can decode back into the original message.
The problem is that this mechanism is only as secure as the sender's ability to transmit the key securely to the receiver, which can often be an expensive task beyond the ability of most people.
Public Key cryptography offered a solution to this problem. It involves two keys, a "public" key and a "private" key. The receiver creates a public and private key-pair. The public key can be used to encrypt a message, but only the corresponding private key can be used to decrypt it. The receiver can then send his public key to the transmitter, it doesn't matter who else knows the public key. The transmitter can then encrypt the message using the public key, and send it to the receiver. Even if other people know the public key, they cannot use it to decrypt the message, only the receiver who has the private key can actually read the message.
Public Key cryptography can also be used in reverse, the transmitter can create a public and private key pair and give the public key to everyone. They can then use their private key to "sign" a message. Anyone with the public key can use it to verify that the message was signed by whoever knew the private key.
A number of algorithms are available for public-private key cryptography. Their existance has far-reaching implications, since they essentially allow almost anyone to communicate securely, even those who do not have the resources to exchange keys privately.
Freenet uses public-private key cryptography in a number of rather innovate ways to to achieve its goals.
An excellent book on this and related subjects is "Applied Cryptography" by Bruce Schneier (Amazon, Barnes and Nobel). It it aimed at a technical audience but there is also material of interest to the semi-technical.
Here you can find some links to articles and stories about Freenet.
Some are more accurate than others but you can judge for yourself!
If you are aware of any publicity not listed here please email
the Freenet
webpage team.
March 7th, 2002: Digital Village Radio
A Real Audio archive available of Freenet's Ian Clarke, Chris Burnett of IndyMedia, and Steven Starr of Freenet, IndyMedia, and KPFK. They are discussing Freenet and IndyMedia on Digital Village, a technology show on KPFK. Listen to part 1 and part 2.
Freenet
A nice "small-media" article which comments on likely positive and
negative reactions to Freenet.
April 26, 2001: New York Times
Punching Holes in Internet Walls
Not about Freenet, but discusses how peer-to-peer is being used to evade
Internet censorship in Saudi Arabia.
April 11, 2001: CNET.com
Intel, others fund Freenet creator's start-up
Somewhat off-topic - Uprizer gets first-round venture capital funding.
Some discussion of commercial uses for the technology behind Freenet.
March 27, 2001: Salon.com
Who is spying on your downloads?
Discusses the privacy shortcomings of Napster and Gnutella, and
highlights Freenet's advantages over these systems.
March 20, 2001: Newsbytes
Freenet: Will It Smash Copyright Law?
A good article covering the conflict between freedom of speech and
copyright. Has some good quotes from some interesting people.
Freenet Casts Wide
Fairly wide-ranging story about Freenet and its capabilities and
implications, including some stuff on EOF and Espra.
February 14, 2001: Stanford University
Seminar by Ian Clarke on Freenet
The Freenet Project:A distributed decentralized information storage and
retrieval system (Requires Micro$oft Windows Media player to view).
Face-to-Face with Peer-to-Peer Networking
Nice overview of the peer-to-peer concept from a technical point of view,
featuring quote from Rob Kramer (Uprizer). Subscribers only.
October 26, 2000: CNET.com
A brave new--or old--world?
"Ian Clarke: Coder with attitude." In-depth discussion of the whole
peer-to-peer landscape from a variety of angles.
re:Ian Clarke
A nice interview with the author of the "Cluetrain Manifesto",
Chris Locke, which highlights the fact that Freenet is about
much more than just
Copyright.
RadioSpy? Interview: Ian Clarke - Developer of Freenet
Largely a warts-an'-all transcript of an interview with Ian,
but gives a rather comprehesive snapshot of Ian's views on
various issues..
Things have really started to heat up now. In terms of the articles
below I have tried to include both articles for and against Freenet, but
because of the vast number of commentaries on Freenet we need to be
more selective. We will try to include a good cross-section, however
our interpretation of what is an intelligent informative article will
probably impose some bias by default - Ian ;-)
Genie 1, Bottle 0
Very amusing article on Freenet and copyright.
Highly recommended.
May 24, 2000: Channel 4 News
Hackers stay one step ahead
A very cool news item talking about recent attempts by the British
government to censor the Internet and how Freenet will make this
very difficult.
Includes text and streaming video of the item.
May 23, 2000: Libération
L'anarchie est au bout du clavier
An interesting French article about Freenet, concentrating on the freedom
of information aspects of the system rather than just copyright.
May 12, 2000: National Post
Napster secured page in Internet history
Interesting description of why Freenet is not vulnerable in the same
way that Napster is, although I must say that their "final thought" is
slightly perplexing!
May 12, 2000: O'Reilly Network
Gnutella and Freenet represent true technological innovation
A nice article concentrating, for a change, on the technical side of
Freenet and Gnutella.
Reasonably accurate, although it understates the efficiency improvement
that Freenet should provide
(describing it as of comparable efficiency to the WWW where it
should be much more efficient).
Client As Server: The New Model
An interesting article discussing distributed systems and how systems
like Freenet are actually in a similar spirit to the original Internet.
Freedom on the Net?
A rehash of the New Scientist article below, but likely
to reach a much larger audience.
March 25, 2000: New Scientist
Out of control
A "big bad Internet"-style article, but it is reasonably well researched
and seeks the opinions of those who might be considered Freenet's
opposition.
Freenet, a polemic concept to deal with WWW
An English translation of a Brazilian interview with
Ian Clarke.
Focuses on the technical aspects of Freenet, and goes into
a reasonable amount of detail as to how the system works.
Get in on the Ground Floor of Freedom
A very positive little article describing Freenet and why they think
it is interesting using some rather "colorful" language.
August 14, 1999: Brave Gnu World
FreeNET
One of the first articles about Freenet back when it was 100% theory.
Still an excellent introduction to the way Freenet works.
Putting anonymity aside there are several benefits in publishing websites into Freenet (known as FreeSites).
First and foremost there is no need to worry about banner ads and size limits. Availability and uptime are proportional to the popularity of the FreeSite because the information in Freenet is being mirrored intelligently and as long as there is enough demand the site will be widely available.
Also, because of the sophisticated distribution mechanisms inherent in Freenet the access to the FreeSites will gradually improve and there are good chances that with time a FreeSite will load faster than an identical website in the conventional internet. To see how and why this works you can look at the in-depth information in the Papers and Architecture sections.
As always, things have been moving rapidly in Freenet development. Over the past few weeks there has been the usual gaggle of bug-fixes, the datastore code is looking very stable at the moment, and user-feedback is pretty positive.
The focus has recently shifted to node and network performance. We have done some detailed profiling of the node's memory and processor usage, and in the process identified and fixed some problems that were really slowing down people's machines.
We implemented a new "Infolet" architecture, which provides a more user-friendly way to peer inside your node's inner-workings. This is now available by default, just regenerate your freenet.conf file and select the NodeInfoServlet option, then visit http://127.0.0.1:8890/ in your web browser.
A new third-party application has come onto the scene. "Freenet Message Board" allows people to communicate in a manner similar to Usenet but where everyone's messages can be cryptographically authenticated. See Third Party Tools for further details of FMB.
Applications like FMB generate a lot of traffic on the network, so we have also been working to reduce overall network traffic. Just today Oskar checked in some modifications which should reduce the impact that messaging applications such as Frost and FMB are having on the network.
Along similar lines, Oskar and GJ have been working to improve Freenet's load balancing, they have already checked-in some improvements, and are currently doing some research to decide how-best to further address this issue.
Bottom line: Things are moving quickly, and people should ensure that they keep up-to-date with the daily snapshot so that they don't miss out on new improvements.
Comment: Doctoral student of economics who happens to be the coordinator for all Windows related stuff. By accident (and with a lot of support) we managed to hack a pretty nice installer and configurator together.
end of interesting part for others
Here follow some random text snippets, which I don't want to loose, but haven't found a place yet to put them in:
> I think calling System.runFinalizersOnExit(true) may help (at least for SIGTERM kills).
"Deprecated. This method is inherently unsafe. It may result in
finalizers being called on live objects while other threads are
concurrently manipulating those objects, resulting in erratic behavior
or deadlock." It has been deprecated since 1.1 and I think it will be gone soon.
Personal Preferences (details in TWikiVariables)
Horizontal size of text edit box:
Set EDITBOXWIDTH = 70
Vertical size of text edit box:
Set EDITBOXHEIGHT = 17
Optionally write protect your home page: (set it to your WikiName)
The last few months of Freenet development have largely been consumed by refining the current code-base, tracking down and fixing bugs, and making sure that the existing functionality works.
Tavin has continued to find and fix bugs in the datastore, and its behavior is now quite stable.
Oskar, Tavin, and Freenet-newcomer, Niklas Mehner have recently checked in some fixes to some problems which were causing "thread leaks", these significantly increased the Freenet node's resource usage, and were eventually leading to nodes locking up. Niklas has also been working to improve the efficiency of the crypto code in Freenet.
Jay Oliveri has taken over work on FCPTools, the set of command-line utilities which make is rather easy to insert websites into Freenet.
Frost continues to progress and seems to have established a significant user-base already.
FreeWeb has not seen many changes in a while, but that may be an indication that it finally has the functionality people need to publish Freesites easily from Windows.
Bottom line: Freenet has never been as stable as it is now. We are definitely on the home-straight to a 0.5 release.
Comment: I'm .philosophically interested in distributed computing, and have a 1.5 GH processor together with [an absolute maximum] of 10 GB of harddisk which could be made available for eight hours/day. I'm a little cautious about lowering my firewall defenses, and will need some reassurance on that score. Please advise. SN
A simplistic way to look at Freenet is as a filesystem, where anyone can save a file under a filename of their choice, and anyone else, given the filename, can load the file, but unlike a file system, you cannot modify or overwrite a file in Freenet, and Freenet will only retain a file for so-long as it is popular.
Imagine you wanted to publish a daily newspaper using this mechanism. One way to do this would be to insert every edition under a name (aka "Freenet key") consisting of the name of your newspaper, and today's date, for example "the freenet times-17022002". This is nice because people always know what key they need to request to get the latest edition of your newspaper.
Unfortunately there is a problem, which is that someone who wanted to annoy you could simply publish a fake edition of your newspaper under tomorrow's key, and there would be nothing you can do about it. In fact, if they really wanted to annoy you, they could insert a fake edition under every key for the next 100 years!
Freenet's subspace mechanism attempts to address this problem, by allowing people to create private "namespaces" to which only they can write. This is achieved using public/private key cryptography by creating a new type of Freenet-key which contains both a public key, and a descriptive text string, for example:
Freenet nodes will check to make sure that any file under this Freenet key will be accompanied by a signature, made using the private key which corresponds to the public key. This means that only the creator of the public key (ie. the holder of the corresponding private key), is the only person who can insert data under keys beginning with 9G4s%7EjLQJB7ALQg-v2q5xKAJy9YPAgM/.
This means that you can now create a secure namespace within Freenet into which you can publish your newspaper without needing to worry about whether someone else can insert a fake edition under tomorrow's key.
Note: Set the members of TWiki Administrator Group in GROUP as a comma separated list
Related topics:TWikiUsers, TWikiGroups, TWikiAccessControl
-- PeterThoeny? - 28 Oct 2000
Add your groups to this list and define new group topics similar to existing ones. Group topics must end in ...Group.IMPORTANT NOTE: Think twice before restricting write access to a web or a topic, because an open system where everybody can contribute is the essence of the WikiCulture. Experience shows that unrestricted write access works very well because:
There is enough peer pressure to post only conform content.
Content does not get lost because topics are under revision control.
A topic revision can be undone by a member of the TWikiAdminGroup in case needed.
A guest of this TWiki web, not unlike yourself. You can leave your trace behind you, just add your name in TWikiRegistration and create your own page.
Personal Preferences (details in TWikiVariables)
Horizontal size of text edit box:
Set EDITBOXWIDTH = 70
Vertical size of text edit box:
Set EDITBOXHEIGHT = 17
Default state of the link check box in the attach file page:
List of TWiki users
Please take the time and add yourself to the list. To do that fill out the form in TWikiRegistration. This will create an account for you which allows you to edit topics.
ABCDEFGHIJKLMNOPQRSTUVWXYZ
TWikiVariables are text strings - %VARIABLE% - that expand into content whenever a page is opened. Variables are replaced by their actual values: stored data, or system info (like the date, or the current user). There are predefined variables, and Preference variables that you set. You can also define custom variables, with new names and values.
Most predefined variables return values that were either defined when TWiki was installed, or taken from server info (like current username, or date and time). Many of the variables let you control how the formatted results appear.
TWiki expands the following variables (enclosed in % percent signs):
Variable:
Expanded to:
%WIKIHOMEURL%
The base script URL of TWiki, is the link of the Home icon in the upper left corner, is http://freenetproject.org/twiki
%SCRIPTURL%
The script URL of TWiki, is http://freenetproject.org/cgi-bin/twiki
%SCRIPTURLPATH%
The path of the script URL of TWiki, is /cgi-bin/twiki
%SCRIPTSUFFIX%
The script suffix, ex: .pl, .cgi is
%PUBURL%
The public URL of TWiki, is http://freenetproject.org/twiki
%PUBURLPATH%
The path of the public URL of TWiki, is /twiki
%ATTACHURL%
The attachment URL of the current topic, is http://freenetproject.org/twiki/TWiki/TWikiVariables Example: If you attach a file you can refer to it as %ATTACHURL%/image.gif
%ATTACHURLPATH%
The path of the attachment URL of the current topic, is /twiki/TWiki/TWikiVariables
%URLPARAM{"name"}%
Returns the value of a URL parameter. Ex: %URLPARAM{"skin"}% returns print for a .../view/TWiki/TWikiVariables?skin=print URL. Is
%WIKITOOLNAME%
Name of wiki tool, is TWiki
%WIKIVERSION%
Wiki tool version is 01 Dec 2001
%USERNAME%
Your login username is guest
%WIKINAME%
Your Wiki username. Same as %USERNAME% if not defined in the TWikiUsers topic. Is TWikiGuest
%WIKIUSERNAME%
Your %WIKINAME% including the Main web name. Usefull for signatures. Is Main.TWikiGuest
The index topic of all registered users. Is TWikiUsers
%WIKIPREFSTOPIC%
The web preferences topic. Is TWikiPreferences
%WEBPREFSTOPIC%
The web preferences topic. Is WebPreferences
%STATISTICSTOPIC%
The web statistics topic. Is WebStatistics
%TOPIC%
The current topic name, is TWikiVariables
%BASETOPIC%
The name of the topic where the includes started, e.g. the first topic of nested includes. Same as %TOPIC% in case there is no include.
%INCLUDINGTOPIC%
The name of the topic that includes the current topic. Same as %TOPIC% in case there is no include.
%SPACEDTOPIC%
The current topic name with added spaces, for regular expression search of Ref-By, is TWiki%20*Variables
%TOPICLIST{"format"}%
Topic index of a web. The "format" defines the format of one topic item. It may include variables: The $name variable gets expanded to the topic name; the $web variable gets expanded to the name of the web.
Parameters are format, separator and web:
Parameter:
Description:
Default:
"format"
Format of one line, may include $name and $web variables
"$name"
format="format"
(Alternative to above)
"$name"
separator=", "
line separator
"\n" (new line)
web="Name"
Name of web
Current web
Examples:
%TOPICLIST{" * $web.$name"}% creates a bullet list of all topics.
%TOPICLIST{separator=", "}% creates a comma separated list of all topics.
%TOPICLIST{" <option>$name</option>"}% creates an option list (for drop down menus).
%WEBLIST{"format"}%
Web index, e.g. list of all webs. Hidden webs are excluded, e.g. webs with a NOSEARCHALL=on preference variable. The "format" defines the format of one web item. The $name variable gets expanded to the name of the web, $qname gets expanded to double quoted name, $marker to marker where web matches selection.
Parameters are format, separator and web:
Parameter:
Description:
Default:
"format"
Format of one line, may include $name variable
"$name"
format="format"
(Alternative to above)
"$name"
separator=", "
line separator
"\n" (new line)
webs="public"
comma sep list of Web, public expands to all non-hidden
"public"
marker="selected"
Text for $marker where item matches selection, otherwise equals ""
"selected"
selection="%WEB%"
Current value to be selected in list
section="%WEB%"
Examples: %WEBLIST{" * [[$name.WebHome]]"}% creates a bullet list of all webs.
%WEBLIST{"" webs="Trash,public" selection="TWiki" separator=" "}% Dropdown of all public Webs + Trash Web, current Web highlighted.
%GMTIME%
GM time, is Thu Apr 18 22:52:54 2002
%GMTIME{"format"}%
Formatted GM time based on time variables.
Variable:
Unit:
Example
$seconds
seconds
59
$minutes
minutes
59
$hours
hours
23
$day
day of month
31
$month
month in ISO format
Dec
$mo
2 digit month
12
$year
4 digit year
1999
$ye
2 digit year
99
Variables can be shortened to 3 characters. Example: %GMTIME{"$day $month, $year - $hour:$min:$sec"}% is 18 Apr, 2002 - 22:52:54
%SERVERTIME%
Server time, is Thu Apr 18 15:52:54 2002
%SERVERTIME{"format"}%
Formatted server time. Example: %SERVERTIME{"$hou:$min"}% is 15:52
%HTTP_HOST%
HTTP_HOST environment variable, is freenetproject.org
%REMOTE_ADDR%
REMOTE_ADDR environment variable, is 195.110.99.218
%REMOTE_PORT%
REMOTE_PORT environment variable, is 59905
%REMOTE_USER%
REMOTE_USER environment variable, is
%INCLUDE{"page" ...}%
Server side include to IncludeTopicsAndWebPages?. Parameters are page name, and an optional pattern="(reg-exp)". The page name is:
"SomeTopic"
The name of a topic located in the current web, i.e. %INCLUDE{"WebNotify"}%
"Web.Topic"
A topic in another web, i.e. %INCLUDE{"TWiki.TWikiWebsTable"}%
"http://..."
A full qualified URL, i.e. %INCLUDE{"http://twiki.org/"}%
%STARTINCLUDE%
If present in included topic, start to include text from this location up to the end, or up to the location of the %STOPINCLUDE% variable. A normal view of the topic shows everyting exept the %STARTINCLUDE% variable itself.
%STOPINCLUDE%
If present in included topic, stop to include text at this location and ignore the remaining text. A normal view of the topic shows everyting exept the %STOPINCLUDE% variable itself.
%TOC%
Table of Contents of current topic.
%TOC{"SomeTopic" ...}%
Table of Contents. Shows a TOC that is generated automatically based on headings of a topic. Headings in WikiSyntax? ("---++ text") and HTML ("<h2>text<h2>") are taken into account. (But not "<H2>text</H2>", which can be used to exclude a heading from the TOC.) Parameters are topic name, web and depth:
What sort of search is required? "topicmoved" if search for a topic that may have been moved "parent" if searcing for topics that have a specific parent i.e. its children
required
web="%WEB%"
Wiki web to search: A web, a list of webs separated by whitespace, or all webs.
required
topic="%TOPIC%"
The topic the search relates to
required
title="Title"
Text the is pre-pended to any search results
required
Example: %METASEARCH{type="topicmoved" web="%WEB%" topic="%TOPIC%" title="This topic used to exist and was moved to: "}%, you may want to use this in WebTopicViewTemplate? and WebTopicNonWikiTemplate? %METASEARCH{type="parent" web="%WEB%" topic="%TOPIC%" title="Children: "}%
%VAR{"NAME" web="Web"}%
Get a preference value from a web other then the current one. Example: To get %WEBBGCOLOR% of the Main web write %VAR{"WEBBGCOLOR" web="Main"}%, is #FFFFC0
[1] Note: The search form uses identical names for input fields.
[2] Note: A web can be excluded from a web="all" search if you define a NOSEARCHALL=on variable in its WebPreferences.
Additional variables are defined in the preferences ( site-level ( SL ) in TWikiPreferences, web-level ( WL ) in WebPreferences of each web, and user level ( UL ) preferences in individual user topics):
Variable:
Level:
What:
%WIKIWEBMASTER%
SL
Webmaster email address (sender of email notifications) , is ian@freenetproject.org
%WIKIWEBLIST%
SL
List of TWiki webs (in upper right corner of topics)
%WEBTOPICLIST%
WL
Common links of web (second line of topics)
%WEBCOPYRIGHT%
SL , WL
Copyright notice (bottom right corner of topics)
%WEBBGCOLOR%
WL
Background color of web
%NOSEARCHALL%
WL
Exclude web from a web="all" search (set variable to on for hidden webs)
%NEWTOPICBGCOLOR%
SL , UL
Background color of non existing topic. ( UL needs authentication for topic views )
%NEWTOPICFONTCOLOR%
SL , UL
Font color of non existing topic. ( UL needs authentication for topic views )
%EDITBOXWIDTH%
SL , UL
Horizontal size of edit box, is 70
%EDITBOXHEIGHT%
SL , UL
Vertical size of edit box, is 17
%RELEASEEDITLOCKCHECKBOX%
SL , UL
Default state of the "Release edit lock" (UnlockTopic?) check box in preview. Checkbox is initially checked if Set RELEASEEDITLOCKCHECKBOX = checked="checked", or unchecked if empty. If checked, make sure to click on Edit to do more changes; do not go back in your browser to the edit page, or you risk that someone else will edit the topic at the same time! Value is: checked
%DONTNOTIFYCHECKBOX%
SL , UL
Default state of the "Minor Changes, Don't Notify" (DontNotify?) check box in preview. Check box is initially checked if Set DONTNOTIFYCHECKBOX = checked="checked", or unchecked if empty. Value is:
%ATTACHLINKBOX%
SL , UL
Default state of the link check box in the attach file page. Check box is initially checked if value is set to CHECKED , unchecked if empty. If checked, a link is created to the attached file at the end of the topic. Value is:
%HTTP_EQUIV_ON_VIEW%
SL
http-equiv meta tags for view, rdiff, attach, search* scripts.
%HTTP_EQUIV_ON_EDIT%
SL , UL
http-equiv meta tags for edit script.
%HTTP_EQUIV_ON_PREVIEW%
SL , UL
http-equiv meta tags for preview script.
%DENYWEBCHANGE%
WL
List of users and groups who are not allowed to change topics in the TWiki web. (More in TWikiAccessControl?)
%ALLOWWEBCHANGE%
WL
List of users and groups who are allowed to change topics in the TWiki web. (More in TWikiAccessControl?)
%DENYTOPICCHANGE%
(any topic)
List of users and groups who are not allowed to change the current topic. (More in TWikiAccessControl?)
%ALLOWTOPICCHANGE%
(any topic)
List of users and groups who are allowed to change the current topic. (More in TWikiAccessControl?)
%DENYWEBRENAME%
WL
List of users and groups who are not allowed to rename topics in the TWiki web. (More in TWikiAccessControl?)
%ALLOWWEBRENAME%
WL
List of users and groups who are allowed to rename topics in the TWiki web. (More in TWikiAccessControl?)
%DENYTOPICRENAME%
(any topic)
List of users and groups who are not allowed to rename the current topic. (More in TWikiAccessControl?)
%ALLOWTOPICRENAME%
(any topic)
List of users and groups who are allowed to rename the current topic. (More in TWikiAccessControl?)
%FINALPREFERENCES%
SL , WL
List of preferences that are not allowed to be overridden by next level preferences
The syntax for Preferences variables is the same anywhere in TWiki. In Edit mode, from the start of a new line: [6 spaces] * [space] Set [space] VARIABLENAME [space] = [value] Example:
You can add your own preference variables for an entire site, a single web, or a single topic, using the standard syntax. Whatever you include in your variable will be expanded on display, and treated exactly as if it had been written out. So you can place formatted text, page links, image paths.
Example: Create a custom logo variable
To place a logo anywhere in a web by typing %MYLOGO%, simply define the variable on the web's WebPreferences page. You also have to upload logo.gif - this can be done by attaching a file to LogoTopic (any topic name you choose):
Set MYLOGO = %PUBURL%/%MAINWEB%/LogoTopic/logo.gif
This website is based on TWiki, and is designed to allow ease of editing. Anyone can edit the public area of this site - using nothing more then their web browser.
If you would like to edit the public area of the website, please register here.
FCPTools provide the same functionality as Freeweb, but without the GUI. Working platforms include MS-Windows, Linux, BSD, and perhaps others. An ANSI-C based Client Lib (ezFCPlib) is also included for developers to aid in writing Freenet clients.
FMB is an excellent Usenet-like tool which allows secure messages to be exchanged via Freenet, it is somewhat similar to Frost, but employs a more sophisticated "outbox" based approach.
FreeNews is a gateway between a NNTP and Freenet news service, based on the Frost TOF boards with some extentions. It allows you to use your favorite news reader to access TOF bulletins.
Liberator is the old-school unix command-line client designed to be easy to script (or cron). It's written in perl so it should be as portable as needed.
If you want to develop a tool or client for Freenet please publish your idea here. There you can also find a list of projects related to Freenet in their early stages of development.
Note: You should automatically have been directed to the correct translation in your language if it exists, and if your web browser is configured correctly.
If you are interested in translating this site to a language not listed here, please read this useful information amd email web@freenetproject.org .
Bulgarian
- Status: In development
- Translator: Zlatin Balevsky
Chinese (China)
- Status: In development
- Translator: Autrijus Tang
Chinese (Taiwan)
- Status: In development
- Translator: Autrijus Tang, Whiteg Weng
Dutch
- Status: Up to date
- Translator: Jaap Bouwsma
Finnish
- Status: Up to date
- Translator: Jukka Holappa
French
- Status: Up to date
- Translator: Benoit Laniel
German
- Status: Up to date
- Translator: Peter Kerner
Hungarian
- Status: In development
- Translator: Noll Janos
Italian
- Status: Up to date
- Translators: Marco A. Calamari, Gianni Bianchini, Carlo Borelli, Djuly, Ergos, Chiara Esposito, Andrea Glorioso, Khc, Giulio Leben, Scana, Marco Vicario
Japanese
- Status: Up to date
- Translator: Kikuo Goto
Portugese
- Status: In development
- Translator: Mikhail Miguel
Russian
- Status: In development
- Translator: Leonid Chukhovsky
Spanish
- Status: In development
- Translator: Ben Curry
List of TWiki users Please take the time and add yourself to the list. To do that fill out the form in TWIKIWEB .TWikiRegistration. This will create an account for ...
Name: Eric Butler Email: caliskunk1@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Alain BEDOTTO Email: alain.bedotto@wanadoo.fr Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Davor Sedic Email: dsedic@inet.hr Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: chwarzy one Email: gromit.fuss@wanadoo.fr Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: lakhdar MOKRANE Email: lmokrane@noos.fr Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: El an Email: tre@aol.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 Vertical ...
Name: john smith Email: jan4unow@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: rustys lounge Email: rustyslounge@yahoo.com Comment: wher you work Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box ...
Name: Frans Zoeteman Email: Zoeteman30@zonnet.nl Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: troy tumbleson Email: doretat@ckt.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: mikSim Email: highlife.nl@caramail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
"I worry about my child and the Internet all the time, even though she's too young to have logged on yet. Here's what I worry about. I worry that 10 or 15 years from ...
Some Screenshots of Freenet in Action The Freedom Engine A popular Freesite which indexes other Freesites in Freenet. Freenet Message Board A Java application which ...
Name: Silvio Erpicaro Email: silvio2050@yahoo.it Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Roberto Gobbo Email: rgobbo@netwise.it Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Michael Hintz Email: mhintz@freeshell.org Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Alberot Hill Email: ahill@adinet.com.uy Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Andrea Mayer Email: netwatch.hexe@aon.at Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: ty forsman Email: tyme 75@yahoo.com Comment: after all this shit to down load it better be worth it Personal Preferences (details in TWIKIWEB .TWikiVariables ...
Name: Guido Brugnara Email: gdo@leader.it Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: jeff harper Email: quietman125@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Pablo Durante Email: BYTE@TELNOR.NET Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: dave dave Email: mydogsnameistori@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: ras ras Email: www.mydogsnameistori@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: GiuseppeRugiano Email: giuseppe.rugiano@libero.it Comment: fantastic Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit ...
Name: xi jingjing Email: xijingjing@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Douglas Fraser Email: freenet@idmf.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: PeteSoden Email: pete@daware.com Comment: Just some stuff really :) Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit ...
Name: Steve Hellin Email: steve hellin@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Paul Daniels Email: pauldaniels@subdimension.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Andrew Rodland Email: arodland@noln.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
State of Freenet #4 As always, things have been moving rapidly in Freenet development. Over the past few weeks there has been the usual gaggle of bug-fixes, the datastore ...
Name: Jean-Baptiste Erceau Email: erceau@wanadoo.fr Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: BillSmooth Email: naumachie@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: jon morris Email: jmor@mail.clis.com Comment: i want to download movies and music... thanks Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal ...
Name: Anthony Fabian Email: pjmc@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: serdenti federico Email: serdenti@libero.it Comment: come funziona questo sistema...? Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal ...
Name: Garfield Cat Email: gfcat2k@yahoo.com Comment: OSSS Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Ramon Luque Email: www.RamonLathome@aol.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Alexander Zelenkoff Email: alexander zelenkoff@pochtamt.ru Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit ...
Name: My Peer Email: jlds@etang.com Comment: !good,all will good Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set ...
Name: Jeremy Welu Email: welu13@insightbb.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Third Party Tools A variety of people have written some excellent tools and clients for use with Freenet. Freenet Publishing & Retrieval Tools http://freeweb.sf.net ...
Name: Car Mee Email: carmee@space.xs4all.nl Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Rafael Perez Email: quetza2@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Web Bouthi Email: webbouthi@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Daniel Dumenil Email: daniel.76@wanadoo.fr Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: K. Tsakaloglou Email: tsakf@tee.gr Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
"I worry about my child and the Internet all the time, even though she's too young to have logged on yet. Here's what I worry about. I worry that 10 or 15 years from now, she will come to me and say 'Daddy, where were you when they took freedom of the press away from the Internet?'"
--Mike Godwin, Electronic Frontier Foundation
In an effort to resolve a recent regression in network performance caused by our attempt to improve load-balancing, today's snapshot is a mandatory upgrade. This means that nodes downloaded from now on will not talk to older nodes. If you downloaded a copy of Freenet before today please upgrade immediately. We try to keep mandatory upgrades to a mimimum but they are occasionally necessary.
Freenet is free software designed to ensure true freedom of communication over the Internet. It allows anybody to publish and read information with complete anonymity. Nobody controls Freenet, not even its creators, meaning that the system is not vulnerable to manipulation or shutdown.
Freenet is also efficient in how it deals with information, adaptively replicating content in response to demand. We have and continue to pioneer innovative new ideas such as the application of emergent behavior to computer communication, and public-key cryptography to creating secure namespaces. For more information please read this paper on the Freenet architecture.
Name: Aaron Burchell Email: aburchel@fit Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: Ab7 Cd Email: ab7cd@juno.com Comment: could not donate on your websie. I will send a check Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal ...
Name: Ada M Email: adam@nocat.net Comment: 123 Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 Vertical ...
Name: Adam Ritter Email: adamsoft@freemail.hu Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Adam Sutton Email: kungfusing@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: adriano ilmiocane Email: adriano@tin.it Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Afree Xanth Email: afree87@yahoo.com Comment: I die, and my computer shuts down, destroying a Freenet hub. A user at a government agency thinks he's clicking ...
Name: Adam Langley Email: freenet.twiki@imperialviolet.org Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set ...
Name: Adrian Hynes Email: aido123@budweiser.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: akis alexis Email: akisalexis@freetone.gr Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: akyra stephane Email: akyra.fr@infonie.fr Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: al clarke Email: niteranger7@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: al saiz Email: alsaiz@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: Alain BEDOTTO Email: alain.bedotto@wanadoo.fr Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Alberot Hill Email: ahill@adinet.com.uy Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Alberto Adrián Schiano Email: alberto@redesdelsur.com Comment: I feel this is something great: Let's find out! (good luck, my precious) Personal Preferences ...
Name: Alessandro Adamo Email: alessandro.adamo.freenet Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Alessandro B. Email: alex@bicnet.it Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: Alex Cruise Email: alex-freenet@cluonflux.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Alex Saltanov Email: asdgray@chat.ru Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Alexander Engel Email: alexanderengel@mac.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Alexander Zelenkoff Email: alexander zelenkoff@pochtamt.ru Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit ...
Name: Alexandr Kovalenko Email: Aspid Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 Vertical ...
Name: alexandre toombs Email: alexestmondieu@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set ...
Name: ZhongLun Email: sparkyspace@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: A. Randel Email: AmaLeo67@yahoo.ca Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: amed choukroun Email: trisomie26@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: AnaI P Email: aipor@us.es Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 Vertical ...
Name: anca popa Email: X tasyanca@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Anders Nilsson Email: anders.bredal@swipnet.se Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Andrea Mayer Email: netwatch.hexe@aon.at Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Andrea Monni Email: andreamonni@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: andreas normann Email: andreas.normann@t-online.de Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set ...
Name: Andrew Rodland Email: arodland@noln.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: angel d. Email: angeld@xasa.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 Vertical ...
Name: antsoden Email: pete@daware.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 Vertical ...
Name: Anthony Fabian Email: pjmc@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: archie goines Email: arch33neg@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: arch mcalister Email: amcalister@centertech.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Freenet Architecture These pages are intended to give a top-down overview of Glossary.Fred Fred 's architecture. Before reading this you should become familiar with ...
Name: Are Årseth Email: elrond@ctemp.dhs.org Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Are Årseth Email: elrond@ctemp.dhs.org Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Arn Burboeck Email: arnstyr@gmx.at Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: ArtemisiaGentileschi Email: bisartemisia@tiscali.it Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set ...
Name: Atanu Nath Email: atanu70@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: Hans-Werner Aull Email: Hawea@efinum.de Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: austin bailey Email: oggybailey@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: bat mann Email: batmann@eudoramail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: BeckyHancock Email: bella@avci.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: Ben Clapp Email: bclapp@brooksschool.org Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Ben Curry Email: privateben@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: BenjaminCummins Email: bcummins22@home.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: BenjaminDescamps Email: benjamindescamps@hotmail.com Comment: I study as a translator from English and Spanish to Dutch (I'm in the last of four years study ...
Name: Benoit Arseneault Email: barsena@globetrotter.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set ...
Name: Benoit Laniel Email: nels@pgroupe.net Comment: French coordinator Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box ...
Name: Bert Shuler Email: BertShuler@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Bharat Madan Email: bbm@ee.duke.edu Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: jonh Email: biggles@webmail.co.za Comment: lets see what this shit can find Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text ...
Name: Big Mike Quinlan Email: mquinlan4@cogeco.ca Comment: music/keep the lines open Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of ...
Name: Bill Ring Email: q159@hotmail Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 Vertical ...
Name: BillSmooth Email: naumachie@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Billy Idlrox Email: pixii182@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Bingo Bongo Email: giuseppe@lycosmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Laura Dauser Email: BizzyBee33@aol.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: BjornT Email: therunyan@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: Blake Hargis Email: blake hargis@yahoo.com Comment: English German translator Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of ...
Name: Bob Kondos Email: kondos@asis.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: Bob Olfenheimer Email: ebin111@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Brave Warria Email: macchina@kyuzz.org Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: brendan kelly Email: themick90068@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Brittany Crowe Email: fastkitten2@aol.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Freenet Reference Daemon Documentation This manual was automatically generated by the manual switch (see below) on Jan 23, 2002 9:56:47 AM. Command line switches: ...
Name: caiwen wang Email: cwang10535@aol.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Car Mee Email: carmee@space.xs4all.nl Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Carl Dutli Email: brc-tvproductions@span.ch Comment: TV Productions, Editing Final Cut Pro SDI With out compression Tel 0041792064343 Personal Preferences ...
Name: Carl Winberg Email: carl.winberg@telia.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: carlos aguilar Email: aguila47@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: carlos corredoura Email: corredourac@netscape.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set ...
Name: CarmenF Email: BUSTERXRX@cs.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 Vertical ...
Name: cedric lacrambe Email: cedric.lacrambe@visitmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set ...
Name: cedric macia Email: famillemacia@aol.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Christopher Sigmund Email: ATM666@SMS.at Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Charles Kylis Email: sylkione@webcosolutions.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: charlie krienke Email: weirdeyedrummer@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set ...
Name: ChazLopez Email: romieyo2002@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Chris Carlin Email: volkris@tamu.edu Comment: Hmmmm Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Chris Pollard Email: smallnfirm@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: chwarzy one Email: gromit.fuss@wanadoo.fr Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Cinzio Gerbi Email: go@go Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 Vertical ...
Name: Claus Färber Email: claus@faerber.muc.de Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: FlorenceYoud Email: fyoud@indianaconnect.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: cotilla cotilla Email: euncotilla@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: curtis slater Email: slaterock@shaw.ca Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: cyclops cyborg Email: cybertronix@operamail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Kalevi Anders Email: nerv secretservice@yahoo.de Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: da 1uth Email: blah@blubb.net Comment: bla! Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: DamienParry Email: damienparry@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: dan parkinson Email: moonlight nyx@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Daniel Dumenil Email: daniel.76@wanadoo.fr Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Daniel Lefebvre Email: dlefebvre@yahoo.fr Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Daniel Morrigan Email: dmorrigan@need2host.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Daniel Suliman Email: nyolot@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Danilo De Benedetto Email: debeneda@tin.it Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: danilo properzi Email: danilopro@mercurio.it Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Darren Williams Email: darrenwilliams@houston.rr.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set ...
Name: Datinh O Email: shaihulud@katamail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: dave dave Email: mydogsnameistori@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: dave pinczkowski Email: Dave Pin@msn.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: David Allen Email: mda@idatar.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: David Chapman Email: DavidChapman@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: David Daniels Email: DDNC@mail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: david griffen Email: dbg4412171@aol.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: david huddleston Email: ddavid1963@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: david moreno meneses Email: holanenaaaa@hotmail.com Comment: gracias Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit ...
Name: David Navarro Fernandez Email: dnavarrof@MailandNews.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box ...
Name: David Roche Email: rochedav@msu.edu Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: Davor Sedic Email: dsedic@inet.hr Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: De meurichy Jacques Email: jacques.demeurichy@wanadoo.be Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box ...
Name: Debbie Trevithick Email: de2be1020@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: derek gill Email: derekgill@eircom.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Derek Gillis Email: gilldog@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: derek iott Email: diott@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: Devin Fisher Email: Devin.Fisher@colorado.edu Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Diana Echlin Email: dechlin@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Dick Williams Email: DJ.Bling@verizon.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: donald carver Email: psyspy001@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Donald Duck Email: kohinoor@swissinfo.org Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Donations We have set-up a non-profit corporation to advance the interests of the Freenet project. The mission statement of Freenet Project Inc is as follows: The ...
Name: Douglas Fraser Email: freenet@idmf.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Download Freenet Please download and test a snapshot of the current development version. The next version 0.5 is expected to be completed soon check back at this ...
Name: Dr. Static Email: dr.static@telus.net Comment: En AnArche En Ho Logos! Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit ...
Name: Dujruthai Email: dujruthai@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: rob peters Email: robsasha11@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Eamonn O'Brien-Strain Email: eob@hpl.hp.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: eblis Null Email: eblis999@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: EdDimmer Email: dimmer@msn.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 Vertical ...
Name: Ed Onken Email: edonken@midwest.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: Ed Thompson Email: kingogofbashan@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: eddy wullems Email: oldversion@kabelfoon.nl Comment: go download Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box ...
Name: edi b Email: e badurina@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: El an Email: tre@aol.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 Vertical ...
Glossary: Emergent Behavior An emergent behavior is a behavior exhibited by a system consisting of a large number of simple and similar (or identical) components ...
Name: Eric Anholt Email: eanholt@gladstone.uoregon.edu Comment: I'm pretty newbish freenet-wise, but I am interested in helping document how to use freenet with FreeBSD ...
Name: Eric Butler Email: caliskunk1@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Eric Norige Email: thelema@mercury.truman.edu Comment: use liber2.pl! Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit ...
Name: Erica Darnell Email: bling812001@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Erich Pilgerstorfer Email: pi. Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 Vertical ...
Name: Erin Inbody Email: einbody21281@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Erwin Kessler Email: kessler@ioz.ch Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: EschweilerFrank Email: stuffz@tm1.at Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Frequently Asked Questions Important notice: These answers are provided by a variety of people involved in the Freenet project, however they should not be taken as ...
What are the FCPTools? The most useful component of the FCPTools is ezFCPlib, a portable ANSI-C based Freenet Client Library. It's been written to make writing Freenet ...
Name: Fabio Fricano Email: info@fabiofricano.it Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
FairShare Rewarding artists without Copyright Ian Clarke 2nd January 2002 Introduction With advances in communication technology, such as the Internet, and systems ...
Name: Federica Teodori Email: eowin@libero.it Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Fekete Lajos Email: fekete.lajos@wanadoo.be Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Fish Fish Email: fish@bovine.artificial-stupidity.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: ...
Name: foiza Mohammed Email: Foiza22@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: forty two Email: udva28y001@sneakemail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: francesco & sammartino Email: domesam@tin.it Comment: hi at all! Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box ...
Name: Frank Eickholt Email: frank@eickholt.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Frans Zoeteman Email: Zoeteman30@zonnet.nl Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Fred Feuerstein Email: 007fragger@gmx.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Fred Melindy Email: fmelindy@roadrunner.nf.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Fred Smith Email: windwalker777@earthlink.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Downloading the Freenet source via CVS You will need a copy of http://www.cvshome.org/ CVS , this comes as standard with most Unix and Linux based operating systems ...
Abstract The Main.FreenetClientProtocol (FCP) is designed to abstract the basics of Freenet so that client developers do not have to track the main Freenet protocol ...
Name: froc here Email: shwardzzy@aol.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: Kenji Miyagi Email: valkyrie@plum.freemail.ne.jp Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: gabisu no ken Email: gabisu@lycos.fr Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Gabriel Leiner Email: gabe@netjunk.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Garfield Cat Email: gfcat2k@yahoo.com Comment: OSSS Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Gearoid Coughlan Email: gearoid.coughlan@kapookigames.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box ...
Name: Georg Kadavy Email: Dentrobad@aol.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: george duck Email: gduck83232@aol.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: george thomas Email: wwwoodbutcher62@aol.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: george walker Email: ggwalkerr1@home.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Gerard Braad Email: g braad@survion.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Cyril So Email: cyril@avarcorp.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: gi nadir Email: rinasidhe@hotmail.com Comment: no comment Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: giles brunet Email: oslo1@caramail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Ging UK Email: None@none.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 Vertical ...
Name: Giovanni Lacava Email: gianni73@iol.it Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Giovanni Riccardi Email: giovanni@composizioni.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set ...
Name: GiuseppeRugiano Email: giuseppe.rugiano@libero.it Comment: fantastic Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit ...
Name: Gnom Jas Email: Gnomjas@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: Gnovo S Email: mason@greenwitch.com Comment: Cats taste good? Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set ...
Name: gomes dos santos Email: gomes@skynet .be Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: GoranFilipovic Email: gripsies@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Goran Zivec Email: goranzivec@rocketmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Graham Olk Email: olk@charter.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: Graham Smith Email: smithg853@aol.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Greg Andrews Email: gregandrews@mac.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Greg Welsh Email: hammer@mail.mdt.net.au Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Gregory Piazza Email: piazzag@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Griffe Luc Email: gblm@wanadoo.fr Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: Guido Brugnara Email: gdo@leader.it Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: Gunther Schmidt Email: gunther.schmidt@web.de Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Hani Kristina Email: hanikristina@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: harry streetman Email: itsjusme@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Hassan Alief Email: mhalief@msn.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: hein maier Email: timber3@t-online.de Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: HARLEY SMITH Email: HARLEYS@SENET.COM.AU Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Hubert smulders Email: hubertsmulders@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set ...
Freenet: A Distributed Anonymous Information Storage and Retrieval System Ian Clarke Uprizer, Inc. 1007 Montana Ave., #323 Santa Monica, CA 90403 USA ian@octayne ...
Name: ignacio carranza Email: skimap245@home.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Ian Boothroyd Email: thehunterd@vampirehunter.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set ...
Name: Ian Clarke Email: ian@freenetproject.org Comment: Project Coordinator Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit ...
Name: Ian Sidle Email: macmouse4@attbi.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Ikoman domingo Email: ikomann@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: IngoHanschur Email: IHanschur@aol.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Ingo Ralf Blum Email: ingoralfblum@gmx.de Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Irawan Setiawan Email: khaine@viletech.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Ivan Bentzen Email: ivanbent@worldonline.dk Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: ivan bimkovich Email: aelita@teleline.es Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Ivan Ivanov Email: ivangiavnov@abv.bg Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Ivan Lee Email: ivanlee168@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Ivan Oliveira Email: icalcan@dglnet.com.br Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: John Noisy Hawk Email: cybliminal@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: jakob roosi Email: 123123@popit.dk Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: James Gaskell Email: James.Gaskell@dunelm.org.uk Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: james graigner Email: graingerjc@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: james mcquillan Email: jmcq@iol.ie Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: James Tzeng Email: cannabis@pchome.com.tw Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Janie Mehew Email: janie@freenetproject.org Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Jano' van Deventer Email: jano2you@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Jared Harrison Email: gqtaz@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Jason Duerstock Email: jason-freenet@cluephone.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set ...
Name: Jason Rohrer Email: rohrer@cse.ucsc.edu Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Kurt Zimmerman Email: Jbele84@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Jay Oliveri Email: ilnero@gmx.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: Jayson Smith Email: jaybird@iglou.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: johnferry Email: johnferry44@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: JeSuisDePassage Email: JeSuisDePassage@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Jean-Baptiste Erceau Email: erceau@wanadoo.fr Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Jeff Darcy Email: freenet spam@platypus.ro Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: jeff harper Email: quietman125@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Jeffrey Mackey Email: wrrangler Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 Vertical ...
Name: jenn todd Email: mefjbt1328@aol.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: Jens Bergendahl Email: j-b@swipnet.se Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Jens O. M. Email: jensom@mail.nu Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 Vertical ...
Name: Jeremy Welu Email: welu13@insightbb.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Jeroen Deken Email: jdeken@medialab.nl Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: jesus angel Email: escuelatango@mixmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Jim Hunziker Email: landtuna@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Jim Weslock Email: spottedwolf01 Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 Vertical ...
Name: Jo Black Email: ash99@gmx.de Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 Vertical ...
Name: joe Berk Email: jogys@nexgo.de Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 Vertical ...
Name: Joe Blo Email: rmarcum5@home.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 Vertical ...
Name: Joe Coulter Email: zepheron@netzero.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: joe dee Email: thermal1@aol.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 Vertical ...
Name: joel dobson Email: joeldobson836@bluelight.com Comment: none Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set ...
Name: Joerg Ebeling Email: jebs@shbe.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: John Barnes Email: hosque@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: john osborne Email: captjao@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: John Restaurant Email: johnrestaurant@wanadoo.be Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: John Richardson Email: RichardsonJ@tce.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: john smith Email: jan4unow@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: john telfer Email: jim2648 Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 Vertical ...
Name: john wolf Email: jyawgdir@aol.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: Janos Noll Email: johnzero-freenetwiki@johnzero.hu Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set ...
Name: Johnny Crow Email: johnny aio2@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: jon morris Email: jmor@mail.clis.com Comment: i want to download movies and music... thanks Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal ...
Name: Jonathan Bringhurst Email: fintler@msec.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: JorgeMuldoon Email: Dawg05@aol.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: Jose Barbosa Email: jbarbsoa@fugu.ist.utl.pt Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Joseph Caneco Email: Caneco1310@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Joshua Abbott Email: jabbott@newpentacle.zzn.com Comment: NARF! Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box ...
Name: Joshua Smith Email: subjanus23@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Jukka Holappa Email: jukkaho@mail.student.oulu.fi Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set ...
Name: Justin Weeks Email: x@hackersinparadise.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Kah Less Email: kahless@st-ac.de Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 Vertical ...
Name: Kai Kammerer Email: kaikammerer@gmx.de Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: kai oksa Email: sya844m@tninet.se Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: Kamal Sulaiman Email: ksulaiman 100@hotmail Comment: Thanks Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set ...
Name: Karsten Schipper Email: tobimoos@gmx.de Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Ken Follett Email: Ken Follett@Infinito.it Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Ken Greer Email: klgreer@hyp.com.au Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: Kenneth R. Melvin Email: kenpamme@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: KennyLad Email: xavierkenny@oreka.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: ker houat Email: kerhouat@noos.fr Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: KevinAtkinson Email: kevin.freenet@atkinson.dhs.org Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set ...
Name: khan khan Email: khan mf2000@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Kikuo Goto Email: kkgoto@yahoo.co.jp Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Krissy Pearl Email: coolk22@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: LETRA Email: LETRA@inicia.es Comment: LENGUAJE: SPANISH Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Milo Polte Email: mp98@cornell.edu Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: lakhdar MOKRANE Email: lmokrane@noos.fr Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: LeeD Email: lcd150@stargate.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 Vertical ...
Name: Lee Girard Email: leegirard22@aol.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: legent guil Email: g legent@hotmail.com Comment: free mot de passe petitlapin ! attaché ... Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal ...
Name: Lemuel Gulliver Email: gulliver@users.sourceforge.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: ...
Name: Leonardo Giacomelli Email: leonardo@firenze.linux.it Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set ...
Name: Leonid Chukhovsky Email: chukhovsky@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Leopoldo Ghielmetti Email: ENQAHIUGSPUT@spammotel.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: ...
Name: leuk he Email: test2201c@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Linda Murphy Email: Mothbulbs@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Linda Roberts Email: sybergrrl@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Note: We constantly get requests of people who want to become unsubscribed. YOU have to do that yourself! Just click on the www link provided at the bottom of every ...
Here would stand the information about the London office: Address: Phone: Fax: List of employees at LondonOffice. Related topic: OfficeLocations, WIKIUSERSTOPIC
Name: Lotty Douglas Email: lrdoug Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 Vertical ...
Name: Louis Wynne Email: louiswynne@yahoo.co.uk Comment: i like pigs Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: ...
Name: LpWilde Email: LWILDEWORK@AOL.COM Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: Luca Martinetti Email: lucamartinetti@phatsoft.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set ...
Name: Lucian Ion Email: l ion@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: Luke Reeves Email: luke@submail.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: Chris Hanson Email: macbeth@gmx.co.uk Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Malakai Q. Adams Email: Malakai1911@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Marco Calamari Email: marcoc@dada.it Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Marco Vicario Email: lion@open4.it Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: marcos m Email: th.ringeval@libertysurf.fr Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Mariano Danicano Email: hitop@edsamail.com.ph Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: mark cullen Email: spike328@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Mark J Roberts Email: mjr@znex.org Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: Mark 75lon Email: Marky75lon@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Mark Sanchez Email: skirr@msn.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: mark satterfield Email: mhsatterfield@tds.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Mark Wagner Email: wags2riches@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: martin joan Email: HERVEM54@HOTMAIL.COM Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Matt Ebner Email: matthias.ebner@gmx.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Matt Puchowicz Email: Lobstert182@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: matteo dominoni Email: verby@tiscalinet.it Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Matthias Kuehnle Email: kuehnle@web.de Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Matthieu Roy Email: mroy@irisa.fr Comment: français/french Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set ...
Name: mauro pecollo Email: pecollo2@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: mazza kanna Email: bekkylea@bigpond Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: Md Dimond Email: markymark1232@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Meghan Clark Email: MegRedVkitty@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Mel Fuhrman Email: Roxas3@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: Meta Corp Email: hkerth@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: Mi Tour Email: posi 99 99@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: Michael Drueing Email: michael@drueing.de Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Michael Hintz Email: mhintz@freeshell.org Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Michael lickley Email: cyclops@tc3net.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Michael Terry Email: msterry@student.umass.edu Comment: I'm an undergraduate CS student at the University of Massachusetts Amherst. Personal Preferences (details ...
Name: Micro-Genius Email: Acerprossecor@msn.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: microdados system Email: ppbrasil@yahoo.com Comment: site experimental Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit ...
Name: mikSim Email: highlife.nl@caramail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Mikael Gustavsson Email: spike mf@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: mike dotd Email: mikedotd@nexthop.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Mike Healey Email: mikeh@freenet.co.uk Comment: I tried using your site to publish a web site but gave up after 2 hours. Is this site for computer boffins? ...
Name: Mike Linksvayer Email: ml@gondwanaland.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Mike Morris Email: mmjj@abcs.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 Vertical ...
Name: Mikhail Miguel Email: mikhail@underpop.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: mo wang Email: mowang@web.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 Vertical ...
Name: Mohammed Shah Email: shades786fj@hotmail.com Comment: I would only like to register if it dose not include any monthly rental, and it is totally free Personal ...
Name: molly bortolotti Email: ebortolotti@libero.it Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Moo Cow Email: Malakai1911@yahoo.com Comment: None Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: muddy none Email: muddz420@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Murray Henson Email: miscnews@exocet-industries.cx Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set ...
Name: Mark Zaiser Email: mark@markzee.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: Me Email: Livyone2000@yahoo.co.uk Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: My Peer Email: jlds@etang.com Comment: !good,all will good Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set ...
Using Freenet from behind a NAT or Firewall To work correctly, Freenet requires that other Freenet nodes can establish TCP connections with your node, typically a ...
Name: Naived Merchant Email: naived m@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Nayden Naydenov Email: nayd@abv.bg Comment: The Freedom is choice! Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box ...
Name: New User Email: ian@freenetproject.org Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Nick Armstrong Email: nickyarm72@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: nick nick Email: dfer266@aol.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 Vertical ...
Name: Nick Urban Email: nurban@calpoly.edu Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Nico Galoppo Email: scratch@ulyssis.org Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: nicolas szymanski Email: nicszymnsk@aol.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: nicole irick Email: nicoleirick@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Nobody Group Set GROUP Set ALLOWTOPICCHANGE TWikiAdminGroup Used to prevent dangerous actions e.g. renaming TWIKIWEB .TWikiPreferences. Related topics: WIKIUSERSTOPIC ...
Name: norbert Email: norbert.delmotte@free.fr Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Noway Jose Email: v eus@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
The OfficeLocations topic has a list of all your offices. TheInternet (This is an example of corporate intranet use and is for demonstration purposes only: TWIKIWEB ...
Name: Oleg Fedorov Email: oleg.fedorov@tvt-info.ch Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Omar Karyem Ravenhurst Email: omar@eris.org Comment: wikki is very annoying Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text ...
Name: Oscar Migliorati Email: oscarmigliorati@libero.it Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set ...
Name: Otis Wildflower Email: otis@unixslave.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Pablo Durante Email: BYTE@TELNOR.NET Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Panayotis Zografakis Email: panayotisz@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set ...
Name: Paolo Margari Email: p.margari@inwind.it Comment: hello world! Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: ...
Name: PaulBley Email: p bley@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: Paul Daniels Email: pauldaniels@subdimension.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Paul Ellison Email: philo@mmcable.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Pedro Campos Email: pmcampos@telepac.pt Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Pedro Rivera Email: pedrorivera@mail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
The People Behind Freenet Note: This may be an incomplete list, a large number of people have contributed to the project. Contributors are responsible for adding ...
Name: PeteSoden Email: pete@daware.com Comment: Just some stuff really :) Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit ...
Name: Peter Brennen Email: pmbst23@pitt.edu Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Peter Brown Email: pbtub@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Peter Coombs Email: petengina@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: peter cristhmast Email: pdenat@tin.it Comment: I will see! Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set ...
Name: Peter Kerner Email: pekerner@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: peter schmidt Email: systhem@gmx.de Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: Peter Soden Email: pete@daware.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: philip hadley Email: jl004b2995@blueyonder.co.uk Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Philippe AGRIPNIDIS Email: protee@protee.fr Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
The Philosophy behind Freenet By Ian Clarke 1. A Disclaimer There are many reasons why people get involved in the Freenet Project. Some share the views outlined in ...
Name: Pipi Kortsok Email: CyMage@operamail.com Comment: The best Flemish translator u'll ever get ;p Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal ...
Name: Pradeep Aragonda Email: apdeeps@rediffmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Pratik Dhebri Email: pmdhebri@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Progress Report 12th January 2002 Over the past few months, most will have noticed a frustrating bug which caused the node to lock-up, and to fail to start until ...
Progress Report 19th January 2002 As of today Tavin thinks he has fixed the data corruption bug which was causing serious problems for Freenet since the introduction ...
Glossary: Public Key Cryptography Symmetric cryptography is the variety of cryptography most people are familiar with. There is a key which only the sender and receiver ...
Publicity Here you can find some links to articles and stories about Freenet. Some are more accurate than others but you can judge for yourself! If you are aware ...
How to Publish Websites in Freenet The basics Windows Users David McNab has written an excellent tool called http://freeweb.sf.net/ FreeWeb which you can use to insert ...
Name: Py Close Email: pyclose@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: Rafael Perez Email: quetza2@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: raffaello rebeggiani Email: raffaello@coraimola.it Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set ...
Name: Rah Rah Rah Email: wherestheanonimitygonenow@freenet.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box ...
Name: Ramon Luque Email: www.RamonLathome@aol.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: ras ras Email: www.mydogsnameistori@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Ratface Otool Email: bipolormaniac@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: ray reed Email: pegasus1959@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Red Herr Email: sasfds@dfads.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 Vertical ...
Name: r reed Email: winston700@aol.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 Vertical ...
Name: res idnt Email: residnt@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: Reuben Balik Email: cybrguyrsb@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Richard Brown Email: rjbrown@emirates.net.ae Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Richard Cochinos Email: polar-twiki@theory.org Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: rimbault pascale Email: cypr@wanadoo.fr Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Ritz Sky Email: a7591@yahoo.com Comment: LNO Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: rob crowley Email: robcrowley@eircom.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Rob Crundwell Email: rcrundwell3@operamail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Robert Bihlmeyer Email: robbe@orcus.priv.at Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Robert E. Lee Email: relee@stuart.iit.edu Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Robert Hensiak Email: rhensiak@att.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: robert morales Email: lblazer10500@yahoo.com Comment: blaze it Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: ...
Name: Robert Pies Email: robert.pies@web.de Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Roberto Gobbo Email: rgobbo@netwise.it Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Roberto Marquez Email: nrgmaster@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Rolf Hofmann Email: r.hofmann@smile.ch Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Ronald Mallory Email: mallory3@axelero.hu Comment: nope:) Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: ron t Email: vbuunk@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 Vertical ...
Name: Ron Thomas Email: RCTHO@AOL.COM Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 Vertical ...
Name: Ross Cates Email: supercarrot@blueyonder.co.uk Comment: i rule Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: ...
Name: Roy Barry Email: roy barry@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: russ hartley Email: russ5411@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: rustys lounge Email: rustyslounge@yahoo.com Comment: wher you work Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box ...
Name: ryan frazier Email: kidacro@archamedis.net Comment: keep it free! Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box ...
State of Freenet #4 As always, things have been moving rapidly in Freenet development. Over the past few weeks there has been the usual gaggle of bug-fixes, the datastore ...
Name: Saggi Reck Email: ARPL@gmx.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 Vertical ...
Name: Jed Normann Email: SaltDr@Hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: sam south Email: dagcity1@address.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: sam spade Email: imtheone@wowmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Here would stand the information about the San Jose office: Address: Phone: Fax: List of employees at SanJoseOffice. Related topic: OfficeLocations, WIKIUSERSTOPIC ...
Name: Scott Miller Email: scgmille@freenetproject.org Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Some Screenshots of Freenet in Action The Freedom Engine A popular Freesite which indexes other Freesites in Freenet. Freenet Message Board A Java application which ...
Name: Sean Palmer Email: sean@mysterylights.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Sebastian Gutweiler Email: newsletter@gutweiler.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set ...
Name: Sebastian Späth Email: spaetz@spaetz.de or Sebastian@SSpaeth.de Homepage: http://sspaeth.de Comment: Doctoral student of economics who happens to be the coordinator ...
Name: Sebastien Cayer Email: crazyworld2000ca@yahoo.ca Comment: right on! Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit ...
Name: SedeMikra Email: sedemikra@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Seedling Seedling Email: seedling@eudoramail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Seemore Legs Email: seemorelegs@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: serdenti federico Email: serdenti@libero.it Comment: come funziona questo sistema...? Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal ...
Name: Serenn Archangelsk Email: e-diote@ifrance.com Comment: Il faut bien des esprits acides pour contrebalancer les âmes basiques... Car si l'homme descend du singe ...
Name: Serge Wroclawski Email: swroclawski@earthling.net Comment: Let's make freenet not suck. Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal ...
Name: Shane O'Neill Email: helloinsane@eircom.net Comment: nuff said Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: ...
Name: Siegfried Kraus Email: skraus@bis.de Comment: no Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Silvio Erpicaro Email: silvio2050@yahoo.it Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: six ten Email: fairpoison@gmx.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: six xten Email: fair@gmx.de Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 Vertical ...
Name: sole man Email: tslico@netscape.net Comment: I find it very hard to find information right now and I was wondering if you could make it easier Personal Preferences ...
Name: sphere girl Email: spheregirl82@hotmail.com Comment: Very interesting Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit ...
State of Freenet 23rd February 2002 The last few months of Freenet development have largely been consumed by refining the current code-base, tracking down and fixing ...
Name: Stephan Niemz Email: st.n@gmx.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: Stephen Thomson Email: bloodyxqqx@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Steve Hellin Email: steve hellin@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: SteveJohnson Email: hom456@aol.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: steve newberry Email: stevnewb@ix.netcom.com Comment: I'm .philosophically interested in distributed computing, and have a 1.5 GH processor together with an ...
Name: Steve Wilson Email: psolutions2001@netzero.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Stewe Andreasson Email: steweandreasson@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set ...
Name: Stony Email: cui shi@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 Vertical ...
Name: stratos k Email: microulis@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: stylo Email: bic22@free.fr Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 Vertical ...
Name: Sub Media Email: submedia2002@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Glossary: Subspace A simplistic way to look at Freenet is as a filesystem, where anyone can save a file under a filename of their choice, and anyone else, given the ...
Name: Sugi Joe Email: ekky89@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: suken woo Email: sukenwoo@163.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: Anthony Fischer Email: SunTzuTov Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 Vertical ...
Name: Super Nova Email: super.nova.records@wanadoo.fr Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Susan Coghlan Email: smc@turbolabs.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Svein-Erik Henriksen Email: s-henrik@online.no Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Sven Berling Email: sven955@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: syed khalid Email: sakhalid86@hotmail.com Comment: internet is free world!!!! Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of ...
TWiki Administrator Group Set GROUP IanClarke Set ALLOWTOPICCHANGE TWikiAdminGroup Note: Set the members of TWiki Administrator Group in GROUP as a comma separated ...
These groups can be used to define fine grained TWIKIWEB .TWikiAccessControl in TWiki: TWikiAdminGroup WebAdminGroup Add your groups to this list and define new group ...
A guest of this TWiki web, not unlike yourself. You can leave your trace behind you, just add your name in TWIKIWEB .TWikiRegistration and create your own page. Personal ...
List of TWiki users Please take the time and add yourself to the list. To do that fill out the form in TWIKIWEB .TWikiRegistration. This will create an account for ...
Name: ta v Email: tav-reg@espians.com Comment: hmz Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: TasosPapadopoylos Email: papas123@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: tasos papadopoylos Email: papas123@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Tavin Cole Email: tavin@freenetproject.org Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: tchoi frank Email: tchoi2@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: teH' kahless Email: kahless@st-ac.de Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Teri Schaufelberger Email: sheenna9999@aol.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: termin dev Email: termin@sitoverde.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: test Email: sabrina69123456@gmx.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: Theo Thomas Email: theo.thomas@freenet.co.uk Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Theodore Hong Email: twh1@doc.ic.ac.uk Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: thierry ringeval Email: th.ringeval@libertysurf.fr Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set ...
About This Site This website is based on http://www.twiki.org/ TWiki , and is designed to allow ease of editing. Anyone can edit the Pub.WebHome public area of this ...
Name: Thomas de Ruiter Email: thomas@de-ruiter.cx Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Thomas Sturm Email: tsturm@gmx.de Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: Thomas Windheuser Email: t.windheuser@gmx.de Comment: Muhahaarrrr Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box ...
Name: Tiernan Hubble Email: thubble@shaw.ca Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: tim douglas Email: tdoug12@aol.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: Tim Sczes Email: timsczes@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: There's more than one way to do it Email: gerrit@familiehaase.de Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text ...
Name: tim vincent Email: timvincent@altavista.fr Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Timm Murray Email: hardburn@users.sourceforge.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set ...
Name: tina macha Email: hellotina3000@yahoo.de Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Here would stand the information about the Tokyo office: Address: Phone: Fax: List of employees at TokyoOffice. Related topic: OfficeLocations, WIKIUSERSTOPIC
Name: Tom Jackson Email: onemoreround@cornerpub.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Tom Longson Email: tlongson@socal.rr.com Comment: Free the bunnies. Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit ...
Name: TomokazuKawabata Email: kawabata@manage.nitech.ac.jp Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set ...
Name: tony jones Email: plypen1100@optusnet.com.au Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Tony Sanchez Email: tonyrs018@juno.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Third Party Tools A variety of people have written some excellent tools and clients for use with Freenet. Freenet Publishing & Retrieval Tools http://freeweb.sf.net ...
Name: toto titi Email: wchicos@free.fr Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 Vertical ...
Name: Tranber Maufmauf Email: tranber91@yahoo.fr Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Translations of the Freenet website Note: You should automatically have been directed to the correct translation in your language if it exists, and if your web browser ...
Name: Travis Bemann Email: bemann@execpc.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: troy tumbleson Email: doretat@ckt.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: K. Tsakaloglou Email: tsakf@tee.gr Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: Tuomas Airaksinen Email: tuomas.airaksinen@tuma.stc.cx Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box ...
Name: Alfredo Ioannilli Email: alfredo.ioannilli@tin.it Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set ...
Name: ty forsman Email: tyme 75@yahoo.com Comment: after all this shit to down load it better be worth it Personal Preferences (details in TWIKIWEB .TWikiVariables ...
Name: Udi Wertheimer Email: spikologia@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Urban Koistinen Email: Urban.Koistinen@abc.se Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Ushamalini Pandi Email: usha mcc@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: UsmanNajib Email: boilingjava@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Lajos Lajos Email: scat@freemail.hu Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 ...
Name: vanilla silverfish Email: vanilla13@diaryland.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set ...
Name: Vash The Stampede Email: vash the stampede @libero.it Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: ...
Name: Hendrik Graupner Email: h.graupner@firemail.de Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Anthony Email: Trojaneer 21@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: vicente fernandez Email: j2f3no@altavista.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: victor tracy Email: alaskavic@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: vinnie vasquez Email: vinniev103@hotmail.com Comment: None at this time! Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text ...
Name: vivian huang Email: wh whuang@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Âëŕńĺíęî Ŕëĺęńĺé Email: alex helen@atlasUA.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: WALTER FANCOURT Email: Wfancourt@cs.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Wayne Costley Email: waynenets3@netscape.net Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Web Bouthi Email: webbouthi@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
"I worry about my child and the Internet all the time, even though she's too young to have logged on yet. Here's what I worry about. I worry that 10 or 15 years from ...
NOTIFYTOPIC is a subscription service to be automatically notified by email when topics change in the TWiki.Main web. This is a convenient service, so you do not ...
TWiki.Main Web Preferences The following settings are web preferences of the TWiki.Main web. These preferences overwrite the site-level preferences in TWIKIWEB . ...
Statistics for TWiki.Main Web Month: Topic views: Topic saves: File uploads: Most popular topic views: Top contributors for topic save and uploads: Feb 2002 18852 ...
Guide for website Editors Note: This page may only be viewed (or edited) by members of the WebAdminGroup. Useful links http://freenetproject.org/cgi-bin/twiki/edit ...
Name: Welmer Pojas Email: whp082874@hotmail.com Comment: No Comments Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: ...
Name: werner mueller Email: werner.mueller@cityweb.de Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
What is Freenet? Freenet is a large-scale peer-to-peer network which pools the power of member computers around the world to create a massive virtual information ...
Name: Whiteg Weng Email: whiteg@elixus.org Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: wolfgang emme Email: wolfgang emme@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Wolfgang Fritsch Email: w.fritsch@web.de Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Wolfgang Moll Email: mollus@t-online.de Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: WuLiSong Haijlöng Email: WuLiSong@Hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Wyle Coyote Email: wyle@mail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH 70 Vertical ...
Name: Xav Xav Email: xav21xav21@yahoo.com Comment: ........ :) Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: xi jingjing Email: xijingjing@hotmail.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: Zlatin Balevsky Email: zlatinb@yahoo.com Comment: Maintaining BG translation style cosmetics of the main web. Seems like I'll be doing the FAQ for a while ...
Name: Allen Wendland Email: awendtlandt@yahoo.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Name: zhe louisa tang Email: louisatang@sina.com Comment: Personal Preferences (details in TWIKIWEB .TWikiVariables) Horizontal size of text edit box: Set EDITBOXWIDTH ...
Number of topics: 569
See also the faster WebTopicList
WebNotify is a subscription service to be automatically notified by email when topics change in the TWiki.Main web. This is a convenient service, so you do not have to come back and check all the time if something has changed. To subscribe to the service, please put yourself on the list below. The format is: 3 spaces * Main.yourWikiName - yourEmailAddress
Note: It is helpful to insert your name in alphabetical order (by first name -- ignore the "Main.") -- then you can find your name (or not) more easily if you wish to remove it or confirm that you are on the list.
Related topics: TWikiUsers, TWikiRegistration
The following settings are web preferences of the TWiki.Main web. These preferences overwrite the site-level preferences in TWikiPreferences, and can be overwritten by user preferences (your personal topic, i.e. TWikiGuest in the TWiki.Main web)
Preferences:
Web preferences that are not allowed to be overridden by user preferences:
Set FINALPREFERENCES = WEBTOPICLIST, DENYWEBVIEW, ALLOWWEBVIEW, DENYWEBCHANGE, ALLOWWEBCHANGE, DENYWEBRENAME, ALLOWWEBRENAME
Notes:
A preference is defined as: 6 spaces * Set NAME = value Example:
Set WEBBGCOLOR = #FFFFC0
Preferences are used as TWikiVariables by enclosing the name in percent signs. Example:
When you write variable %WEBBGCOLOR% , it gets expanded to #FFFFC0 .
The sequential order of the preference settings is significant. Define preferences that use other preferences first, i.e. set WEBCOPYRIGHT before WIKIWEBMASTER since %WEBCOPYRIGHT% uses the %WIKIWEBMASTER% variable.
You can introduce new preferences variables and use them in your topics and templates. There is no need to change the TWiki engine (Perl scripts).
If you edit a page, then change your mind, you should click on the "Cancel Edit" link rather than just hitting "back" on your browser, since if you don't the page will remain locked.
I [Ian] have modified the TigerSkinPlugin.pm so that rather than having a fancy custom language for defining menus in the WebMenu
topic, it simply copies the topic verbatim. This has the disadvantage that menus no longer collapse and un-collapse, but the advantage that it is more flexible, and that where the old mechanism was a browser-compatability nightmare, the new mechanism can stick to nice 100% certified HTML.
Additionally, I have added Developer and Actions sections to the menu, which are only displayed for logged in users. This basically makes the website look like "Just Another Website" to non-logged in users.
There are two components to the multi-language support. Firstly, a separate "web" has been created for each language, named according to the language's two-letter language code, for example, French is "FR", and Italian is "IT". The only exception is English which remains in the "Main" web. This affords much flexibility with permissions, and templates.
For languages other than English, editors should use the "Edit Lang Menu" button in the Actions section of the menu.
The second component is a simple PHP script in freenet/htdocs/index.php, which checks the HTTP_ACCEPT_LANGUAGE environment variable to see what language the user's browser is requesting, and automatically redirects the user to the appropriate page.
Freenet is a large-scale peer-to-peer network which pools the power of member computers around the world to create a massive virtual information store open to anyone to freely publish or view information of all kinds. Freenet is:
Highly survivable: All internal processes are completely anonymized and decentralized across the global network, making it virtually impossible for an attacker to destroy information or take control of the system.
Private: Freenet makes it extremely difficult for anyone to spy on the information that you are viewing, publishing, or storing.
Secure: Information stored in Freenet is protected by strong cryptography against malicious tampering or counterfeiting.
Efficient: Freenet dynamically replicates and relocates information in response to demand to provide efficient service and minimal bandwidth usage regardless of load. Significantly, Freenet generally requires log(n) time to retrieve a piece of information in a network of size n.
Freenet is an enhanced Open Source implementation of the system described by Ian Clarke's 1999 paper "A distributed decentralized information storage and retrieval system" (see here). Work started on Freenet shortly after the publication of this paper in July 1999 by Clarke and a small number of volunteers. By March 2000 version 0.1 of Freenet was ready for release. Since March 2000 Freenet has been extensively reported on in the press, albeit primarily due to its implications for copyright rather than for its wider aim, namely freedom of communication.
Freenet development continues at an increasingly breathless pace, releasing a new version almost every two weeks, each with significant performance and ease of use improvements. At the time of writing the 0.4 release, with major architectural, performance, and security improvements, is nearing completion.
The system provides a flexible and powerful infrastructure capable of supporting a wide range of applications, including:
Uncensorable dissemination of controversial information: Freenet protects freedom of speech by enabling anonymous and uncensorable publication of material ranging from grassroots alternative journalism to banned exposes like Peter (Spycatcher) Wright's and David Shayler's revelations about MI5.
Efficient distribution of high-bandwidth content: Freenet's adaptive caching and mirroring is being used to distribute Debian Linux software updates and to combat the Slashdot effect.
Universal personal publishing: Freenet enables anyone to have a website, without space restrictions or compulsory advertising, even if you don't own a computer.
Freenet is an open, democratic system which cannot be controlled by any one person, not even its creators. It was originally designed by Ian Clarke and is being implemented on the open-source model by a number of volunteers.
Comment: Maintaining BG translation + style cosmetics of the main web. Seems like I'll be doing the FAQ for a while, така че ако някой иска да се заеме с обновяването на превода на Български е добре дошъл.