From 080c0de9afc72c81be6d88f8d8dcbf50194430d3 Mon Sep 17 00:00:00 2001
From: Jeromy <jeromyj@gmail.com>
Date: Fri, 20 Feb 2015 03:31:16 -0800
Subject: [PATCH] add about file to ipfs on init

---
 assets/about.go  | 56 ++++++++++++++++++++++++++++++++++++++++++++++++
 assets/assets.go |  2 ++
 2 files changed, 58 insertions(+)
 create mode 100644 assets/about.go

diff --git a/assets/about.go b/assets/about.go
new file mode 100644
index 000000000..2a0bd6005
--- /dev/null
+++ b/assets/about.go
@@ -0,0 +1,56 @@
+package assets
+
+var Init_doc_about = `
+                  IPFS -- Inter-Planetary File system
+
+IPFS is a global, versioned, peer-to-peer filesystem. It combines good ideas
+from Git, BitTorrent, Kademlia, SFS, and the Web. It is like a single bit-
+torrent swarm, exchanging git objects. IPFS provides an interface as simple
+as the HTTP web, but with permanence built in. You can also mount the world
+at /ipfs.
+
+IPFS is a protocol:
+- defines a content-addressed file system
+- coordinates content delivery
+- combines Kademlia + BitTorrent + Git
+
+IPFS is a filesystem:
+- has directories and files
+- mountable filesystem (via FUSE)
+
+IPFS is a web:
+- can be used to view documents like the web
+- files accessible via HTTP at 'http://ipfs.io/<path>'
+- browsers or extensions can learn to use 'ipfs://' directly
+- hash-addressed content guarantees authenticity
+
+IPFS is modular:
+- connection layer over any network protocol
+- routing layer
+- uses a routing layer DHT (kademlia/coral)
+- uses a path-based naming service
+- uses bittorrent-inspired block exchange
+
+IPFS uses crypto:
+- cryptographic-hash content addressing
+- block-level deduplication
+- file integrity + versioning
+- filesystem-level encryption + signing support
+
+IPFS is p2p:
+- worldwide peer-to-peer file transfers
+- completely decentralized architecture
+- **no** central point of failure
+
+IPFS is a cdn:
+- add a file to the filesystem locally, and it's now available to the world
+- caching-friendly (content-hash naming)
+- bittorrent-based bandwidth distribution
+
+IPFS has a name service:
+- IPNS, an SFS inspired name system
+- global namespace based on PKI
+- serves to build trust chains
+- compatible with other NSes
+- can map DNS, .onion, .bit, etc to IPNS
+`
diff --git a/assets/assets.go b/assets/assets.go
index 705f6bf39..61ee1dc04 100644
--- a/assets/assets.go
+++ b/assets/assets.go
@@ -1,3 +1,4 @@
+//go:generate doc2go -in=init-doc/about -out=about.go -package=assets
 //go:generate doc2go -in=init-doc/readme -out=readme.go -package=assets
 //go:generate doc2go -in=init-doc/help -out=help.go -package=assets
 //go:generate doc2go -in=init-doc/contact -out=contact.go -package=assets
@@ -6,6 +7,7 @@
 package assets
 
 var Init_dir = map[string]string{
+	"about":          Init_doc_about,
 	"readme":         Init_doc_readme,
 	"help":           Init_doc_help,
 	"contact":        Init_doc_contact,