Awesome
py-ipfs
Python implementation of IPFS
Python implementation of IPFS, the InterPlanetary File System. Not even remotely done yet.
For the current status, and where you can help, please see issue 49.
Table of Contents
Background
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.
IPFS could become 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.
<!-- ### Organization This repository contains the Python package `ipfs`, which contains the subpackages `block`, `merkledag`, `naming`, and `routing`, which function as laid out in [the main IPFS repo](http://github.com/ipfs/ipfs) The repo roughly looks like this:: ipfs ├─ block ├─ merkledag ├─ naming ├─ network └─ routing -->Install
Not ready for prime time yet
Usage
Also not ready for prime time yet
Documentation
To build the Sphinx docs, execute:
$ make -C docs/ <your favorite docs format> # html, pdf etc.
Contribute
IPFS implementation in Python is a work in progress. As such, there's a few things you can do right now to help out:
- Get in touch! You can find us on #py-ipfs on chat.freenode.org!
- A Matrix chat option is also provided. Please note however that, at the time of writing, the default
matrix.orgserver is severely overloaded and your messages may only arrive with extreme delay; using a different homeserver is hence highly recommended.
- A Matrix chat option is also provided. Please note however that, at the time of writing, the default
- Check out issue 49 for an up-to-date list (maintained by @alexander255) of tasks that could use your help. Feel free to ask questions on that and we'll try to help. Be sure to drop a note if there is anything you'd like to work on and we'll update the issue to let others know.
- Perform code reviews. More eyes will help a) speed the project along b) ensure quality and c) reduce possible future bugs.
- Take a look at both go-ipfs and js-ipfs (which we intend to follow to a point), and also at some of the planning repositories or issues: for instance, the libp2p spec here. Contributions here that would be most helpful are top-level comments about how it should look based on our understanding. Again, the more eyes the better.
- Add tests. There can never be enough tests.
- Contribute to the FAQ repository with any questions you have about IPFS or any of the relevant technology. A good example would be asking, "What is a merkledag tree?". If you don't know a term, odds are someone else doesn't either. Eventually, we should have a good understanding of where we need to improve communications and teaching together to make IPFS and IPN better.
- TODO: write our own
CONTRIBUTE.mdsimilar to IPFS's and once we know what we're doing and who's doing it.
Please be aware that all interactions related to IPFS, libp2p and Multiformats are subject to the IPFS Code of Conduct.