On Mon, Apr 23, 2001 at 05:29:26PM +1200, David McNab wrote:
> I need a site SSK public key for each of these.
>
> So for each domain you submit, you'll need to have a pre-existing site at:
> 'freenet:MSK@SSK@somedamnsskpublickey/domainname//'
>
> For example, if you want microsoft.free, I'll need you to create a DBR-based
> MSK site:
> freenet:MSK@SSK@my-ssk-public-key/microsoft//
> Note - omit the '.free' from your subkey!
>
> Note also - FreeWeb uses freenetmirror as its upload engine, so any site
> uploaded with freenetmirror is compatible (as long as it uses DBR).
I have some concerns over this approach. What is required for someone to
access FreeWeb? I get the impression that it:
* Is Windows only
* Is closed source (I find the argument that the code is too disorgainised
to release yet to be somewhat unconvincing)
* Relies on some central DNS server to convert .free domains to FProxy
domains
* Mandates that anyone who wishes to use a .free domain uses FreeWeb, thus
forcing them to tolerate the above-mentioned restrictions.
FreeWeb seems to add a very thin layer around Freenet, and freenetmirror,
but in the process adds a number of rather undesirable requirements.
Can you clarify this David?
Ian.
PGP signature
