@tabcat/zzzync
Version:
replication protocol over IPLD, IPNS, and IPFS Provider Records
36 lines (22 loc) • 1.26 kB
Markdown
# 💤<sub><sup>ync</sup></sub>
<span>
<a href="https://static.sfdict.com/audio/Z00/Z0026700.mp3" target="_blank" rel="noopener noreferrer">
<img src="https://camo.githubusercontent.com/b900202928a33c7574d271fb0ef74b60036da10fe81079709e87b86b939ed8e7/68747470733a2f2f6475636b6475636b676f2e636f6d2f6173736574732f69636f6e732f706c61792d627574746f6e2e737667" />
</a>
zĭngk
</span>
<br/>
<br/>
sync with peers that have gone to sleep 😴
***
<br/>
Zzzync uses [IPLD](https://ipld.io/), [IPNS](https://docs.ipfs.tech/concepts/ipns/), and [Provider Records](https://docs.ipfs.tech/concepts/dht/) to replicate dynamic content over IPFS. Read about the design in [tabcat/dynamic-content](https://github.com/tabcat/dynamic-content).
IPLD is used to store replica data
IPNS is used to point to the latest version of a collaborator's local replica
Provider Records are used to find the [peerIDs](https://docs.libp2p.io/concepts/fundamentals/peers/#peer-id) of collaborators, which can be turned into IPNS names
## API Docs
<https://tabcat.github.io/zzzync/>
## Spec
<https://github.com/tabcat/zzzync/blob/master/spec.md>
***
This work is being funded as part of a [grant](https://github.com/tabcat/rough-opal) by [Protocol Labs](https://protocol.ai)