6) '!/' - example SSK@blah/name!/index.html
Could be a winner :)
I'll support it parallel to '//' in FwProxy (which I expect to start testing
on 0.4 in the next day or two), and see how the misbehaving 3rd party progs
(such as ht://dig and Offline Explorer) behave, and report findings back to
Hi folks,
To assist with 0.4 testing, I've released some FCP-based clients that are
now
working with 0.4 metadata
0) FreeWeb - pre-release version 0.1.4 - supports freenet 0.4 and freenet
0.3 metadata, available from http://freeweb.sf.net/index1.html It works on
Linux via Wine, if you tweak
0.4 is incompatible with 0.3. Even if there weren't good design decisions
for doing so (which there are), I still think 0.4 should be incompatible
with 0.3 just for the sake of starting with a fresh network.
0.3 sucks. Let it die.
- Original Message -
From: John Goerzen [EMAIL
0.3 sucks. Let it die.
0.3 does have problems. No-one will mourn it.
But surely some of its *content* is worth saving and re-inserting into 0.4
- Original Message -
From: Timm Murray [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, July 19, 2001 02:24
Subject: Re:
Hi folks,
To assist with 0.4 testing, I've released a couple of FCP tools that are now
working with 0.4 metadata
1) fcpget - a simple command-line key retrieval prog
2) FwProxy - like FProxy, but working with 0.4. By default, FwProxy listens
on port , and talks to a node on localhost:8481,
Hi folks,
To assist with 0.4 testing, I've released a couple of FCP tools that are now
working with 0.4 metadata
1) fcpget - a simple command-line key retrieval prog
2) FwProxy - like FProxy, but working with 0.4. By default, FwProxy listens
on port , and talks to a node on localhost:8481,
Hi all,
FreeWeb now works with Freenet 0.4
I've put up a pre-release test version of FreeWeb 0.1.4 on the site -
http://freeweb.sf.net/index1.html
To enable freenet 0.4 compatibility, you must be running a freenet 0.4 node.
Also, you'll need to open the options window, change the FCP port to
