Add blog: Distributed Wikipedia Mirror Update

.forestry/front_matter/templates/blog-post.yml

@@ -149,10 +149,12 @@ fields:
     need to add a new tag, please <a href="https://github.com/ipfs/ipfs-blog/issues"
     target="_blank">file an issue</a> with the details.
 pages:
+- src/_blog/2021-05-31-distributed-wikipedia-mirror-update.md
 - src/_blog/announcing-js-ipfs-0.53.0.md
 - src/_blog/audius-uses-ipfs-for-content-streaming-storage-to-empower-artists-creators-worldwide.md
 - src/_blog/congrats-gitcoin-grants-round-9-winners.md
 - src/_blog/decentralized-games-at-gamedev.js-jam-2021.md
+- src/_blog/decentralizing-infrastructure-during-scaling-ethereum.md
 - src/_blog/go-ipfs-0.8.0-and-remote-pinning-is-here.md
 - src/_blog/hey-ethdenver-hack-on-ipfs-with-these-bounties.md
 - src/_blog/how-we-put-ipfs-in-brave.md

src/_blog/2021-05-31-distributed-wikipedia-mirror-update.md

@@ -0,0 +1,115 @@
+---
+title: Distributed Wikipedia Mirror Update
+description: Status update for 2021 Q2, usage instructions, current build process,
+  and open problems.
+author: Marcin Rataj
+date: 2021-05-31
+permalink: "/2021-05-31-distributed-wikipedia-mirror-update/"
+translationKey: ''
+header_image: "/wikipedia-mirrors-2021-q2-1.png"
+tags:
+- censorship
+
+---
+* [Distributed Wikipedia Mirror](https://github.com/ipfs/distributed-wikipedia-mirror#readme) and [Kiwix](https://kiwix.org/) projects are happy to the announce **general availability** of **updated** [English](https://en.wikipedia-on-ipfs.org/) and [Turkish](https://tr.wikipedia-on-ipfs.org) mirrors, along with **new languages**: [Myanmar](https://my.wikipedia-on-ipfs.org/), [Arabic](https://ar.wikipedia-on-ipfs.org), [Chinese](https://zh.wikipedia-on-ipfs.org) and [Russian](https://ru.wikipedia-on-ipfs.org).
+* A handy, up-to-date list can be found at [ipfs.kiwix.org](ipfs.kiwix.org), and in the [`snapshot-hashes.yml`](https://github.com/ipfs/distributed-wikipedia-mirror/blob/main/snapshot-hashes.yml  "snapshot-hashes.yml") manifest.
+* The idea of a distributed Wikipedia mirror goes back to 2017, when the IPFS Project created a snapshot of English and Turkish languages and put it on IPFS.  To learn why we did it, please read the original [Uncensorable Wikipedia on IPFS](https://blog.ipfs.io/24-uncensorable-wikipedia/) post.
+* Below is a short status update with improved usage instructions, current build process, open problems, and future work that could be contributed to the project.
+
+## Improved access to Wikipedia mirrors
+
+### User-friendly `ipns://{dnslink}` and public gateways
+
+Browsers with built-in support for IPFS addresses ([Brave](https://brave.com/brave-integrates-ipfs/), [Opera](https://blog.ipfs.io/2020-03-30-ipfs-in-opera-for-android/), or a regular [Firefox](https://www.mozilla.org/en-US/firefox/new/), [Chromium](https://en.wikipedia.org/wiki/Chromium_(web_browser)) with [IPFS Companion](https://github.com/ipfs/ipfs-companion#readme)) can now load the latest snapshot using [DNSLink](https://docs.ipfs.io/concepts/dnslink/):
+
+* `ipns://{dnslink}`
+* `ipns://en.wikipedia-on-ipfs.org`
+
+To ensure true P2P transport, offline storage and content integrity, you can run your own IPFS node ([command-line](https://docs.ipfs.io/install/command-line/) or  [IPFS Desktop](https://docs.ipfs.io/install/ipfs-desktop/) app) combined with the [IPFS Companion](https://docs.ipfs.io/install/ipfs-companion/) browser extension. You can also use the [Brave browser, which has built-in support for IPFS](https://brave.com/brave-integrates-ipfs/):
+
+@[youtube](jTDkTQiKzJA)
+
+When it is not possible to run your own IPFS node, one of the [many public gateways](https://ipfs.github.io/public-gateway-checker/) can be used as a proxy for accessing the mirror. For example:
+
+* [https://dweb.link/ipns/my.wikipedia-on-ipfs.org](https://dweb.link/ipns/my.wikipedia-on-ipfs.org)
+* [https://cf-ipfs.com/ipns/my.wikipedia-on-ipfs.org](https://cf-ipfs.com/ipns/my.wikipedia-on-ipfs.org)
+
+### Robust and immutable `ipfs://{cid}`
+
+If DNS resolution is blocked, or a public gateway can't be trusted, accessing the immutable snapshot using underlying cryptographic content identifier ([CID](https://docs.ipfs.io/concepts/content-addressing/)) is advised:
+
+* `ipfs://{cid}`
+
+The `{cid}` of a specific mirror can be found in [`snapshot-hashes.yml`](https://github.com/ipfs/distributed-wikipedia-mirror/blob/main/snapshot-hashes.yml), or read from its DNSLink record with`ipfs resolve -r /ipns/en.wikipedia-on-ipfs.org`. At the time of writing this post, the English mirror points at    `ipfs://bafybeiaysi4s6lnjev27ln5icwm6tueaw2vdykrtjkwiphwekaywqhcjze`
+
+Sharing CIDs via [sneakernet](https://en.wikipedia.org/wiki/Sneakernet) is a popular way of routing around DNS issues and censorship. Turkish citizens resorted to that in 2017 when [Turkey blocked Wikipedia](https://en.wikipedia.org/wiki/Block_of_Wikipedia_in_Turkey).  History does not repeat itself, but it rhymes: Myanmar started experiencing internet blackouts earlier this year:
+
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Confirmed: <a href="https://twitter.com/hashtag/Myanmar">#Myanmar</a> has blocked all language editions of the Wikipedia online encyclopedia, part of a widening post-coup internet censorship regime imposed by the military junta 📚<br><br>Network data show restriction in effect on major providers.<br><br>📰 Report: <a href="https://t.co/Jgc20OBk27">https://t.co/Jgc20OBk27</a> <a href="https://t.co/qstGEefO4E">pic.twitter.com/qstGEefO4E</a></p>— NetBlocks (@netblocks) <a href="https://twitter.com/netblocks/status/1362814793502097409">February 19, 2021</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+To address this critical need, we [created a mirror of Myanmar Wikipedia](https://github.com/ipfs/distributed-wikipedia-mirror/pull/83) and [shared both DNSLink and CID](https://github.com/ipfs/distributed-wikipedia-mirror/pull/83#issuecomment-786021082).
+
+<blockquote class="twitter-tweet"><p lang="en" dir="ltr">In response to ongoing internet restrictions / censorship in Myanmar, <a href="https://twitter.com/Wikipedia?ref_src=twsrc%5Etfw">@Wikipedia</a> in MY is now on <a href="https://twitter.com/IPFS?ref_src=twsrc%5Etfw">@IPFS</a>:<a href="https://t.co/trt0AbEMuW">https://t.co/trt0AbEMuW</a><br><br>Huge props to <a href="https://twitter.com/playingwithsid?ref_src=twsrc%5Etfw">@playingwithsid</a> who proposed it, & coordinated w/ native speakers.<br><br>Epic implementation effort by <a href="https://twitter.com/lidelOrg?ref_src=twsrc%5Etfw">@lidelOrg</a> & Kelson of <a href="https://twitter.com/KiwixOffline?ref_src=twsrc%5Etfw">@KiwixOffline</a>!</p>— dietrich (@dietrich) <a href="https://twitter.com/dietrich/status/1364978192075866115?ref_src=twsrc%5Etfw">February 25, 2021</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+## How to help co-hosting this?
+
+You can run your own IPFS node and co-host a subset of Wikipedia, store a full copy, or even follow collaborative cluster to pull in future updates automatically.
+
+It is also possible to donate co-hosting costs by pinning specific CID to a remote service.
+
+### Lazy co-hosting with your own IPFS node
+
+It is possible to keep a lazy-loaded copy.  which does not fetch the entire Wikipedia, but keeps the browsed subset of pages around.
+
+    $ ipfs files cp /ipfs/{cid} /my-wikipedia-snapshot
+
+One can convert a lazy copy to full one by recursively pinning the [DAG](https://docs.ipfs.io/concepts/glossary/#dag) behind a CID:
+
+    $ ipfs pin add --progress {cid}
+
+A recursive pin will preload the entire mirror to the local datastore.
+Be wary that the English one is far bigger than other ones, and pinning it requires hundreds of gigabytes and may take a very long time.
+
+The size of a specific mirror can be read with `ipfs files stat /ipfs/{cid}`.
+
+### Collaborative cluster
+
+This is an advanced option aimed at server administrators and power users. The `wikipedia` cluster includes all language versions and its size only grows over time.
+
+    $ ipfs-cluster-follow wikipedia run --init wikipedia.collab.ipfscluster.io
+
+See _Instructions_ at [collab.ipfscluster.io](collab.ipfscluster.io).
+
+### Donate remote pins
+
+When co-hosting with your own IPFS node is not possible, one can still help by pinning snapshot CIDs to a remote pinning service.    
+ [Learn how to _work with remote pinning services_](https://docs.ipfs.io/how-to/work-with-pinning-services/).
+
+## How is a mirror built?
+
+The current setup relies on [Wikipedia snapshots in the ZIM format](https://download.kiwix.org/zim/wikipedia/) produced by the [Kiwix](https://kiwix.org/) project.
+
+We don't have a web-based reader of ZIM archives (yet – more in the next section), and the way we produce a mirror is an elaborate, time-consuming process:
+
+1. Unpacking ZIM archive with [openzim/zim-tools](https://github.com/openzim/zim-tools)
+2. Adjusting HTML/CSS/JS to fixup unpacked form
+3. Import snapshot to IPFS
+4. Include original ZIM inside of unpacked IPFS snapshot
+
+While this works, the need for unpacking and customizing the snapshot makes it difficult to reliably produce updates. And including the original ZIM for use with [Kiwix offline reader](https://www.kiwix.org/en/kiwix-reader), partially duplicates the data.
+
+We would love to mirror more languages, and increase the update cadence, but for that to happen we need to remove the need for unpacking ZIM archives. 
+
+We will be looking into putting [all ZIMs from Kiwix](https://download.kiwix.org/zim/wikipedia/) on IPFS and archiving them for long term storage on [Filecoin](https://filecoin.io/) as part of [farm.openzim.org ](https://farm.openzim.org )pipeline.
+
+## Help Wanted and Open Problems
+
+If you are still reading this, there is a high chance you are interested in improving the way the distributed Wikipedia mirror works.
+
+Below are areas that could use a helping hand, and ideas looking for someone to explore them.
+
+* **Search.** There's no search function currently. Leveraging the index present in ZIM, or building a DAG-based search index optimized for use in web browsers would make existing mirrors more useful. See [distributed-wikipedia-mirror/issues/76](https://github.com/ipfs/distributed-wikipedia-mirror/issues/76).
+* **Web-based ZIM reader.** The biggest impact for the project would be to create a web-based reader capable of browsing original ZIM archives without the need for unpacking them, nor installing any dedicated software. Want to help make it a reality? See [kiwix-js/issues/659](https://github.com/kiwix/kiwix-js/issues/659)
+* **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?

src/_blog/decentralizing-infrastructure-during-scaling-ethereum.md

@@ -0,0 +1,76 @@
+---
+title: Decentralizing infrastructure during Scaling Ethereum
+description: 'Announcing the winners from ETHGlobal’s Scaling Ethereum hackathon event.'
+author: PL Hackathon Team
+date: 2021-05-26
+permalink: "/2021-05-26-scaling-ethereum-recap/"
+translationKey: 2021-05-26-scaling-ethereum-recap
+header_image: "/2021-04-14-cardheader-scaling-ethereum-1459531d.png"
+tags:
+- recap
+- hackathon
+
+---
+An endeavour to collaborate on creating a powerful foundation for the future of the Ethereum community, [Scaling Ethereum](https://scaling.ethglobal.co/), has come to a close, resulting in some innovative and inspiring solutions. The IPFS and Filecoin projects, alongside the ETHGlobal team, sponsored this 4-week hackathon event.
+
+We put up $7500 in Filecoin across various scaling areas to award to those brave and intrepid souls willing to rise to the challenge!
+
+## Our challenges + winners
+
+### 💮 NFT Metadata Updater
+
+Mo minting, mo problems. Best method for managing signed permissioned and timestamped updates to NFT metadata stored on IPFS via any L2 chain.
+
+Winner: [Nama Finance]()
+
+A decentralized one-stop-shop data manager for meta creators.
+
+@[youtube](7MdRDDK-T3M)
+
+### ⛵️ Sailing the Sea of CIDs
+
+You’re publishing everything to IPFS by default now, but… dude, where’s my stuff? Best tool, service, website or library for working with large collections of IPFS CIDs.
+
+Winner: [Hashmark]()
+
+Hashmark is like Instapaper, but for NFTs. It’s the simplest way to view and bookmark NFTs.
+
+@[youtube](9dccga2yQxg)
+
+Winner: [IPFS-CIDSail](https://hack.ethglobal.co/showcase/ipfs-cidsail-recHTKp8X5ddxI4FK)
+
+A command line utility that helps you find/check/keep track of your files published on IPFS.
+
+@[youtube](Uzt0bA6s444)
+
+Winner: [HydroFile](https://hack.ethglobal.co/showcase/hydrofile-recobwnZCxJ50qpoo)
+
+An automated way to keep track of IPFS CIDs – sail the seas of CIDs!
+
+@[youtube](zuRjzrqozUs)
+
+Winner: [DVHDB](https://hack.ethglobal.co/showcase/vhddb-video-hash-distributed-data-base-recIXMgkcMXnpSabe) - Distributed Video Hash Database
+
+A collaborative and distributed database of video hashes.
+
+@[youtube](hcHhkKUsqSk)
+
+Congrats to all of the projects who participated during Scaling Ethereum, and thank you to our prize winners for their great work!
+
+See all of the Scaling Ethereum projects in [the official showcase](https://showcase.ethglobal.co/scaling).
+
+## Talks + workshops
+
+The Protocol Labs team gave two talks at the event:
+
+### Pre-event talk: Deploying Web3: IPFS Architectures, Topologies and Menageries with Dietrich Ayala
+
+@[youtube](13rHbWCYNWA)
+
+### SNARKs Summit: Scaling zkSNARKSs to meet the demands of Filecoin with Friedel Ziegelmayer
+
+@[youtube](GRaR8N380h0)
+
+## Want to get involved in a future hackathon?
+
+Follow us on Twitter at [@IPFS](https://twitter.com/ipfs) or [@Filecoin](https://twitter.com/filecoin). You can also subscribe to the [IPFS weekly newsletter](https://ipfs.us4.list-manage.com/subscribe?u=25473244c7d18b897f5a1ff6b&id=cad54b2230), or the [Filecoin monthly](https://filecoin.us16.list-manage.com/subscribe?u=a1dfb670c4f1fb042e82a1f1d&id=cf409026a0). Or, join us in chat in the [Filecoin Slack](http://filecoin.io/slack) or the [IPFS Discord](https://discord.com/invite/vZTcrFePpt). We’ll see you there! 👋

src/_blog/events.md

@@ -4,6 +4,14 @@ type: Event
 sitemap:
   exclude: true
 data:
+- title: Web3 Weekend
+  date: 2021-05-28
+  publish_date: 2021-05-24T12:00:00+00:00
+  path: https://web3.ethglobal.co/
+  card_image: "/2021-05-24-cardheader-web3-weekend.png"
+  tags:
+  - community
+  - hackathon
 - title: 'DI2F: Decentralizing the Internet with IPFS and Filecoin'
   date: 2021-06-21
   publish_date: