Right now, software that is fully in the control of the user is often too technical, too fragile, and too time-consuming to be the default choice.

But we're making headway. Today, we'd like to share some collaborations the IPFS project has had in the works for a while, which bring us a few steps closer to making unmediated access to information just work… by solving that "last mile" problem and integrating IPFS directly into web browsers.

The path to a truly decentralized web is a long one. For over 30 years the browser has been a client – but a foundational concept in P2P systems is that a participant is both a client and a server. Web browser vendors and web standards bodies have not designed for this architectural shift, so we're breaking it down into steps.

From the beginning, IPFS had an HTTP gateway. The gateway lets HTTP clients like web browsers publish to and read from the IPFS network. Now there are lots of different public HTTP gateways to the IPFS network, and the gateway we run at ipfs.io serves over five million requests per day.