Update from Forestry.io

Marcin Rataj updated src/_blog/2021-05-31-distributed-wikipedia-mirror-update.md
This commit is contained in:
Marcin Rataj
2021-06-01 10:53:06 +00:00
committed by Forestry.io
parent 51a4d9f3ce
commit 4872c75aa6
@@ -77,7 +77,7 @@ This is an advanced option aimed at server administrators and power users. The `
$ ipfs-cluster-follow wikipedia run --init wikipedia.collab.ipfscluster.io
See _Instructions_ at [collab.ipfscluster.io](collab.ipfscluster.io).
See _Instructions_ at [collab.ipfscluster.io](https://collab.ipfscluster.io#instructions).
### Donate remote pins
@@ -112,4 +112,4 @@ Below are areas that could use a helping hand, and ideas looking for someone to
* **Improving the way ZIM is represented on IPFS.** When we store an original ZIM on IPFS, the DAG is produced by `ipfs add --cid-version 1`. This works fine, but with additional research on customizing DAG creation, we may improve deduplication and speed when doing range requests for specific bytes. There are different stages to explore here: if any of them sounds interesting to you, please comment in [distributed-wikipedia-mirror/issues/42](https://github.com/ipfs/distributed-wikipedia-mirror/issues/42).
* Stage 1: Invest some time to benchmark parameter space to see if low hanging fruits exists.
* Stage 2: Create a DAG builder that understands ZIM format and maximizes deduplication of image assets by representing them as sub-DAGs with dag-pb files.
* Stage 3: Research augmenting or replacing ZIM with [IPLD](https://ipld.io/). How can we maximize block deduplication across all snapshots and languages? How would an IPLD-based search index work?
* Stage 3: Research augmenting or replacing ZIM with [IPLD](https://ipld.io/). How can we maximize block deduplication across all snapshots and languages? How would an IPLD-based search index work?