Okay, this step will be harder again, as it is now how to store your freesite.

I guess that you might like to change your freesite from time to time, so it should not be static. Even if it were static, some files could get dropped. Although one cannot change a file that is in Freenet any more, you can insert another one if one is dropped. This would be even possible for anyone else, not only for you - if there were no SSKs.

SSKs:

A SSK consists of two parts (a bit like a PGP or GPG key): One is public and you need it to retrieve a freesite. The other part is private and you need it to insert a freesite. DO NOT LOSE THIS PART or you cannot update your freesite any longer.

As those keys have to fit together, you can generate a `key pair' by pressing the button on the right. If you want to use the same key pair as in another FIW project, enter a "#" and the project number into the Public Key field and click "Generate". If you already have a key pair outside FIW, you can copy&paste it into the two text boxes. if there is a problem with copy&paste, simply create a new pair and replace it with the actual one in the `fiw.conf' file afterwards (before inserting!).

If you want to use a CHK instead (only for One Shot Sites!), simply enter CHK into both fields. For a KSK enter KSK into both fields and the name for the KSK into the key dir field (KSKs are not available for DBR sites, either).

SSK Entropy:

This feature (also known as SSK crypto key) makes it harder to decrypt SSK files in your datastore - so it is generally a good idea to use. Whenever you create a new key pair (and your freenet build is recent enough), the entropy field is filled with a new value. If you do not want to use SSK entropy (for some reason), remove that entry manually. Sites using entropy will be retrievable with "any" Freenet builds I know, but for inserts one should use build 5017 or above.

CAUTION: When you already have inserted some data into a SSK, changing (or removing) the crypto key is generally a *bad* idea, as it may produce nasty error messages! As the crypto key appears in the public URI, it is generally a bad idea to change that value for existing freesites anyway (as the requests from the older edition header or DBR file will create errors when retrieving w/o the crypto key).


Key dir:

This is the "human readable" part of your site link. It will help others to distinguish between links for different sites (as the public key usually looks like crap) and allow you to insert more than one freesite with the same SSK (to show that these sites are made by the same person).

The key dir may only contain printable ASCII characters, except !"#$%&'()* and spaces.

Now let's look at an example:

SSK@rBjVda8pC-Kq04jUurIAb8IzAGcPAgM/TFE//

it consists of "SSK@", the public key "rBjVda8pC-Kq04jUurIAb8IzAGc", the sequence "PAgM/", the key directory "TFE" and two slashes.

Path:

This thing has nothing to do with Freenet, only with your file system. It should be an absolute canonical (i. e. no ".." in it) path name to the dir where your freesite is stored locally. It must contain at least an index.html, and it should contain your ActiveLink image. As FIW will create files in that directory, the user running FIW must have write access to it.

ActiveLink:

As freesites get dropped from time to time, it would be nice to see from a link if the site is still active. That's what ActiveLinks are for (they are also for precaching your site's map file and to see if a new edition of an Edition freesite is available).
An ActiveLink is an image of 95x32 pixels and should be PNG or GIF file format.

You can enter your activelink name in the Parser settings tab now.

Charset:

If you want to use other charsets for your freesites than ISO-8859-1 (aka Latin-1 aka Western Europe Charset), you have to specify that here - otherwise the anonymity filter will strip that charset from your website. (The reason for that is, that multibyte charsets like UTF-16 use more than one byte for a usual ASCII char and so the anonymity filter would not notice that there are usual ascii chars in it - like evil java scripts and such things). If you leave that field empty, ISO-8859-1 is used.

DBR vs. Edition Site:

A DBR site links to a new "virtual" URL every day. (Date based redirect; actually cou can specify any update interval, but mot people use 1 day for it.). So it is interesting for freesites that change regularly. If one uploads a DBR freesite, he has to upload one (and only one) map file for every day. So if you know that you cannot upload a file on one day, you have to upload it for two days the day before. If you don't, the site will be inaccessible on that day. On the other hand, if you always upload it for one week, you won't be able to change it before that week is over.

Another approach is an Edition freesite. This kind of freesite does not have automatic redirects, but on the top of the page there are ActiveLinks to future editions. (You can setup FIW's parser to create these links for you.) If you upload a new edition, these links become visible and a user can click them to get to the next edition. The advantage of Edition sites is that you can update them whenever you want to, but people linking to your site have to change their links frequently (as the edition number is part of the link), to keep them accurate.

So you should use an Edition freesite only for content that changes very rarely (less than once a week, I'd say) and in unpredictable intervals.

An example for a DBR freesite is `TFE' mentioned above.

An example for an Editon Freesite is `Nubile':

SSK@qe3ZRJg1Nv1XErADrz7ZYjhDidUPAgM/nubile/11//

As you see, the edition number (11 when I wrote this) is part of the link.

If you want to create an one shot freesite (one that never changes), you can select it here as well.

Check settings:

You can check your settings now (may take some time) and then save&continue with "Next >>".

NOTE THAT "Check Settings" SAVES YOUR SETTINGS AS WELL.
