> <!DOCTYPE>, instead of
> <!DOCTYPE HTML PUBLIC .... blah blah>
>
> The test site I inserted into my own node did have a full doctype tag
> when I wrote it, but it didn't when I retrieved it, it just had <!DOCTYPE>.
>
> Is this due to fproxy's anonymity filter? If so, why does it
> remove/shorten them? Also, I've noticed that the default gateway page
> does have a full doctype tag, why, if  is fproxy that removes the tags
> from freesites, does it let this one through?

This is a very likely possibility because the doctype makes reference to a
W3C DTD which is a public internet link.  The annonymity filter needs to
remove references to internet sites since most browsers will send a
referral URL that invades your privacy (it essence if the web browser goes
to the validation site it will do so with the address of the page you are
viewing.  This invades your privacy becomes someone reading the access
logs can find out what freesite you were visiting).  The government could
subpoena W3C's weblogs to find out about freesite accesses and they'll
have an IP number attached to the visit to their site so the referral
freesite URI + the IP number access in W3C's log could be used against you
if the material you were accessing is outlawed in the jurisdiction of
W3C's server or any government system that sees packets along the route to
W3C.  They could visit the same freesite by the referal URI and find out
"what book you were reading at the time"

> 2.  I have noticed on some pages they have this sort of section in the
> header:
>
> <!--index
> <title>The Freedom Engine</title>
> <category>Index</category>
> <description>The mother of all freesite link lists.</description>
> <activelink>ActiveLink.jpg</activelink>
> <address type>DBR</address type>
> <author>CofE</author>
> -->

These are the meta tags used by freesites to support their inclusion onto
the various indexing freesites.

title - ovbious, this is the site's name
category - what kind of site is this?  I don't have knowledge
           about what acceptable values for this are
description - textual description of the freesite
activelink - the site icon to be associated with your freesite
             (think like the little banner icons many people
              put onto their regular internet websites for
              people to link to them with)
addresstype - again I'm iffy on all the acceptable values but DBR
              AFAIK means the address of this freesite permutates
              automatically to a different site name either daily or
              weekly at midnight GMT.  A site marked as DBR has to
              reinsert itself at the new DBR generated redirect
              key or the site effectively disappears (unless you
              select go to earlier site in the error screen that
              comes up for references to DBR sites that haven't
              been updated yet [or your routing can't find the new
              content yet]).

The alternative to DBR is to using revisions by putting an integer in the
URI part of your site.  You start the integer at 1 on your first insertion
of the site.  Your site forward references a number of 'editions' ahead
(that you have not yet inserted) by refering to the same uri echanging 1
for 2, 2,3 3,4 etc for several steps (usally four or five).  You have an
activelink image on each edition so on the existing (edition 1) page shows
up for edition 1.  If you haven't inserted a new edition then the other
activelinks show up as broken images.  But if at somepoint you insert with
the integer now set to 2 the #2 activelink comes alive and the visitor to
the #1 site now knows (by the unbroken activelink) that a second edition
is now available.  To be nice to people that might want to check on older
content your edition list should be design so that when more editions are
available that your have edition links that you put forward and at least
one previous edition so the users can backtrack the editions of your
freesite.

ie: site using 5 edition links (the numbers in [] would be your edition
activelinks)

first edition:
[1] [2] [3] [4] [5]

second edition:
[1] [2] [3] [4] [5]

third edition:
[2] [3] [4] [5] [6]

fourth edition:
[2] [3] [4] [5] [6]

fifth edition:
[3] [4] [5] [6] [7]

sixth edition:
[4] [5] [6] [7] [8]

The edition list 'scrolls' as you have more editions than links the user
can still follow the backlinks to get to previous editions.

Or you can keep a permanent edition list with at least one forward edition
link).  You'd probably do it with buckets.  This following setup would let
you do four editions before having having to add another row for the next
five editions:

while publishing edition 1-4:
[ 1] [ 2] [ 3] [ 4] [ 5]

while publisihing edition 5-9:
[ 1] [ 2] [ 3] [ 4] [ 5]
[ 6] [ 7] [ 8] [ 9] [10]

while publisihing edition 10-14:
[ 1] [ 2] [ 3] [ 4] [ 5]
[ 6] [ 7] [ 8] [ 9] [10]
[11] [12] [12] [14] [15]

while publisihing edition 15-19:
[ 1] [ 2] [ 3] [ 4] [ 5]
[ 6] [ 7] [ 8] [ 9] [10]
[11] [12] [12] [14] [15]
[16] [17] [18] [19] [20]

etc...

Note: larger bucket sizes (I chose 5) will increase the time taken for the
page, moreover, the main disadvantage of a permanent list is that when
older editions fall off the freenet (remember that stale unaccessed
content is moved out to make way for new content).  So IMHO the scrolling
idea is probably the better one becuase it never refers to more than five
activelinks at once.  Now if you have the kind of freesite where all past
editions are going to be popular and edition addition is frequent (but
greater-than daily) use the bucket method but scroll off the top bucket to
keep the edition list to three rows.

ie: for the last part of the last example while publishing edition 15-19:

[ 6] [ 7] [ 8] [ 9] [10]
[11] [12] [12] [14] [15]
[16] [17] [18] [19] [20]

while publisihing edition 20-24:

[11] [12] [12] [14] [15]
[16] [17] [18] [19] [20]
[21] [22] [23] [24] [25]

while publisihing edition 25-29:

[16] [17] [18] [19] [20]
[21] [22] [23] [24] [25]
[26] [27] [28] [29] [30]

This will keep the size down but allow backtracking in sets of five which
will navigate more quickly for the user trying to access previous
editions.

If you are revising editions daily it might be time to switch to a DBR or
change to buckets of 7 and keep five rows (35 days) of editions.  Scroll
the list (delete the topmost row) and add a new row each time you go from
the last edition # in the third row to the first edition # in the 4th row.
This means the current week will always be in the middle row and that
there will be just under half a month of backtracking each way.
_______________________________________________
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]

Reply via email to