# decentralized-web Published articles for decentralized-web. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Interplanetary Shipyard Introduces Its Team and Roadmap for IPFS and libp2p DevFeed: [Interplanetary Shipyard Introduces Its Team and Roadmap for IPFS and libp2p]() Original publisher: [Read original article]() Author: Adin Schmahmann Published: 2024-04-08T00:00:00Z Content type: release Language: en Sources: [IPFS]() Topics: [IPFS](), [Maintainers](), [Open Source](), [decentralized-web](), [Tooling](), [coding-community]() Tags: [decentralized-web](), [ipfs](), [libp2p](), [maintainers](), [object-object](), [open-source](), [tooling]() ### AI overview Interplanetary Shipyard, an independent collective of maintainers, introduces its team and roadmap for supporting open-source projects in the IPFS and libp2p ecosystem. The post describes initiatives involving browser retrieval, minimal HTTP-based protocols, and debugging tools. ### Source excerpt Meet the team behind Interplanetary Shipyard, the newly created entity of many core maintainers behind the most popular implementations of IPFS and libp2p. ## Debugging WebRTC, IPFS & Ethereum with HTTP Toolkit DevFeed: [Debugging WebRTC, IPFS & Ethereum with HTTP Toolkit]() Original publisher: [Read original article]() Author: HTTP Toolkit; Tim Perry Published: 2022-10-28T13:30:00Z Content type: article Language: en Sources: [HTTP Toolkit]() Topics: [WebRTC](), [Ethereum](), [IPFS](), [debug](), [web applications](), [browsers](), [HTTP]() Tags: [blockchain](), [browsers](), [debug](), [debugging](), [decentralized-web](), [ethereum](), [http](), [interception](), [javascript](), [web](), [webrtc]() ### AI overview This article describes HTTP Toolkit support for capturing, debugging, mocking, rewriting, and injecting errors in WebRTC, IPFS, and Ethereum traffic used by decentralized web applications. It also explains why debugging multi-protocol applications matters and discusses related protocols used alongside HTTP. ### Source excerpt HTTP is important on the web, but as other alternative protocols grow popular in networked applications, it's often important to be able to capture, debug and mock those too. I've been working on expanding HTTP Toolkit's support for this over the past year (as one part of a project funded by EU Horizon's Next Generation Internet initiative), to extend HTTP Toolkit to cover three additional rising protocols that are often used alongside simple HTTP in decentralized web applications: WebRTC, IPFS & Ethereum. This is now live! If you're using HTTP Toolkit to intercept browsers, and a web application connects to another peer over WebRTC, interacts with the Ethereum blockchain, or pulls content from the IPFS network, then you'll now see this inline amongst your collected HTTP traffic, and you can create rules to rewrite these requests, define mock responses, or inject errors. Let's talk about why this matters, what you can do with this, and how it actually works internally: Why? HTTP remains the key protocol on the web, by a wide margin, and that's not going to change any time soon. That said, there are an increasing number of new protocols being explored both alongside and on top of HTTP, covering alternate use cases and supporting different communication models, and as software evolves this will only increase. HTTP Toolkit needs to be able to support these, to ensure that you can easily understand and test all communications from the increasing number of multi-protocol applications. There's a lot of examples of HTTP-adjacent protocols where this applies: WebSockets, which grew to cover use cases needing persistent connections that weren't well supported by the request/response model, which use HTTP just for initial connection setup, and are now widely supported and used in HTTP-based apps. WebTransport, a new QUIC-based connection protocol that's aiming to supplant WebSockets with a modern approach that adds a swathe of other benefits on top. GraphQL, a general-purpose ## Testing libraries for the Decentralized Web DevFeed: [Testing libraries for the Decentralized Web]() Original publisher: [Read original article]() Author: HTTP Toolkit; Tim Perry Published: 2022-10-24T17:00:00Z Content type: tutorial Language: en Sources: [HTTP Toolkit]() Topics: [Testing](), [IPFS](), [Ethereum](), [Integration testing](), [ci](), [WebRTC](), [JavaScript](), [P2P](), [web applications]() Tags: [ci](), [data](), [database](), [decentralized-web](), [ethereum](), [hosting](), [integration-testing](), [javascript](), [testing](), [web-applications](), [webrtc]() ### AI overview This article introduces MockIPFS and Mockthereum, network interception libraries for IPFS and Ethereum. It explains how they support automated integration testing and CI workflows while also serving as foundations for network proxy tools for decentralized web applications. ### Source excerpt The world of decentralized web applications is an exciting place that has exploded in recent years, with technologies such as IPFS and Ethereum opening up possibilities for a peer-to-peer web - creating applications that live outside the traditional client/server model, where users to interact and control their own data directly. At the same time, it's still immature, and for software developers it lacks a lot of the affordances & ecosystem of the traditional HTTP-based web app world. There's far fewer tools and libraries for developers working in this space. I've been working on improving this over the last year (as one part of a project funded by EU Horizon's Next Generation Internet initiative), by building network interception libraries for both IPFS & Ethereum: MockIPFS & Mockthereum. These each act as both an immediately useful automated testing library, to support modern integration testing & CI workflows, and a base for building more general network proxy tools for web applications using either (or both) technologies. If that sounds cool and you just want to jump straight in and try these for yourself, you can get started at github.com/httptoolkit/mockipfs/ and github.com/httptoolkit/mockthereum/. On the other hand, if you want to hear what this can do in practice, and learn a little about how it works under the hood, read on: A new way to build web apps Decentralized web apps often use a mix of many different technologies, at various layers of the stack, such as: IPFS - for decentralized static content hosting & data storage Ethereum - for decentralized consistent global state, computation on that state, and financial transactions Filecoin/Storj - for paid decentralized long-term content storage WebRTC - for peer-to-peer raw data transfer, and video/audio connections Service workers - a JavaScript API allowing fully offline web apps Handshake (HNS)/Ethereum Name System (ENS) - to map domain names to web applications GunDB - a decentralized database for the ## EU Funding for Dev Tools for the Decentralized Web DevFeed: [EU Funding for Dev Tools for the Decentralized Web]() Original publisher: [Read original article]() Author: HTTP Toolkit; Tim Perry Published: 2021-09-15T12:00:00Z Content type: article Language: en Sources: [HTTP Toolkit]() Topics: [dev-tools](), [ZeroNet](), [IPFS](), [WebRTC](), [Ethereum](), [interception](), [debug](), [Testing](), [Logging](), [Script]() Tags: [announcements](), [applications](), [decentralized-web](), [dev-tools](), [development](), [ethereum](), [funding](), [interception](), [logging](), [open-source](), [webrtc]() ### AI overview HTTP Toolkit received EU Horizon funding through the Next Generation Internet initiative to expand its interception, debugging, and testing capabilities for decentralized-web applications. The project will focus on IPFS, WebRTC, and Ethereum, with results released under free and open-source licenses. ### Source excerpt Through the Next Generation Internet (NGI) initiative, HTTP Toolkit has been selected for funding from the EU's Horizon research & innovation program, to expand beyond HTTP and offer the same interception, debugging & testing functionality for applications built on top of the decentralized web. This is going to be a huge opportunity to invest in expanding HTTP Toolkit to support some very exciting new technologies, and extending existing core functionality to do so along the way. For this project I'm going to be specifically focusing on 3 main protocols that today form the backbone of the decentralized web: IPFS, WebRTC & Ethereum. For each of these protocols, the essential technologies are usable now, but the wider ecosystem and uptake is still in their infancy. I think it's clear that most mainstream web developers are not currently using these technologies to build production-grade decentralized applications. There are many reasons for this, but one is a lack of high-quality developer tooling. Moving from traditional client/server architectures to building decentralized applications requires developers to replace many day-to-day debugging & testing tools with manual logging, custom scripts and guesswork. This tooling gap makes decentralized development significantly more difficult. The goal here is to fix that, by providing modern tools for the future of the web. This is funded as part of the NGI Pointer project, funding me as an individual to work on this for a year, with all the resulting output to be available under free & open-source licenses (of course, HTTP Toolkit is conveniently already 100% open-source, so that's no change at all). If you're interested in the future of the web and you think developer tooling matters, I hope this is very exciting! If you're an existing HTTP Toolkit user though and you're only interested in HTTP, don't worry. This is equity-free R&D funding, so HTTP Toolkit remains a completely independent open-source project, and although