Merge pull request #3 from kyledrake/kylecopywork

Some copy changes, comment out unused links

src/pages/index.jade

@@ -2,33 +2,31 @@ extends ./layout.jade
 
 block content
  .row
- .col-md-2 
+ .col-md-2
  .col-md-8
  img(src="https://raw.githubusercontent.com/diasdavid/specs/libp2p-spec/protocol/network/figs/logo.png")
- h1 A multiprotocol aware networking suite
+ h1 A network framework for decentralized P2P application development
  .col-md-2
 
  hr
  .row
  .col-md-2
- ul
- li Home
- li Goals
- li Requirements
- li Usage Examples
- li
- a(href="/ready.html") is libp2p ready?
+ //
+ ul
+ li Home
+ li Goals
+ li Requirements
+ li Usage Examples
+ li
+ a(href="/ready.html") is libp2p ready?
  .col-md-8
- h2 Welcome!
- p With the developement of building IPFS, the InterPlanetary FileSystem[?], we came to learn about the several challenges imposed by having to run a distributed file system on top of heterogeneous devices, with diferent network setups and capabilities. During this process, we had to revisit the whole network stack and elaborate solutions to overcome the obstacles imposed by design decisions of the several layers and protocols, without breaking compatibility or recreating technologies.
- p In order to build this library, we focused on tackling problems independently, creating less complex solutions with powerful abstractions, that when composed, can offer an environment for a Peer-to-Peer application to work sucessfuly.
- p `libp2p` is the result of the collective experience while building a distributed system, that puts the responsability on the developers on how they want their app to interop with others in the network, favoring configuration and extensibility instead of assumptions about how the network setup.
- p In essence, a peer using libp2p should be able to communicate with another peer using different transports, including connection relay, and talk over different protocols, negotiated in demand.
- p 
- | The full specification for libp2p is a working process that can be found on 
- a(href="https:/ipfs/specs/pull/19") ipfs/specs
-
- h2 Goals and Requirements 
+ p While developing <a href="https://ipfs.io">IPFS</a>, we came to learn about the several challenges imposed by having to run a distributed file system on top of heterogeneous devices, with diferent network setups and capabilities. During this process, we had to constantly revisit the whole network stack and create solutions to overcome the obstacles imposed by design decisions of the several layers and protocols, without breaking compatibility or recreating technologies. This was a tedious, time consuming process.
+
+ p Instead of re-inventing the wheel every time we need to build a decentralized P2P application, we focused on streamlining the problem by tackling networking complexity in an abstract, general purpose way. The result is <strong>libp2p</strong>: a framework for simplifying networking with P2P applications. Developers decide on how they want their app to interop with others in the network, favoring configuration and extensibility instead of assumptions about networking setup. The goal is to enable rapid development of P2P applications for everyone.
+
+ p <strong>We are still actively developing libp2p, so expect the specification to change.</strong>
+
+ h2 Goals and Requirements
  p Our goals for libp2p specification and its implementations are:
  ul
  li Enable the use of various transports (TCP, UDP, DTLS, uTP, etc)
@@ -40,8 +38,19 @@ block content
  li Use the current network technologies to its best capability
  li Have NAT Traversal
  li Enable connections to be relayed
- li Enable encrypted channels 
+ li Enable encrypted channels
+
+ h2 Specifications and Implementations <small>(note: work in progress!)</small>
+ ul
+ li
+ a(href="https:/ipfs/specs/tree/master/protocol/network") Specification
+ li
+ a(href="https:/diasdavid/js-libp2p") Node.js / browser implementation
+ li
+ a(href="https:/ipfs/go-libp2p") Golang implementation
+
+ h2 IRC
+ ul
+ li You can find us at #ipfs on Freenode.
 
- h2 Usage examples
- pre From Readmes and so on
  .col-md-2

src/public/index.html

@@ -6,34 +6,30 @@
  </head>
  <body>
  <div class="row">
- <div class="col-md-2"> </div>
+ <div class="col-md-2"></div>
  <div class="col-md-8"><img src="https://raw.githubusercontent.com/diasdavid/specs/libp2p-spec/protocol/network/figs/logo.png">
- <h1>A multiprotocol aware networking suite</h1>
+ <h1>A network framework for decentralized P2P application development</h1>
  </div>
  <div class="col-md-2"></div>
  </div>
  <hr>
  <div class="row">
  <div class="col-md-2">
- <ul>
- <li>Home</li>
- <li>Goals</li>
- <li>Requirements</li>
- <li>Usage Examples</li>
- <li><a href="/ready.html">is libp2p ready?</a></li>
- </ul>
+ <!--
+ ul
+ li Home
+ li Goals
+ li Requirements
+ li Usage Examples
+ li
+ a(href="/ready.html") is libp2p ready?
+ -->
  </div>
  <div class="col-md-8">
- <h2>Welcome!</h2>
- <p>With the developement of building IPFS, the InterPlanetary FileSystem[?], we came to learn about the several challenges imposed by having to run a distributed file system on top of heterogeneous devices, with diferent network setups and capabilities. During this process, we had to revisit the whole network stack and elaborate solutions to overcome the obstacles imposed by design decisions of the several layers and protocols, without breaking compatibility or recreating technologies.</p>
- <p>In order to build this library, we focused on tackling problems independently, creating less complex solutions with powerful abstractions, that when composed, can offer an environment for a Peer-to-Peer application to work sucessfuly.</p>
- <p>`libp2p` is the result of the collective experience while building a distributed system, that puts the responsability on the developers on how they want their app to interop with others in the network, favoring configuration and extensibility instead of assumptions about how the network setup.</p>
- <p>In essence, a peer using libp2p should be able to communicate with another peer using different transports, including connection relay, and talk over different protocols, negotiated in demand.</p>
- <p>
-
- The full specification for libp2p is a working process that can be found on <a href="https:/ipfs/specs/pull/19">ipfs/specs</a>
- </p>
- <h2>Goals and Requirements </h2>
+ <p>While developing <a href="https://ipfs.io">IPFS</a>, we came to learn about the several challenges imposed by having to run a distributed file system on top of heterogeneous devices, with diferent network setups and capabilities. During this process, we had to constantly revisit the whole network stack and create solutions to overcome the obstacles imposed by design decisions of the several layers and protocols, without breaking compatibility or recreating technologies. This was a tedious, time consuming process.</p>
+ <p>Instead of re-inventing the wheel every time we need to build a decentralized P2P application, we focused on streamlining the problem by tackling networking complexity in an abstract, general purpose way. The result is <strong>libp2p</strong>: a framework for simplifying networking with P2P applications. Developers decide on how they want their app to interop with others in the network, favoring configuration and extensibility instead of assumptions about networking setup. The goal is to enable rapid development of P2P applications for everyone.</p>
+ <p><strong>We are still actively developing libp2p, so expect the specification to change.</strong></p>
+ <h2>Goals and Requirements</h2>
  <p>Our goals for libp2p specification and its implementations are:</p>
  <ul>
  <li>Enable the use of various transports (TCP, UDP, DTLS, uTP, etc)</li>
@@ -45,10 +41,18 @@ <h2>Goals and Requirements </h2>
  <li>Use the current network technologies to its best capability</li>
  <li>Have NAT Traversal</li>
  <li>Enable connections to be relayed</li>
- <li>Enable encrypted channels </li>
+ <li>Enable encrypted channels</li>
+ </ul>
+ <h2>Specifications and Implementations <small>(note: work in progress!)</small></h2>
+ <ul>
+ <li><a href="https:/ipfs/specs/tree/master/protocol/network">Specification</a></li>
+ <li><a href="https:/diasdavid/js-libp2p">Node.js / browser implementation</a></li>
+ <li><a href="https:/ipfs/go-libp2p">Golang implementation</a></li>
+ </ul>
+ <h2>IRC</h2>
+ <ul>
+ <li>You can find us at #ipfs on Freenode.</li>
  </ul>
- <h2>Usage examples</h2>
- <pre>From Readmes and so on</pre>
  </div>
  </div>
  <div class="col-md-2"></div>

versions

@@ -44,3 +44,4 @@ QmQjFqrJ55hhTDTSfSJ1UQZ3VW3xmAD6DSBLBNvnCW4tQ6
 QmNQRxp5VGMaws1Q5fyctnEogWZEWGD1PARKeJAVazzTTS
 QmTBGcHZxcisgAr9NQHtEv6szvcaU74sC5VnpsVE45akwF
 QmU6gztSrDCbYC5DEj5KUBge4HimwaqpgVdsh8TcYuaPEv
+QmSMDe7G2meu3RhnDyJi31dfMszz9r1acdQuAyXDYnGxWY