ipfs / ipfs
- пятница, 25 марта 2016 г. в 02:14:14
228 stars today
IPFS - The Permanent Web
Welcome to IPFS! Why not watch a video demo to get started?
IPFS (the InterPlanetary File System) is a new hypermedia distribution protocol, addressed by content and identities. IPFS enables the creation of completely distributed applications. It aims to make the web faster, safer, and more open.
IPFS is a distributed file system that seeks to connect all computing devices with the same system of files. In some ways, this is similar to the original aims of the Web, but IPFS is actually more similar to a single bittorrent swarm exchanging git objects. You can read more about its origins in the paper IPFS - Content Addressed, Versioned, P2P File System.
IPFS is becoming a new major subsystem of the internet. If built right, it could complement or replace HTTP. It could complement or replace even more. It sounds crazy. It is crazy.
Want to see more? Check out Juan Benet's talk at Sourcegraph - IPFS: The Permanent Web.
IPFS is a protocol:
IPFS is a filesystem:
IPFS is a web:
http://ipfs.io/<path>
ipfs://
directlyIPFS is modular:
IPFS uses crypto:
IPFS is p2p:
IPFS is a cdn:
IPFS has a name service:
To learn more about how IPFS works take a look at the Papers or Talks. You can also explore the Specs in writing.
This is a short selection of introductory talks. In time we will collect more here.
The IPFS project seeks to evolve the infrastructure of the Internet and the Web, with many things we've learned from successful systems, like Git, BitTorrent, Kademlia, Bitcoin, and many, many more. This is the sort of thing that would have come out of ARPA/DARPA/IETF/BellLabs in another age. IPFS is a Free Open Source project, with hundreds of contributors.
Please note that IPFS is a work in progress. It is an ambitious plan to make the internet more free, open, secure, and high performance. It builds on the good ideas of numerous battle-tested distributed systems.
Today, there is one main IPFS Protocol implementation (in Go) with more on the way (Javascript, and Python).
In February of 2015, the go-ipfs implementation was released as an "Alpha Distribution". Since then, go-ipfs has been making regular releases on the road towards Beta. Both js-ipfs and py-ipfs are in progress.
For an in-depth tutorial, see a Hands on Introduction.
The IPFS protocol and its implementations are still in heavy development. This means that there may be problems in our protocols, or there may be mistakes in our implementations. And -- though IPFS is not production-ready yet -- many people are already running nodes in their machines. So we take security vulnerabilities very seriously. If you discover a security issue, please bring it to our attention right away!
If you find a vulnerability that may affect live deployments -- for example, by exposing a remote execution exploit -- please send your report privately to security@ipfs.io. Please DO NOT file a public issue.
If the issue is a protocol weakness that cannot be immediately exploited or something not yet deployed, just discuss it openly.
The IPFS Project is now very large, with hundreds of contributors in our community. You are invited to join it! Here are some links to our communication channels:
You can also find our community on:
The IPFS Project is big -- there are many efforts subprojects and related efforts. We will document the core efforts here, though look around. The space is exploding and lots of new projects are springing up all the time.
For a community-curated lists of awesome projects using IPFS, check out awesome-ipfs!
Language | Project | Completeness |
---|---|---|
Go | https://github.com/ipfs/go-ipfs | reference |
Javascript | https://github.com/ipfs/js-ipfs | incomplete |
Python | https://github.com/ipfs/py-ipfs | starting |
If you would you like to start your own language implementation of IPFS, check out the IPFS Implementation Guide, and the Specifications. The specs are still evolving, but the core formats are stable and can be built on. Make sure to post an issue if you would like to start an effort, as many people have expressed interest in contributing to new implementations.
Language | Client Library | Completeness |
---|---|---|
Go | https://github.com/ipfs/go-ipfs-api | |
Java | https://github.com/ipfs/java-ipfs-api | |
Javascript | https://github.com/ipfs/js-ipfs-api | |
Python | https://github.com/ipfs/python-ipfs-api | |
Scala | https://github.com/ipfs/scala-ipfs-api | |
Haskell | https://github.com/davidar/hs-ipfs-api | |
Swift | https://github.com/ipfs/swift-ipfs-api | |
CommonLisp | https://github.com/WeMeetAgain/cl-ipfs-api | |
Rust | https://github.com/rschulman/rust-ipfs-api | |
Ruby | https://github.com/Fryie/ipfs-ruby | |
Swift | https://github.com/NeoTeo/ipfs-osx-service | |
PHP | https://github.com/cloutier/php-ipfs-api | |
C# | https://github.com/richardschneider/net-ipfs-api | |
C/C++ | contact: @PayasR | 0% |
Julia | contact: @rened | 0% |
Lua | contact: @seclorum | 0% |
Erlang | ! | 0% |
Objective C | ! | 0% |
Please help by contributing to one of the above client libraries. If you would like to create another, please see the IPFS API Client Implementation Guide, and tell us so we can help!
This aims to be a directory of all the various repos in the IPFS Github Organization, and other closely related things.
Ref Lists
We encourage and support IPFS Meetups, please let us know if you would like to start one. Feel free to organize yourself through the Community discussions and to advertise events in the main repository.
Installing
Other
Many more exist, but we will endeavor to find them and add them here.