TL;DR: IPFS is planning the next phase of work to make browsers better for the decentralized web – not just IPFS, but any protocol that needs lightweight crypto, peer-to-peer connections, or native browser integration. We need your input on what features matters most. Background: What We’ve Accomplished Over the past 5 years, sustained collaboration with Igalia has delivered real improvements to all major browsers: Ed25519 in WebCrypto API - Shipped in Chrome 137 (May 2025), now available in...
Project: IPFS Chromium implementation | Little Bear Labs | Little Bear Labs
Faster, more secure, more accessible IPFS links in Chromium-based browsers.
IPFS: Building blocks for a better web | IPFS
Open protocols to store, verify, and share data across distributed networks.
High Performance Browser Networking (O'Reilly)
What every web developer must know about mobile networks, protocols, and APIs provided by browser to deliver the best user experience.
Announcing Supporters of Chromium-based Browsers
Since Google announced the Chromium project in 2008, we have been excited to build on the great foundations of open-source web browsers and contribute to the continued d…
Which browsers are best for privacy?
An open-source privacy audit of popular web browsers.
IPFS is moving beyond the sponsored gateways
How IPFS is shifting from centralized public gateways to distributed infrastructure and client-side retrieval.
Forget the Fate of Chrome, Focus on the Fate of the Browser
In debating what undoubtedly won't happen, we're looking past some key things that are -- and might...
Introducing Filebase Sites: Simplified IPFS Websites with IPNS
Hosting a real website on IPFS has always come with friction: changing CIDs, manual IPNS management, and fragile workflows. Filebase Sites removes the last-mile complexity, giving developers a simple way to publish, update, and maintain decentralized websites without breaking links.
Stop Ignoring the Browser: The Biggest Frontend Shift in a Decade
Native browser APIs now provide powerful alternatives for routing, state management, and components. Never mind the frameworks, use the browser.
#protocolsforpublishers #atproto #mcp #webapplets | Chad Kohalyk
Web publishing is facing its next challenge: a new iteration of centralizing platforms. BUT there is also a new wave of open protocols and standards that can help us gain our independence. Next month in NYC we are gathering a group of frontier technologists and popular web publishers to discuss how we can sail into this next platform shift as captains. #ProtocolsForPublishers Learn more and sign up here: https://pfp.unternet.co We will be hosting talks on #atproto #mcp #webapplets and web payments, and give publishers the opportunity to interact directly with developers working on these frontier technologies. Thank you to Unternet, Graze Social, Free our Feeds, and betaworks for their support.
Oh yeah — Ed25519 is now available in Chrome! Read what the ineffable @bumblefudge.com has to say about this wonderful piece of news. ipfsfoundation.org/ed25519-support-in-chrome-mak…
Ed25519 Support in Chrome: Making the Web Faster and Safer
ipfsfoundation.orgImportant piece of multi-protocol support in browsers! Thanks to much work from Javi, and funding from @ipfs.tech. HEY NOW, settle down - a ways to go: - can only redirect to URLs/paths - no Safari - off by default in Chrome (for now) - only allow-listed schemes unprefixed Step by step...
Javier Fernandez
Blog post about a new Chromium feature I've been working on to allow Web Extensions register protocol handlers just declaring them in the Manifest. blogs.igalia.com/jfernandez/2026/03/24/protoco…
Manifest-declared protocol handlers just landed (behind a flag) in Chrome 146 🎉 This is how ipfs:// or atproto:// can become first-class citizens of the browser! The web that's coming is built on keys, hashes, and verifiable data. Browsers need to meet it there. ipfsfoundation.org/protocol-handler-registration…
Protocol Handler Registration in Chrome 146 and the Browser as OS
ipfsfoundation.org
