Skip to content
This repository was archived by the owner on Jun 2, 2020. It is now read-only.
This repository was archived by the owner on Jun 2, 2020. It is now read-only.

[NEW CONTENT] [BOUNTY] Glossary #56

Closed
@Mr0grog

Description

@Mr0grog

This issue has a bounty!

Successfully closing this issue by producing a production-ready piece of documentation can earn you not only the undying love of the IPFS community — it can net you a financial reward. See the current list of bounty issues and their values here.

The need in brief

Create a glossary that provides a brief and clear definition of major concepts in IPFS, plus links to longer explainers when they exist. Note that we will be pulling these definitions into hover-style tool tips in the future, so please keep definitions fairly brief and written in such a way that the first n characters can be excerpted into a complete tool tip.

Regarding future use in tool tips: Visual design work has already been done on this effort. Please see #372 for mockups and resulting discussion; it'll help you determine how best to proceed with excerpting tool-tip content.

Below are initial terms to seed with. Please add others as you see fit. See as well prior art for “concepts and terms that trip people up”.

  • DWeb
  • DHT
  • Graph
  • DAG
  • Merkle Tree/DAG
  • Merkle “Forest”
  • Hash
  • Gateway
  • Pinning
  • Transport
  • Swarm
  • Information Space
  • MFS
  • UnixFS (lots of confusion out there on whether this is the same or different from MFS)
  • (Cryptographic) Signing
  • Peer
  • Peer ID
  • CRDT
  • Repo
  • DataStore
  • Node, Daemon
  • CID (v0, v1, …)
  • Path/Address
  • DNSLink
  • CBOR
  • Bitswap
  • Blocks
  • Bootstrap Node
  • Listening
  • Dialing
  • Announcing
  • Relay
  • GC/Garbage Collection
  • Pubsub
  • Filestore
  • IPLD (and selectors)
  • Libp2p
  • Multihash
  • IPNS
  • SFS
  • Blockchain
  • Bittorrent
  • GraphSync
  • pubsub
  • filestore
  • IPLD
  • Libp2p
  • multihash
  • IPNS
  • SFS
  • Blockchain
  • Bittorrent
  • IPLD Selectors
  • GraphSync

Deliverable

Content should take the form of a Markdown document. File locations should be as follows:

Guidelines

  • Please use the IPFS Docs Contributor Guidelines as your north star — adherence to these guidelines are crucial when it comes to awarding potential bounty!
  • Also, please keep in mind our core user personae. If a piece of content serves one or more personae in particular, make sure it checks out with that persona's attributes.

Metadata

Metadata

Labels

P3Low: Not priority right nowdif/easySomeone with a little familiarity can pick upeffort/daysEstimated to take multiple days, but less than a weekhelp wantedSeeking public contribution on this issuetopic/design-contentContent design, writing, information architecturetopic/docsDocumentation

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions