IPFS Bootstrap Command

[llSourcell]

Resolution to issue #117

All of the features work as described in the issue referenced.

The peers are added to the config file. You can add new peers, delete those new peers, and list all peers.

[jbenet]

How about:

    Long: `ipfs bootstrap - show, or manipulate bootstrap node addresses

SECURITY WARNING:

The bootstrap command manipulates the "bootstrap list", which contains 
the addresses of bootstrap nodes. These are the *trusted peers* from 
which to learn about other peers in the network. Only edit this list 
if you understand the risks of adding or removing nodes from this list.

Running 'ipfs bootstrap' with no arguments will run 'ipfs bootstrap list'.

Commands:

  list               Show the boostrap list.
  add <address>      Add a node's address to the bootstrap list.
  remove <address>   Remove an address from the bootstrap list.

`,

[llSourcell]

this was fixed

[jbenet]

Hey @llSourcell thanks for the PR! Very much appreciated.

But please familiarize yourself more with Go and with the codebase. This duplicates a lot of code and ignores existing facilities. Since I take it you're new to Go, in the future, maybe a good idea would be to propose the changes you'll be making by describing the design first, so that I or others can point you in the right direction before wasting your time duplicating code.

[llSourcell]

np, thanks for the CR. This was a personal lesson in distributed team communication. I'll vocalize what I'm doing more.

[llSourcell]

alright fixed everything

[jbenet]

@llSourcell these changes do not address the comments-- for example, still not using subcommands. Please look back through all of them. Github hides outdated diffs, so make sure to open those

[llSourcell]

k thx. re: multiaddr and subcommands- i'm on it.

[llSourcell]

ok everything addressed except multiaddr because multiaddr doesn't yet contain peerIDs so we have to parse them manually for now.

[jbenet]

Great! Thanks for addressing those, @llSourcell

[jbenet]

Can't automatically merge, so will merge manually.

[jbenet]

I'm going to have to squash the history. It's not go-fmt ed at all, and causing conflicts with the rebase. In the future, you want to make to (or make your editor) run go fmt (and golint while at it) before committing. Most editors have nice plugins that do it all for you on save.

[jbenet]

rebased, squashed history because of fmting, improved and resubmitted at #144 (cant push to this branch)