This IPFS-related repository has been archived, and all issues are therefore frozen. If you want to ask a question or open/continue a discussion related to this repo, please visit the official IPFS forums.
We archive repos for one or more of the following reasons:
- Code or content is unmaintained, and therefore might be broken
- Content is outdated, and therefore may mislead readers
- Code or content evolved into something else and/or has lived on in a different place
- The repository or project is not active in general
Please note that in order to keep the primary IPFS GitHub org tidy, most archived repos are moved into the ipfs-inactive org.
If you feel this repo should not be archived (or portions of it should be moved to a non-archived repo), please reach out and let us know. Archiving can always be reversed if needed.
A collection of descriptions for terms related to ipfs and surrounding techs
These terms are not yet defined, but have been suggested as good terms to work on. Please define them if you can!
IPLD, IPNS, IPRS, cbor, starlog, starship, solarnet, DHT (Distributed Hash Table), merkle-dag, Fuse
A set of rules describing how to communicate
A way of generating a unique name for a piece of data
Mutable filesystem (see also: FUSE)
Querying the DHT for random keys, in order to discover new peers and fill gaps in keyspace
TCP is a protocol that is used for a huge portion of web traffic. It guarantees that information arrives entirely and in order.
UDP is a protocol that does not have the same guarantees as TCP. Data sent can go missing, or arrive in the wrong order.
TODO
Merkle-dag based data structures for representing unix files, directories, and symlinks
Feel free to join in. Just edit this main README file in a PR, or open an issue!
This repository falls under the IPFS Code of Conduct.
