Provide default object hashesto explore/demo

[patcon]

I'm attempting to experiment with go-ipfs, but am not sure how to tell when I have it set up correctly. It might be nice if there were some hashes for default objects that people could explore as they're diving in.

Ref: IRC

[whyrusleeping]

I like this idea, @jbenet what do you think?

[jbenet]

absolutely, let's have them in the readme for now. And I want to have an ipfs tour command that shows you around.

[patcon]

Oooooh, ipfs tour sounds rad as fuck

[whyrusleeping]

👍

[whyrusleeping]

So, im looking at adding in a default file that contains something like:

Hello and Welcome to IPFS!
If you're seeing this, that means that you have successfully
installed ipfs and are now interfacing with the wonderful 
world of DAGs and hashes!

And inserting and pinning that during init.

Thoughts?

[jbenet]

+1. Put it in init.go

—
Sent from Mailbox

On Mon, Nov 3, 2014 at 11:02 PM, Jeromy Johnson notifications@github.com
wrote:

So, im looking at adding in a default file that contains something like:
Hello and Welcome to IPFS!
If you're seeing this, that means that you have successfully
installed ipfs and are now interfacing with the wonderful
world of DAGs and hashes!
And inserting and pinning that during init.

Thoughts?

Reply to this email directly or view it on GitHub:
#164 (comment)

[btc]

I pushed a commit that adds a peer identity line. Explained the reasoning here: e431dd2

If we agree it's worthwhile, you can push to that branch and we can merge together.

branch: https://github.com/jbenet/go-ipfs/compare/maybebtc-november

ipfs (maybebtc-november) λ. ipfs init -f
initializing ipfs node at /Users/btc/.go-ipfs
generating key pair
peer identity: QmcRbn41Vc2CvbpLYfN36mAWusErKWvAAHbq92LPra2gFT

[jbenet]

👍 on peer identity line

[whyrusleeping]

I added a default file in the branch defaulthash

[jbenet]

This is fixed in #639