After the two recent changes to SSKs and manifests, both of which broke
hyperlink compatibility, I am now reasonably sure I won't have to do it
again. So lets have some freesites! :)

The first change:
For SSKs: Request URIs have 3 components, the last bit indicating the
type of crypto being used. Insert URIs don't.

E.g.:
MAKESSK
Insert URI:
SSK at 
AIXbFPyeMrEb4~gT9l-OsiEIsDy9Aee~pU86xtVrVLVI,c7-ThmvR05GvR1hUUE29tzk~v4x2vPFZTd4MBf69dNc/
Request URI:
SSK at 
pomiX2edfxWlmvAKpfUv05BMtSQQ3kn92G4XfOG8dZk,c7-ThmvR05GvR1hUUE29tzk~v4x2vPFZTd4MBf69dNc,AQABAAE/

The second change:
We now use single slashes for manifests.

Hence:
http://127.0.0.1:7001/freenet:SSK at 
PTIDQD6DZBjmmgeWoPDL35J1jyD1R~Fb6L6ysTCgfJA,xhRMl7eAAgMeVfHat11RBWW-P1zCRThXBV1OiTdchAg,AQABAAE/testsite/P1010003.JPG

Is a manifest.
Deconstruct it:
http://127.0.0.1:7001/ - my fproxy runs on port 7001
freenet: - duh
SSK at 
PTIDQD6DZBjmmgeWoPDL35J1jyD1R~Fb6L6ysTCgfJA,xhRMl7eAAgMeVfHat11RBWW-P1zCRThXBV1OiTdchAg,AQABAAE/testsite
- the SSK, including the site name. Note that it has 2 commas, so it is
  a *request* SSK. This particular one consists of a few pictures of
  amphibians. (There's a bigger one being inserted).
/ - manifest lookup
P1010003.JPG - filename within the SSK

Freenet 0.7 is still a testnet, with no real anonymity, (with a built
in back door to browse old logs, and a central server to which all
nodes are reported) but if you don't mind that, feel free to come test
it with us on #freenet on irc.freenode.net. It has a disk usage of
well under 2GB, including the 512MB datastore.

What is the next step? Apart from debugging...
- Basic FCP.
- Download/upload manager.
- Updatable keys.
-- 
Matthew J Toseland - toad at amphibian.dyndns.org
Freenet Project Official Codemonkey - http://freenetproject.org/
ICTHUS - Nothing is impossible. Our Boss says so.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: 
<https://emu.freenetproject.org/pipermail/tech/attachments/20060116/b6f96a4f/attachment.pgp>

Reply via email to