Fix editstate build.

637bac76 added Destruct to disk.NewState.
Add a warning in documentation about using golang 1.0
custom tor address via env variable (closes #19)
Ignore invalid values of POND_TOR_ADDRESS.
Remove superfluous line break.
Merge branch 'kargig-fixdoc'
Merge branch 'ebfe-fix-editstate-build'
Added sendDraft and refactored to use it instead of send.

All interactions with pond.Message from cli.go and gui.go now take place in
network.go.  sendDraft func isolates updating the ratchet.

I believe this should simplify sending messages to multiple recipiants,
and reduce the chances of making mistakes when writing future UIs.

This should also fix a minor hickup in the GUI where, if the user begins
a reply, but deletes the inbox message before replying, then the reply
loses its status as a reply.
go fmt
Set the InReplyTo field when sending a draft from the GUI.
Added reply quoting to the GUI.

Ideally this should quote only the selected text if any text is selected
in the message viewer when the user presses reply.  At least that's how
my email client works.

I assume Go initalizes the two local varialbes I eliminated to zero,
but I thought it looked cleaner to initalize them explicitly and
and set them if inReplyTo is set.  <shrug>
Add a note about building on Tails with < 1GB of RAM.
Fix nil-pointer defer in the case of an HTTP error from the PANDA server.
Reduce the reordering limit.

The old value (2048) was just a sanity check against storing a huge
number of keys for missing messages, but was still very large. This
seems like a more reasonable number.
Edits to the panda paper
Explicitly mention the topology of communication. This is already implied further below, but it is good to clear up confusion as early as possible.
cli: print sendCommand errors instead of logging
Merge branch 'master' into merged

Conflicts:
	client/client.go
Merge pull request #94 from arlolra/panda

Edits to the panda paper
doc: don't set ORPort.

The exit instructions were suggesting that server operators set the
ORPort, which is probably a bad idea.