<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Interplanetary Shipyard</title><link>https://ipshipyard.com/</link><description>Recent posts on Interplanetary Shipyard</description><generator>Hugo</generator><language>en-us</language><copyright>IPShipyard Inc. All rights reserved.</copyright><lastBuildDate>Mon, 11 May 2026 00:00:00 -0400</lastBuildDate><atom:link href="https://ipshipyard.com/index.xml" rel="self" type="application/rss+xml"/><item><title>IPFS Public Gateways are Redirecting to inbrowser.link</title><link>https://ipshipyard.com/blog/2026-ipfs-gateways-redirect-inbrowser-link/</link><pubDate>Mon, 11 May 2026 00:00:00 -0400</pubDate><guid>https://ipshipyard.com/blog/2026-ipfs-gateways-redirect-inbrowser-link/</guid><description>&lt;p>Following up on our &lt;a
 href="https://ipshipyard.com/blog/2025-a-post-gateway-world/"
 
 target="_blank" rel="noopener noreferrer"
 
 >earlier post&lt;/a
>
 about moving IPFS users beyond centralized gateways, we have now begun redirecting users who navigate directly to &lt;a
 href="https://ipfs.io"
 
 target="_blank" rel="noopener noreferrer"
 
 >ipfs.io&lt;/a
>
 and &lt;a
 href="https://dweb.link"
 
 target="_blank" rel="noopener noreferrer"
 
 >dweb.link&lt;/a
>
 to &lt;a
 href="https://inbrowser.link"
 
 target="_blank" rel="noopener noreferrer"
 
 >inbrowser.link&lt;/a
>
.&lt;/p></description></item><item><title>Shipyard’s Q1 2026 Contributions to IPFS</title><link>https://ipshipyard.com/blog/2026-q1-shipyard-ipfs-contributions/</link><pubDate>Sat, 18 Apr 2026 00:00:00 -0400</pubDate><guid>https://ipshipyard.com/blog/2026-q1-shipyard-ipfs-contributions/</guid><description>&lt;h3 id="tldr">TL;DR&lt;/h3>
&lt;p>In Q1 2026, Shipyard moved IPFS meaningfully closer to production readiness by:&lt;/p></description></item><item><title>Migrating IPFS Project Websites from Fleek to Modular Infrastructure</title><link>https://ipshipyard.com/blog/2026-ipfs-self-hosting-migration/</link><pubDate>Tue, 06 Jan 2026 00:00:00 -0500</pubDate><guid>https://ipshipyard.com/blog/2026-ipfs-self-hosting-migration/</guid><description>&lt;p>Shipyard migrated 15+ IPFS Project websites to modular infrastructure where each component is independently swappable. This post explains the approach and how to set it up for your project.&lt;/p></description></item><item><title>Shipyard 2025: Bringing IPFS Home</title><link>https://ipshipyard.com/blog/2025-shipyard-ipfs-year-in-review/</link><pubDate>Fri, 19 Dec 2025 00:00:00 -0500</pubDate><guid>https://ipshipyard.com/blog/2025-shipyard-ipfs-year-in-review/</guid><description>&lt;h2 id="tldr">TL;DR&lt;/h2>
&lt;p>2025 was the year IPFS became practical for regular users. Seven &lt;a
 href="#kubo"
 
 >Kubo&lt;/a
>
 releases shipped alongside dozens more across &lt;a
 href="#gateway"
 
 >Rainbow&lt;/a
>
, &lt;a
 href="#user-facing-tools"
 
 >Desktop, WebUI, Companion&lt;/a
>
, and the JavaScript ecosystem including &lt;a
 href="https://github.com/ipfs/helia"
 
 target="_blank" rel="noopener noreferrer"
 
 >Helia&lt;/a
>
 and &lt;a
 href="#verified-fetch"
 
 >@helia/verified-fetch&lt;/a
>
. The theme throughout: removing barriers that kept IPFS confined to datacenters and making it work on consumer hardware.&lt;/p></description></item><item><title>Provide Sweep: Solving the DHT Bottleneck for Self-Hosting IPFS at Scale</title><link>https://ipshipyard.com/blog/2025-dht-provide-sweep/</link><pubDate>Wed, 26 Nov 2025 00:00:00 -0500</pubDate><guid>https://ipshipyard.com/blog/2025-dht-provide-sweep/</guid><description>&lt;h2 id="tldr">TL;DR&lt;/h2>
&lt;p>&lt;strong>What&amp;rsquo;s new:&lt;/strong> &lt;a
 href="https://github.com/ipfs/kubo/releases/tag/v0.39.0"
 
 target="_blank" rel="noopener noreferrer"
 
 >Kubo v0.39&lt;/a
>
 ships &lt;a
 href="https://github.com/ipfs/kubo/blob/master/docs/config.md#providedhtsweepenabled"
 
 target="_blank" rel="noopener noreferrer"
 
 >Provide Sweep&lt;/a
>
 as the default provider system. After testing as an opt-in experimental feature in v0.38 with no significant issues, it now comes with smart &lt;a
 href="https://github.com/ipfs/kubo/blob/master/docs/config.md#providedhtresumeenabled"
 
 target="_blank" rel="noopener noreferrer"
 
 >resume capabilities&lt;/a
>
 and memory optimizations. By grouping CIDs allocated to the same IPFS DHT servers and sweeping through keyspace regions systematically, nodes achieve &lt;strong>97% fewer DHT lookups&lt;/strong> with smooth, predictable resource usage.&lt;/p></description></item><item><title>An update about Libp2p maintenance at Shipyard</title><link>https://ipshipyard.com/blog/2025-libp2p-maintenance-update/</link><pubDate>Thu, 21 Aug 2025 00:00:00 -0400</pubDate><guid>https://ipshipyard.com/blog/2025-libp2p-maintenance-update/</guid><description>&lt;p>Today we want to share an important update on Shipyard’s role as a contributor to the libp2p project and as the maintainers of go-libp2p and js-libp2p. We will be transitioning stewardship of the Go and JavaScript implementations of libp2p to community maintainers.&lt;/p></description></item><item><title>Debugging Superpowers With the New js-libp2p Developer Tools</title><link>https://ipshipyard.com/blog/2025-js-libp2p-devtools/</link><pubDate>Fri, 25 Jul 2025 00:00:00 -0400</pubDate><guid>https://ipshipyard.com/blog/2025-js-libp2p-devtools/</guid><description>&lt;p>Interplanetary Shipyard is thrilled to share &lt;a
 href="https://github.com/ipshipyard/js-libp2p-inspector/"
 
 target="_blank" rel="noopener noreferrer"
 
 >js-libp2p inspector&lt;/a
>
, the new developer tools for debugging and inspecting js-libp2p and Helia, for use both in browsers and Node.js.&lt;/p></description></item><item><title>A Post Gateway World: Transitioning Users to Direct Retrieval with IPFS</title><link>https://ipshipyard.com/blog/2025-a-post-gateway-world/</link><pubDate>Wed, 23 Jul 2025 00:00:00 -0400</pubDate><guid>https://ipshipyard.com/blog/2025-a-post-gateway-world/</guid><description>&lt;h1 id="summary">Summary&lt;/h1>
&lt;p>The public-good IPFS gateways at &lt;code>ipfs.io&lt;/code> and &lt;code>dweb.link&lt;/code> have played a foundational role in IPFS adoption—serving over 614 million requests and 45TB of data to 10 million users daily. However, this centralized infrastructure has become a major obstacle to sustainability and decentralization.&lt;/p></description></item><item><title>Could IPFS Have Prevented the Bybit Hack?</title><link>https://ipshipyard.com/blog/2025-could-ipfs-prevent-bybit-hack/</link><pubDate>Fri, 28 Feb 2025 00:00:00 -0500</pubDate><guid>https://ipshipyard.com/blog/2025-could-ipfs-prevent-bybit-hack/</guid><description>&lt;h2 id="the-bybit-hack-and-ipfs">The Bybit Hack and IPFS&lt;/h2>
&lt;p>Bybit&amp;rsquo;s &lt;a
 href="https://www.reuters.com/technology/cybersecurity/cryptos-biggest-hacks-heists-after-15-billion-theft-bybit-2025-02-24/"
 
 target="_blank" rel="noopener noreferrer"
 
 >recent hack&lt;/a
>
, which resulted in the loss of $1.4 billion, is a reminder of the importance of verification for frontends, especially dapp frontends in the Web3 ecosystem.&lt;/p></description></item><item><title>IPFS on the Web in 2024: Update From Interplanetary Shipyard</title><link>https://ipshipyard.com/blog/2024-shipyard-improving-ipfs-on-the-web/</link><pubDate>Mon, 25 Nov 2024 00:00:00 -0500</pubDate><guid>https://ipshipyard.com/blog/2024-shipyard-improving-ipfs-on-the-web/</guid><description>&lt;h2 id="update-from-interplanetary-shipyard">Update From Interplanetary Shipyard&lt;/h2>
&lt;p>Earlier this year, &lt;a
 href="https://blog.ipfs.tech/shipyard-hello-world/"
 
 target="_blank" rel="noopener noreferrer"
 
 >we introduced Interplanetary Shipyard&lt;/a
>
, as the evolution of the maintainers leading the open-source development of libp2p and the most popular IPFS implementations, tooling and infrastructure.&lt;/p></description></item><item><title>IPFS &amp; libp2p Devs Go Independent: Meet Interplanetary Shipyard</title><link>https://ipshipyard.com/blog/shipyard-hello-world/</link><pubDate>Mon, 08 Apr 2024 00:00:00 -0400</pubDate><guid>https://ipshipyard.com/blog/shipyard-hello-world/</guid><description>&lt;p>&lt;em>Last November, Protocol Labs, where IPFS was invented and incubated, &lt;a
 href="https://protocol.ai/blog/advancing-ipfs-and-libp2p-governance/"
 
 target="_blank" rel="noopener noreferrer"
 
 >announced its commitment to decentralizing project governance&lt;/a
>
. In this post, you&amp;rsquo;ll hear from Adin Schmahmann of Interplanetary Shipyard, introducing the new team, its roadmap, and what this means for the IPFS community.&lt;/em>&lt;/p></description></item></channel></rss>