Brave web browser adds native support for peer-to-peer IPFS protocol

NelsonG · January 19, 2021

The decentralized tech community is aiming to find support for technologies that go beyond cryptocurrency support.

In a blog post today the team at Brave announced that they have worked with Protocol Labs to integrate native support for the InterPlanetary File System (IPFS) inside their browser. The peer-to-peer file-sharing standard launched in 2015 and has been gathering support among open-source advocates who laud the protocol’s ability to stop companies and government bodies from taking down content across the web, as well as the more functional performance improvements, offline file-viewing capabilities and underlying reliability.

IPFS shares plenty of similarities with BitTorrent and allows files to be hosted by a multitude of users distributed across networks. With the update, Brave users will be able to access content from web addresses starting with ipfs:// and will be able to host an IPFS node themselves. The company says that adding support for IPFS will help improve “the overall resilience of the Internet.”

Why The Internet Needs IPFS Before It’s Too Late

Brave is a likely home for the IPFS protocol given the company’s affinity for all things decentralized. The startup founded by Mozilla co-founder Brendan Eich says it now has 24 million monthly active users. Some of Brave’s most unique features have involved blockchain or peer-to-peer tech. In 2018, Brave announced a beta of Tor Tabs bringing the decentralized Onion protocol into the mix.

Last year, Opera announced that it was bringing limited support for IPFS to its Android application.

Decentralization tech is finding more mainstream interest as tech companies have slowly warmed up to the opportunities in cryptocurrency. Last week, TechCrunch looked into how Twitter was looking to help build out a decentralized network for social media platforms.

Twitter’s decentralized future

It’s unclear whether this is a technology that more mainstream browsers will opt to support natively, given the clear potential for abuse that exists in allowing users to work around file takedowns and the fact that it is a pretty niche technology for the time being.