feat: shipyard-hello-world blog post

src/_blog/2024-04-shipyard-hello-world.md

@@ -0,0 +1,130 @@
+---
+title: 'IPFS & libp2p Devs Go Independent: Meet Interplanetary Shipyard'
+
+description: 'Check out the new IPFS community calendar where you can participate and contribute to one of the many working groups advancing IPFS.'
+author: Bethany Crystal
+date: 2024-04-01
+permalink: '/2024-04-shipyard-hello-world/'
+header_image: '/shipyard-hello-world.png'
+tags:
+  - 'ipfs'
+  - 'libp2p'
+  - 'shipyard'
+  - 'interplanetary shipyard'
+---
+
+Since its release nearly ten years ago, IPFS has become the connective tissue that powers the infrastructure layer for the decentralized web and connects web2 to web3. Well over 50 million monthly active users access IPFS-based applications, from ENS addresses (~90% of content hashes) to NFTs to blockchains to IoT to enterprise applications. IPFS has always been an open, decentralized, censorship-resistant protocol. But its developers and maintainers were employees of Protocol Labs. 
+
+Now we’re delighted to announce our own “exit to community”: [Interplanetary Shipyard](https://ipshipyard.com/), an **independent collective of many of the most popular implementations in the IPFS and libp2p ecosystem**. 
+
+Many of the core maintainers of IPFS and libp2p implementations are now part of Shipyard, a newly created Delaware-based non-stock entity. Shipyard is laser-focused on supporting users of the open-source projects in the Interplanetary stack. We are committed to building bridges between web2 and web3 through open-source innovation.
+
+Our current set of implementations maintained by Shipyard include:
+
+
+<table>
+  <tr>
+   <td colspan="2" ><strong>IPFS</strong>
+   </td>
+   <td><strong>libp2p</strong>
+   </td>
+  </tr>
+  <tr>
+   <td rowspan="2" >Boxo
+<p>
+Rainbow
+<p>
+Someguy
+<p>
+ipfs.io
+<p>
+dweb.link
+<p>
+trustless-gateway.link
+<p>
+delegated-ipfs.dev
+<p>
+Kubo
+<p>
+Badbits
+   </td>
+   <td rowspan="2" >Amino DHT
+<p>
+IPFS Companion
+<p>
+IPFS Measurements
+<p>
+IPFS Desktop
+<p>
+libp2p Measurements
+<p>
+Helia
+<p>
+service-worker-gateway
+<p>
+@helia/verified-fetch
+<p>
+IPFS Cluster <em>(on hold)</em>
+   </td>
+   <td rowspan="2" >go-libp2p
+<p>
+js-libp2p
+<p>
+rust-libp2p
+   </td>
+  </tr>
+  <tr>
+  </tr>
+</table>
+
+
+IPFS is a big project with big ambitions of being the essential content addressing layer for the next generation of the internet. That ecosystem comes with a sprawling set of resources that IPFS users today depend on in some way, including:
+
+* People and expertise
+* Applications
+* Libraries
+* Networks
+* Infrastructure
+
+Think of Shipyard as the union of dockworkers who send ships (projects) out onto the ocean of the distributed web, well-built and equipped with all they need to sail. The next era of the internet is still in its infrastructure phase; IPFS has already positioned itself as one of the core infrastructure layers for the next generation of the internet, and these implementations will be working with the foundation to continue to steward the project.
+
+We want the community to inform how we grow and sustain ourselves, and are eager for community input on our roadmap. We believe the builders growing IPFS, libp2p, and ProbeLab will thrive best together, under their own roof. 
+
+So, a few questions might arise next.
+
+**Why now?**
+
+The set of projects leveraging IPFS and libp2p is now so broad and diverse that it exceeds the purview of one company. Open-source projects need to be managed and owned by their community. 
+
+Consider the precariousness of core IPFS development being tied to a single company, and thus a single funding source. What if that company experiences a crisis? What if that funding source decides to prioritize something different from what the IPFS developers believe is most important? In web2, the model for supporting and promoting open-source projects was to get the largest centralized players to pay their own employees to maintain the tooling. What does that model look like for the next generation of the internet? 
+
+We want to let the community decide. We believe putting control of the IPFS stack in the hands of an independent collective will foster better resiliency, transparency, open-protocol governance, and long-term future health. By **operating independently while collaborating publicly**, we will build alongside other technical teams that rely on this essential infrastructure. 
+
+**Is this a spinout from Protocol Labs?**
+
+Not quite. Better to think of Shipyard as an independent entity in the Protocol Labs Network.
+
+**What’s on deck for Shipyard?**
+
+We have an extensive [initiative roadmap](https://ipshipyard.com/initiative-roadmap) and are eager to get more input from the developer community. To shout out just a few ideas we’re working on:
+
+* [Reliable, decentralized, and verified retrieval of CIDs](https://ipshipyard.com/initiative-roadmap/reliable-decentralized-and-trustless-browser-fetching-of-ipfs-content) (content identifiers) in browsers. The idea is to allow web browsers to fetch CIDs in a verifiable and trustless manner without being vulnerable to centralized chokepoints.
+* [IPFS for pioneers](https://ipshipyard.com/initiative-roadmap/ipfs-for-pioneers-enable-building-interoperable-ipfs-systems-using-http-protocols). We aim to enable the building of interoperable IPFS systems using extremely minimal HTTP-based protocols so that building IPFS-compatible tooling in something like Python (that doesn’t have much IPFS or libp2p tooling today) is super easy and appealing.
+* [Self-service tooling for debugging IPFS request handling](https://ipshipyard.com/initiative-roadmap/self-service-tooling-for-debugging-ipfs-request-handling). The idea here is that a user can hit a Boxo-based HTTP gateway and if they experience an error, get a link to download an IPFS request trace. They can then use easy tooling locally or centrally hosted to pinpoint the issue.
+
+**Who maintains and funds this work?**
+
+We're grateful to Protocol Labs, our anchor financial partner for 2024-2025, for its continued support. We’ve also secured significant commitments from other big3 web3 foundations in support of public goods funding to maintain IPFS and libp2p. We’re thankful as well to our early ecosystem supporters and patrons including CoopHive, Pinata, and Fission.
+
+We’re exploring multiple avenues for financial support, and in keeping with our new community collective approach, we’re thinking in public about what those avenues could be: public goods funding, community grants, or even token splits. 
+
+**Our team is raising an additional $3 million in community contributions to sustain our work as technical stewards in 2024**. Here’s how you can support Shipyard: 
+
+* **Support Public Goods Maintenance \
+**If you or your project depends upon IPFS or libp2p, we invite you to consider contributing toward the ongoing maintenance of these important protocols as a public good. You can donate directly to IPFS or libp2p through the [Open Internet Foundation](https://openimpact.foundation/).
+* **Hire Shipyard for Commercial Services \
+**In addition to public good funding, we are also beginning to support commercial service agreements for our core users, including service tiers, contracted support, and other embedded engineering work. You can check out our [commercial services tiers](https://ipshipyard.com/) or reach out directly if you have a project you’d like to collaborate with us on.
+
+We’re so excited to watch the ecosystem of the Shipyard “docks” flourish with more projects, partnerships, and input from a community that will now have more say than ever in shaping the future of the entire Interplanetary stack.
+
+--