From fb4d41bcd4351085a5a624951e785697a311f022 Mon Sep 17 00:00:00 2001 From: Kyle Drake Date: Mon, 23 Nov 2015 12:08:18 -0800 Subject: [PATCH] some copy changes, comment out unused links --- src/pages/index.jade | 53 +++++++++++++++++++++++++------------------ src/public/index.html | 48 +++++++++++++++++++++------------------ versions | 1 + 3 files changed, 58 insertions(+), 44 deletions(-) diff --git a/src/pages/index.jade b/src/pages/index.jade index 432f1a0..3d12f3c 100644 --- a/src/pages/index.jade +++ b/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://github.com/ipfs/specs/pull/19") ipfs/specs - - h2 Goals and Requirements + p While developing IPFS, 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 libp2p: 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 We are still actively developing libp2p, so expect the specification to change. + + 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 (note: work in progress!) + ul + li + a(href="https://github.com/ipfs/specs/tree/master/protocol/network") Specification + li + a(href="https://github.com/diasdavid/js-libp2p") Node.js / browser implementation + li + a(href="https://github.com/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 diff --git a/src/public/index.html b/src/public/index.html index a979f16..27f6d6c 100644 --- a/src/public/index.html +++ b/src/public/index.html @@ -6,34 +6,30 @@
-
+
-

A multiprotocol aware networking suite

+

A network framework for decentralized P2P application development

- +
-

Welcome!

-

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.

-

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.

-

`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.

-

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.

-

- - The full specification for libp2p is a working process that can be found on ipfs/specs -

-

Goals and Requirements

+

While developing IPFS, 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.

+

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 libp2p: 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.

+

We are still actively developing libp2p, so expect the specification to change.

+

Goals and Requirements

Our goals for libp2p specification and its implementations are:

  • Enable the use of various transports (TCP, UDP, DTLS, uTP, etc)
    • @@ -45,10 +41,18 @@

    Goals and Requirements

  • Use the current network technologies to its best capability
  • Have NAT Traversal
  • Enable connections to be relayed
    • -
  • Enable encrypted channels
    • +
  • Enable encrypted channels
    • +
+

Specifications and Implementations (note: work in progress!)

+ +

IRC

+
    +
  • You can find us at #ipfs on Freenode.
-

Usage examples

- 
From Readmes and so on
diff --git a/versions b/versions index 90c7f38..52c5594 100644 --- a/versions +++ b/versions @@ -44,3 +44,4 @@ QmQjFqrJ55hhTDTSfSJ1UQZ3VW3xmAD6DSBLBNvnCW4tQ6 QmNQRxp5VGMaws1Q5fyctnEogWZEWGD1PARKeJAVazzTTS QmTBGcHZxcisgAr9NQHtEv6szvcaU74sC5VnpsVE45akwF QmU6gztSrDCbYC5DEj5KUBge4HimwaqpgVdsh8TcYuaPEv +QmSMDe7G2meu3RhnDyJi31dfMszz9r1acdQuAyXDYnGxWY