log for hellnet

update

2010-09-03T12:30:12+00:00

update

--- a/hellnet/hspawn/use
+++ b/hellnet/hspawn/use
@@ -4,7 +4,7 @@

h3. Simple data storage

-All the data in Hellnet is stored in 64kb chunks. You can see your current cache in ~/.hellnet/store.
+All the data in Hellnet is stored in 256kb chunks. You can see your current cache in ~/.hellnet/store.

A chunk may be a [[/hellnet/tech/recursive-filelinks|filelink]], which stores information about chunks that form a file.

RIP Hellage

2010-09-03T11:24:22+00:00

RIP Hellage

--- a/hellnet/hellage/admin
+++ /dev/null
@@ -1,14 +1 @@
-h1. How to run your own Hellage index
-
-First, see [[use]] for installing Hellage.
-
-Then, see [[/hellnet/hspawn/use#metatrees]] for information how to create your own meta key.
-
-Last, run
-
-bc. $ hellage-genmeta mykey hackage
-
-Where @mykey@ is your key alias and @hackage@ is your meta name.
-
-This will download index and packages from [http://hackage.haskell.org] and store links in your meta. If download of certain package is stalled for too long, feel free to interrupt the program; next time it will start where it ended, only need to re-download index.

--- a/hellnet/hellage/index
+++ /dev/null
@@ -1,5 +1 @@
-use - How to use it
-admin - How to run your own mirror
-
-Hellage is a distributed "Hackage":http://hackage.haskell.org/ haskell packages' repository mirror.

--- a/hellnet/hellage/use
+++ /dev/null
@@ -1,73 +1 @@
-h1. How to use Hellage
-
-h2. Install
-
-This may be insanely difficult. Or not.
-
-If you can't build from source, get the [[../hspawn/jumpstart]] package.
-
-h3. Otherwise
-
-First, "install Hellnet":/hellnet/hspawn/build. If you manage it, the rest is simple:
-
-bc. $ cabal install hellage
-
-or, @git clone git://git.bitcheese.net/hellage && cd hellage && runghc Setup.hs install@ and have fun.
-
-h2. Actually use it
-
-First, you need to add at least one Hellnet node to your nodelist. You can use bitcheese.net:6666 for now.
-
-bc. $ hell-nodes handshake bitcheese.net 6666
-
-Then you need to run hellage daemon on your machine:
-
-bc. $ hellage 8da7ec91e46c4b1444bd1b1a151a038a0544fad23266111a8a84178efb9499cb756a265bbe456bd9ec9ba309bf146f8453ba17201ff968e181e36b5efe54fc1f hackage
-
-Here, *8da7ec...* is my encryption key ID and *hackage* is meta name of hellage. If you plan to use this (or any other) key often, you can create an alias:
-
-bc. $ hell-meta alias add voker57_key 8da7ec91e46c4b1444bd1b1a151a038a0544fad23266111a8a84178efb9499cb756a265bbe456bd9ec9ba309bf146f8453ba17201ff968e181e36b5efe54fc1f
-
-and then refer to this key as "voker57" everywhere:
-
-bc. $ hellage voker57_key hackage
-
-This command will run hellage on its default port, which is 6609. If you want to change it, run hellage with -p 64657.
-
-*WARNING WARNING*: Currently hellage does not bind to localhost, thus anybody with access to port can use it. Use firewalls or whatever to protect.
-
-Now, let's add hellage to cabal's sources:
-
-bc. $ editor ~/.cabal/config
-
-Search out the @remote-repo:@, comment it out and add hellage:
-
-bc. -- remote-repo: hackage.haskell.org:http://hackage.haskell.org/packages/archive
-remote-repo: hellage:http://localhost:6609
-
-Update the hellage index:
-
-bc. $ wget http://localhost:6609/update -O- 2>/dev/null
-Success
-
-If result is "Failed" then something went wrong and hellage won't work. Check node connectivity.
-
-Then, run @cabal update@ to get package index:
-
-bc. $ cabal update
-
-If everything was OK, then you can download packages now:
-
-bc. $ cabal install empty
-
-Congratulations! You got hellage up and running.
-
-h2. Tricks
-
-* If you don't like to keep a terminal emulator constantly running, i suggest using "daemontools":http://packages.debian.org/sid/daemontools or "dtach":http://dtach.sourceforge.net/ or "screen":http://www.gnu.org/software/screen/ for daemonizing hellage.
-* You can update hellage via hellage!
-
-h2. Troubleshooting / Feedback
-
-If you succeeded, or failed, in installing hellage by this manual, share your experience in "hellnet mailing list":http://groups.google.com/group/hellnet.

delimiters

2010-06-15T12:16:52+00:00

delimiters

--- /dev/null
+++ b/code/delimiters_must_die
@@ -1 +1,83 @@
+h1. On delimiters
+
+h2. Escaping from backslash hell
+
+OK, so you want to use simple comma-separated format to store your data.
+
+bc. one,two,three,four
+five,six,seven,eight
+
+Good! Simple and clean, human readable too. You separate entries with , and series with newlines (\n). But then, you need to store comma inside of one of values. So you decide to escape commas with \, like all decent people do.
+
+bc. one\,two,thr\,ee,four
+five,six,seven,eight
+
+Blech! Your parser cannot simply split lines by ",". It must check if \ doesn't precede it, and if it does, then strip \. But that still works.
+
+Now, you see that \ can be encountered too, and maybe even directly before ,. So, let's escape it with itself.
+
+bc. one\\\,two,thr\,ee,four
+five,six,seven,eight
+
+Three slashes! Isn't that fancy? Not much changed for your parser, you just tell him to strip one backslash from \\.
+
+Now to think of it, newlines can be encountered inside entries too. So, let's make it \n (and \r for these obscene OSes).
+
+bc. one\\\,two,thr\,ee,four
+five,\\nsix,se\nven,eight
+
+Senven? What the fuck.
+
+Well, if you made it similar so far, congrats, you are a decent man. If not, you might have used quotes.
+
+bc. one\\\,"two thr\,ee",four
+five,\\nsix,se\nven,e\"ig\"ht
+
+Such a fine backslash soup! Now, imagine you would want to pack all this inside of another CSV entry. You get something like this:
+
+bc. one\\\\\\\,\"two thr\\\,ee\"\,four\nfive\,\\\\nsix\,se\\nven,e\\"ig\\"ht
+
+Well, I made up this example, but try coding in shell (which involves), and you'll understand all this.
+
+h2. I Will Never Encounter This Set Of Bytes
+
+Let's make up a bizarre, totally random string. It will never ever appear in our data, I'm assuring you. We'll start our entry with it and end with it.
+
+bc. %%%%%%%%%%DATA BOUNDARY srfg345632rfefh56t34freg56y43rffgmy/dev/urandomsays hello#$^#$%TR%%%%%%%%%%%
+SRgwerg24yg!#RG@2365u246jh4fgb345ik54y245g56u234rgfw43r8ty2348we9fuhg309ekxc09w3fu8tu32598jf03928qrg2938rhy093rjg293riyjg92384fj8934rjhg28975y 10wejmwodkvnn32w9048hjfq 3984hf9q38hf 398rh 93q8r hg98q2hr 9g813h9rthg9 3rhf98h219hgf1923gh9 qhf91jhgh1
+%%%%%%%%%%DATA END srfg345632rfefh56t34freg56y43rffgmy/dev/urandomsays hello#$^#$%TR%%%%%%%%%%%
+
+Know what? IT FUCKING WILL APPEAR. And if you want your system not to fail miserably, you have to scan through all this data and make sure it's not there. Not worth it. And anyway, scanning for this string is rather complicated.
+
+Another good example (besides "HTTP multipart boundary":http://www.w3.org/Protocols/rfc1341/7_2_Multipart.html mocked above) is "CDATA":http://en.wikipedia.org/wiki/CDATA.
+
+h2. Taboo delimiter
+
+People will never ever need ASCII 0 in their strings! I assure you! Let's use it as delimiter. No other options.
+
+h2. Tolerable delimiting
+
+Is implemented in "JSON":http://www.json.org/. It uses backslashes plus very limited set of what can follow them. The format is quite readable and writeable by humans and parser-friendly. And also its page has nice graphics, I'd like to be able to make such myself.
+
+h2. (in search of) Perfect delimiting
+
+If you need simple strings, that will not encounter one character, you can delimit with that character. But for god's sake, do not try to allow strings do contain this character escaped.
+
+bc. very long value
+
+There is \n at and.
+
+If you need byte strings that can contain any byte, specify length before data.
+
+bc. 64 �d��W��uu&f(�69��須��?K4{u�
+�@��Ӌ*�yT��O;��|ÑZT}��Kn�
+52 �d��W��uu&�d��
+��uu&�d��W��uu&�d��W��uu&
+�d��W��uu&}
+
+Lines _start_ with \n, there is single space after numbers, numbers consist of 0-9.
+
+So, to summarize it: very strict format, *NO* escaping, taboo *OR* skip-n-bytes delimiting.
+
+This kind of escaping is implemented in my serialization format called [[transfer]].

--- /dev/null
+++ b/code/transfer
@@ -1 +1,50 @@
+h1. "Transfer" data transfer protocol
+
+This protocol can be used to transfer associative arrays with bytestrings over any byte transferring connection.
+
+h2. Text mode commands
+
+All fields are separated with single space, 'data' in FLD may contain spaces though.
+
+I will use pseudo-abnf here, because plain abnf sucks. (something) in parentheses denotes "something" field, $something later refers to its value
+
+Definitions:
+
+space = ASCII 32
+lf = ASCII 10
+non-lf = anything but lf
+non-space = anything but space
+
+h3. MOD module_name
+
+modCommand = "MOD" space *non-lf
+
+Means start of data structure named 'module_name'. If another module have already been started, throw error.
+
+h3. FLD name data
+
+fldCommand = "FLD" space *non-space space *non-lf
+
+Textual field 'name' with 'data' as content. 'data' may contain any character except of \n. Used for transferring small amount of data without linebreaks.
+
+h3. DAT name size
+
+datCommand = "DAT" space *non-space(name) space *digit(size) lf *<$size>any-byte(data)
+
+Initiates data mode for field 'name'. Right after delimiting \n recipient should start reading data and switch back to lines mode after exactly 'size' bytes of data.
+
+h3. END
+
+Ends a module
+
+Example of correct structure transfer:
+
+bc. MOD query
+FLD hops 1
+FLD query hash
+DAT args 64
+�d��W��uu&f(�69��須��?K4{u��@��Ӌ*�yT��O;��|ÑZT}��Kn��
+END
+
+Example of protocol implementation in Haskell can be seen here: [http://git.bitcheese.net/?a=summary&p=transfer]

--- a/hellnet/protocols/transfer
+++ /dev/null
@@ -1,39 +1 @@
-h1. DEPRECATED
-
-This page contains deprecated information. This has been replaced with [[http|HTTP interfaces]].
-
-h1. HellNet data transfer protocol
-
-This protocol is used to transfer data structures between HellNet nodes.
-
-Conversation consists of lines, separated by \n (text mode) or data chunks (data mode).
-
-h2. Text mode commands
-
-All fields are separated with single space, 'data' in FLD may contain spaces though.
-
-h3. MOD module_name
-
-Means start of data structure named 'module_name'. If another module have already been started, throw error.
-
-h3. FLD name data
-
-Textual field 'name' with 'data' as content. 'data' may contain any character except of \n. Used for transferring small amount of data without linebreaks.
-
-h3. DAT name size
-
-Initiates data mode for field 'name'. Right after delimiting \n recipient should start reading data and switch back to lines mode after exactly 'size' bytes of data
-
-h3. END
-
-Ends a module
-
-Example of correct structure transfer:
-
-bc. MOD query
-FLD hops 1
-FLD query hash
-DAT args 64
-�d��W��uu&f(�69��須��?K4{u��@��Ӌ*�yT��O;��|ÑZT}��Kn��
-END

Jumpstart

2010-03-03T08:30:31+00:00

Jumpstart

--- a/hellnet/hellage/use
+++ b/hellnet/hellage/use
@@ -4,6 +4,10 @@

This may be insanely difficult. Or not.

+If you can't build from source, get the [[../hspawn/jumpstart]] package.
+
+h3. Otherwise
+
First, "install Hellnet":/hellnet/hspawn/build. If you manage it, the rest is simple:

bc. $ cabal install hellage

--- a/hellnet/hspawn/build
+++ b/hellnet/hspawn/build
@@ -26,5 +26,9 @@

And pray, since not all packages on hackage are ready for GHC 6.12 and you may have to patch them.

+h2. Jumpstart
+
+Last resort: download [[jumpstart]] package, extract & launch.
+
Now, to the next step, [[use]].

--- /dev/null
+++ b/hellnet/hspawn/jumpstart
@@ -1 +1,8 @@
+h1. Hellnet jumpstart package
+
+If you can't build hellnet from hackage, this package is probably for you.
+
+This archive contains all required Hellnet && Hellage linux-x86 executables, built statically. They may require openssl, libffi and whatever your system will notify you on launch.
+
+"0.1-1-gdd80491":http://dump.bitcheese.net/files/hellnet-bin.tar.bz2 12 MB

Massive hellnet update

2010-03-02T19:49:12+00:00

Massive hellnet update

--- /dev/null
+++ b/hellnet/feedback
@@ -1 +1,4 @@
+h1. Hellnet feedback
+
+Hellnet "mailing list":mailto:hellnet@googlegroups.com ("web":http://groups.google.com/group/hellnet)

--- /dev/null
+++ b/hellnet/hspawn/serve
@@ -1 +1,25 @@
+h1. Running your own Hellnet node
+
+First: You will not be serving unrelated content, only stuff you downloaded.
+
+h2. Why?
+
+* That is the only way to publish your own metatrees for now
+* You help the network
+
+h2. How?
+
+[[build|Install hellnet]].
+
+bc. $ hell-serve 6666
+
+6666 is server port, which should be open to Internet. This will launch Hellnet server.
+
+Now,
+
+bc. $ hell-nodes handshake bitcheese.net 6666
+
+If response is "Handshake successful", all is good. Server have added you to its nodelist and will announce your address to everybody, who in turn will be able to download your chunks and metatrees.
+
+Otherwise, read the message and fix the error.

--- a/hellnet/index
+++ b/hellnet/index
@@ -3,8 +3,12 @@
protocols - protocols' documentation
crypto - cryptographic stuff used in Hellnet
hellage - distributed hackage mirror using Hellnet
+philosophy - about the project, its goals and idea
+feedback - how to provide feedback & get help on Hellnet

Hellnet is a project to create simple, distributed, anonymous data sharing network.

You can see current state of matters on [[status]] page.
+
+Current use cases: [[hellage]], [[general file sharing & setup|hspawn/use]]

--- /dev/null
+++ b/hellnet/philosophy
@@ -1 +1,10 @@
+h1. Hellnet philosophy
+
+Hellnet is simple. It tries to rely on already existing things.
+
+Hellnet is not for playing hide-and-seek with law enforcement. It's for simple, reliable distribution of legal content. No esprit de corps: you store only what you like to store, no other people's CP on your hard drive.
+
+_...or is it me too lazy to write code for sophisticated routing and shared storage?_
+
+Hellnet is named so because I like this name.

Hellnet & hellspawn update

2010-02-28T16:29:42+00:00

Hellnet & hellspawn update

--- /dev/null
+++ b/hellnet/hellage/admin
@@ -1 +1,14 @@
+h1. How to run your own Hellage index
+
+First, see [[use]] for installing Hellage.
+
+Then, see [[/hellnet/hspawn/use#metatrees]] for information how to create your own meta key.
+
+Last, run
+
+bc. $ hellage-genmeta mykey hackage
+
+Where @mykey@ is your key alias and @hackage@ is your meta name.
+
+This will download index and packages from [http://hackage.haskell.org] and store links in your meta. If download of certain package is stalled for too long, feel free to interrupt the program; next time it will start where it ended, only need to re-download index.

--- /dev/null
+++ b/hellnet/hellage/index
@@ -1 +1,5 @@
+use - How to use it
+admin - How to run your own mirror
+
+Hellage is a distributed "Hackage":http://hackage.haskell.org/ haskell packages' repository mirror.

--- /dev/null
+++ b/hellnet/hellage/use
@@ -1 +1,69 @@
+h1. How to use Hellage
+
+h2. Install
+
+This may be insanely difficult. Or not.
+
+First, "install Hellnet":/hellnet/hspawn/build. If you manage it, the rest is simple:
+
+bc. $ cabal install hellage
+
+or, @git clone git://git.bitcheese.net/hellage && cd hellage && runghc Setup.hs install@ and have fun.
+
+h2. Actually use it
+
+First, you need to add at least one Hellnet node to your nodelist. You can use bitcheese.net:6666 for now.
+
+bc. $ hell-nodes handshake bitcheese.net 6666
+
+Then you need to run hellage daemon on your machine:
+
+bc. $ hellage 8da7ec91e46c4b1444bd1b1a151a038a0544fad23266111a8a84178efb9499cb756a265bbe456bd9ec9ba309bf146f8453ba17201ff968e181e36b5efe54fc1f hackage
+
+Here, *8da7ec...* is my encryption key ID and *hackage* is meta name of hellage. If you plan to use this (or any other) key often, you can create an alias:
+
+bc. $ hell-meta alias add voker57_key 8da7ec91e46c4b1444bd1b1a151a038a0544fad23266111a8a84178efb9499cb756a265bbe456bd9ec9ba309bf146f8453ba17201ff968e181e36b5efe54fc1f
+
+and then refer to this key as "voker57" everywhere:
+
+bc. $ hellage voker57_key hackage
+
+This command will run hellage on its default port, which is 6609. If you want to change it, run hellage with -p 64657.
+
+*WARNING WARNING*: Currently hellage does not bind to localhost, thus anybody with access to port can use it. Use firewalls or whatever to protect.
+
+Now, let's add hellage to cabal's sources:
+
+bc. $ editor ~/.cabal/config
+
+Search out the @remote-repo:@, comment it out and add hellage:
+
+bc. -- remote-repo: hackage.haskell.org:http://hackage.haskell.org/packages/archive
+remote-repo: hellage:http://localhost:6609
+
+Update the hellage index:
+
+bc. $ wget http://localhost:6609/update -O- 2>/dev/null
+Success
+
+If result is "Failed" then something went wrong and hellage won't work. Check node connectivity.
+
+Then, run @cabal update@ to get package index:
+
+bc. $ cabal update
+
+If everything was OK, then you can download packages now:
+
+bc. $ cabal install empty
+
+Congratulations! You got hellage up and running.
+
+h2. Tricks
+
+* If you don't like to keep a terminal emulator constantly running, i suggest using "daemontools":http://packages.debian.org/sid/daemontools or "dtach":http://dtach.sourceforge.net/ or "screen":http://www.gnu.org/software/screen/ for daemonizing hellage.
+* You can update hellage via hellage!
+
+h2. Troubleshooting / Feedback
+
+If you succeeded, or failed, in installing hellage by this manual, share your experience in "hellnet mailing list":http://groups.google.com/group/hellnet.

--- a/hellnet/hspawn/build
+++ b/hellnet/hspawn/build
@@ -2,11 +2,11 @@

Warning: this requires lot of magic

-h2. Downloading
+h2. Manually

Get the latest source from git: @git clone git://git.bitcheese.net/Hellnet@

-Requirements are: "GHC":http://haskell.org/ghc 6.10 (didn't check with other compilers), "Cabal":http://haskell.org/cabal (you will have to install them manually, as described "here":http://book.realworldhaskell.org/read/installing-ghc-and-haskell-libraries.html) HTTP, Lucu, Crypto (these are Cabal packages, you can install them with @cabal install name@)
+Requirements are: "GHC":http://haskell.org/ghc 6.12 (didn't check with other compilers), "Cabal":http://haskell.org/cabal (you will have to install them manually, as described "here":http://book.realworldhaskell.org/read/installing-ghc-and-haskell-libraries.html) HTTP, Lucu, Crypto (these are Cabal packages, you can install them with @cabal install name@)

Once you have all those installed, Hellnet can be built with

@@ -17,6 +17,14 @@
On first stage, Cabal may complain about missing dependencies, you'll have to install them.

Alternatively, if you don't want to mess with Cabal, you can just run 'make', it will compile all the executables in current folder. They are static and can be safely moved.
+
+h2. Via cabal
+
+Hellnet is available on Hackage. To install it, you'll need working Cabal setup (see above). Then
+
+bc. $ cabal install hellnet
+
+And pray, since not all packages on hackage are ready for GHC 6.12 and you may have to patch them.

Now, to the next step, [[use]].

--- a/hellnet/hspawn/use
+++ b/hellnet/hspawn/use
@@ -51,7 +51,7 @@

And after short wait read the text of GPL.

-h2. Meta trees
+h2(#metatrees). Meta trees

[[/hellnet/tech/metatrees|Meta trees]] are tool to publish named information to Hellnet and keep it updated. Authenticity of information is guaranteed via digital signatures.

--- a/hellnet/index
+++ b/hellnet/index
@@ -1,3 +1,9 @@
+tech - descriptions of technologies used in Hellnet
+hspawn - documentation related to Haskell implementation
+protocols - protocols' documentation
+crypto - cryptographic stuff used in Hellnet
+hellage - distributed hackage mirror using Hellnet
+
Hellnet is a project to create simple, distributed, anonymous data sharing network.

You can see current state of matters on [[status]] page.

updated short meta res. desc.

2010-02-19T22:24:30+00:00

updated short meta res. desc.

--- a/hellnet/protocols/http/index
+++ b/hellnet/protocols/http/index
@@ -6,7 +6,7 @@

|_. Query |_. Path |_. Static/dynamic |_. Description |
| GET | @/chunks/([0-9a-f]+)@ | static | [[/hellnet/tech/chunk|Chunk]] with hash $1 |
-| GET | @/meta/([0-9a-f]+)/([^/]+){,\.key,\.sign}@ | static | [[../tech/metatrees|Metatree]] of key $1 and name $2, and its signature & date |
+| GET | @^hell://meta/([0-9a-f]{64})/([^/]+)/(.*)(/.*)$@ | static | [[../tech/metatrees|Metatree]] of key $1 and name $2 |
| GET, HEAD | @/hello@ | static | Check whether node is up |
| POST | @/handshake@ | dynamic | Establish a link to node |

More hellnet updates

2010-02-19T22:07:16+00:00

More hellnet updates

--- a/hellnet/hspawn/use
+++ b/hellnet/hspawn/use
@@ -1,11 +1,9 @@
h1. Usage of Hellnet

-Currently, the only thing Hellnet can do is file storage and retrieval.
+*WARNING: This part contains much unsettled stuff and interfaces that can be not convenient to use yet. This will change.*

-h2. How it works
+h3. Simple data storage

-h3. Data storage
-
All the data in Hellnet is stored in 64kb chunks. You can see your current cache in ~/.hellnet/store.

A chunk may be a [[/hellnet/tech/recursive-filelinks|filelink]], which stores information about chunks that form a file.

@@ -20,38 +18,88 @@

So, let's assume you need to share a copy of GPL[2]. It's named COPYING and located in current folder. Here you go:

-bc. hell-insert COPYING
-COPYING: hell://file/361e6d35ac16281294314c5b40b57ccd3f0d5e6ab2ed6088e346f8e181ec4c89ac141a9a786a1f0afc454610f4db8c00af98272f44490a6f601fa08293a13be9/COPYING
+bc. % hell-insert COPYING
+COPYING: hell://file/361e6d35ac16281294314c5b40b57ccd3f0d5e6ab2ed6088e346f8e181ec4c89ac141a9a786a1f0afc454610f4db8c00af98272f44490a6f601fa08293a13be9?name=COPYING

Hellnet *inserts* the file in local storage and gives you a link to the file. You might as well request to encrypt the file, to protect your privacy:

-bc. hell-insert -e COPYING
-COPYING: hell://file/04e69a4c0cf881dfe487cb76551e0cbfabde629453765dd647f2ee5bddd3d4298a78bae8bc4094e3c4df3f76ad7bdf5112592d85f6dab3571a931a145854a391.9f85e591452b21f9390bc75a5bb016da4a73a13e58e7649bc9a748c4a80b49cf/COPYING
+bc. % hell-insert -e COPYING
+COPYING: hell://file/04e69a4c0cf881dfe487cb76551e0cbfabde629453765dd647f2ee5bddd3d4298a78bae8bc4094e3c4df3f76ad7bdf5112592d85f6dab3571a931a145854a391?name=COPYING&key=9f85e591452b21f9390bc75a5bb016da4a73a13e58e7649bc9a748c4a80b49cf

Link here consists of three or two parts, first is hash, second is encryption key. Third may be the file name. If you are using a link without filename, contents will be printed to STDOUT.

You can test how file is inserted then:

-bc. hell-get hell://file/04e69a4c0cf881dfe487cb76551e0cbfabde629453765dd647f2ee5bddd3d4298a78bae8bc4094e3c4df3f76ad7bdf5112592d85f6dab3571a931a145854a391.9f85e591452b21f9390bc75a5bb016da4a73a13e58e7649bc9a748c4a80b49cf/COPYING.2
+bc. % hell-get "hell://file/04e69a4c0cf881dfe487cb76551e0cbfabde629453765dd647f2ee5bddd3d4298a78bae8bc4094e3c4df3f76ad7bdf5112592d85f6dab3571a931a145854a391?name=COPYING2&key=9f85e591452b21f9390bc75a5bb016da4a73a13e58e7649bc9a748c4a80b49cf"
diff COPYING COPYING.2

Now let's assume you have a friend who needs to receive a copy of GPL. First, you should bring up Hellnet server on your side:

-bc. hell-serve 12345 &
+bc. % hell-serve 12345 &

where 12345 is port on your machine which is open to the world.

Then, your friend should run:

-bc. hell-nodes add 123.12.1.0 12345
+bc. % hell-nodes add 123.12.1.0 12345

where *123.12.1.0* is *your* host and 12345 is *your* open port.

Then he can type as well:

-bc. hell-get hell://file/04e69a4c0cf881dfe487cb76551e0cbfabde629453765dd647f2ee5bddd3d4298a78bae8bc4094e3c4df3f76ad7bdf5112592d85f6dab3571a931a145854a391.9f85e591452b21f9390bc75a5bb016da4a73a13e58e7649bc9a748c4a80b49cf/COPYING
+bc. % hell-get "hell://file/04e69a4c0cf881dfe487cb76551e0cbfabde629453765dd647f2ee5bddd3d4298a78bae8bc4094e3c4df3f76ad7bdf5112592d85f6dab3571a931a145854a391?name=COPYING&key=9f85e591452b21f9390bc75a5bb016da4a73a13e58e7649bc9a748c4a80b49cf"

And after short wait read the text of GPL.
+
+h2. Meta trees
+
+[[/hellnet/tech/metatrees|Meta trees]] are tool to publish named information to Hellnet and keep it updated. Authenticity of information is guaranteed via digital signatures.
+
+h3. Create a key
+
+First step is to create your own key that will be used to sign content.
+
+bc. % hell-meta genkey
+Generating keys...
+Your key ID is 02883714ac21fc87478e91cb0204a9cff2c82a1368b03aed84bfe1c3567268a7331fa5d04e8a9725b0d18094ab546068b6e569e15c09277f1ca9cd89a8ff10e9
+
+This key ID is effectively public key's hash. It's rather long and hard to remember, so we can create client-side alias:
+
+bc. % hell-meta alias add testkey 02883714ac21fc87478e91cb0204a9cff2c82a1368b03aed84bfe1c3567268a7331fa5d04e8a9725b0d18094ab546068b6e569e15c09277f1ca9cd89a8ff10e9
+
+Now you can refer to your key as "testkey"
+
+h3. Write a meta
+
+Second step is editing your meta file. It's "JSON":http://json.org and represents a filesystem of Hellnet links. Let us add our homepage:
+
+bc. % echo "<html>Hallo thar</html>" > index.html
+% hell-insert index.html
+hell://file/6890e1d532ac7a8f21453f86a082bad7109eb452589bd19606b7251973a63bbeeb9e4d66b99a0411f7d3c897445ef2dc1c8fd0da678604caff10d72bddc25e2f?name=index.html
+
+OK, we got a helllink to our home page. Let's insert it into meta:
+
+bc. % hell-meta new testkey homepage
+% hell-meta edit testkey homepage
+
+This will launch your favourite (or default) editor and open meta content in it. Editing, saving and exiting will overwrite meta content and update the meta. Let's write the following:
+
+bc. {
+ "index.html" : "hell://file/6890e1d532ac7a8f21453f86a082bad7109eb452589bd19606b7251973a63bbeeb9e4d66b99a0411f7d3c897445ef2dc1c8fd0da678604caff10d72bddc25e2f"
+}
+
+Save & exit. Now you can get your homepage by these tricky commands:
+
+bc. % hell-meta get testkey homepage /index.html
+"hell://file/6890e1d532ac7a8f21453f86a082bad7109eb452589bd19606b7251973a63bbeeb9e4d66b99a0411f7d3c897445ef2dc1c8fd0da678604caff10d72bddc25e2f"
+% hell-get hell://file/6890e1d532ac7a8f21453f86a082bad7109eb452589bd19606b7251973a63bbeeb9e4d66b99a0411f7d3c897445ef2dc1c8fd0da678604caff10d72bddc25e2f
+<html>Hallo thar</html>
+
+Other people can get it too, only using you key's real ID instead of "testkey".
+
+h2. Discover more nodes
+
+If you have already discovered at least one Hellnet node, you can use @hell-nodes discover@ to scan the net for more. All found nodes will be added to your nodelist.

fn1. Or run out of nodes

Hellnet: meta

2010-02-19T21:41:16+00:00

Hellnet: meta

--- a/hellnet/status
+++ b/hellnet/status
@@ -4,5 +4,5 @@

*Hellspawn* -- Hellnet daemon in Qt/C++. Supports data inserting, retrieving, [[protocols/transfer|message]] parsing and even some network connectivity. Doesn't work out of localhost, development is stopped in favour of hspawn.

-*[[hspawn|Hspawn]]* -- Hellnet daemon in Haskell. Currently supports data inserting and retrieval (optionally [[crypto/symmetric|encrypted]]), [[tech/metatrees]] with manual server discovery
+*[[hspawn|Hspawn]]* -- Hellnet daemon in Haskell. Currently supports data inserting and retrieval (optionally [[crypto/symmetric|encrypted]]), [[tech/metatrees]], manual bootstrapping and semi-automatic server discovery.

--- a/hellnet/tech/URIs/meta
+++ b/hellnet/tech/URIs/meta
@@ -2,15 +2,20 @@

h2. Regex

-@^hell://meta/([0-9a-f]{64})/([^/]+)/(.*)$@
+@^hell://meta/([0-9a-f]{64})/([^/]+)/(.*)(/.*)$@

$1: public key hash
$2: meta name
+$3: JPath to meta content

h2. Optional parameters

name: Any string, contents' filename
key: hex number, symmetric encryption key
+
+h2. Returned data
+
+JSON structure (meta content with possibly applied JPath).

h2. How it works

hell-updat

2010-01-03T20:05:20+00:00

hell-updat

--- a/hellnet/tech/metatrees
+++ b/hellnet/tech/metatrees
@@ -8,7 +8,7 @@

bc. {
"updated" : 1258639915,
- "key" : "hell://chunk/22fea70fde222e2463b1dd716fa9f7faf75d90ebc6517333643826348c05950021fd2a2b31dcb23c1971149adf952bd1f38763b2338708acd12e97823a5017d2?key=a1234567",
+ "key" : "22fea70fde222e2463b1dd716fa9f7faf75d90ebc6517333643826348c05950021fd2a2b31dcb23c1971149adf952bd1f38763b2338708acd12e97823a5017d2",
"name" : "test"
"content" : "hell://chunk/e4dfde12d6612f9816d1e924c274689e5236af74db23d14cf76bee0fc49690398f1c32bce9db951305a62906c4344c04a5682b1c6bdf64e219c2dde2810b44da"
}
@@ -18,7 +18,7 @@
Description of top-level fields:

"updated" : UNIX timestamp of last update
-"key" : link to public key
+"key" : public key hash
"name" : name of this meta
"content" : link to meta tree