Develop the security and privacy user interface and visual language for IPFS in the browser address bar.

Experiment with integrating the features and economic models of Basic Attention Token and Filecoin.

Define the application model for IPFS web apps.

Add features for revisitation, co-hosting, and offline/local collaboration.

Ease both publishing and sharing of IPFS content in browser UI.

Improve performance and stability - reduce memory, CPU, and bandwidth use.

There’s still a lot to do - here’s a list of some planned work for this year, and areas we’d like to experiment in, as well: This initial release of native support for IPFS in Brave provides basic node functionality. You can access the IPFS administrative UI at brave://ipfs, or enable IPFS Companion and select “My Node” button in the main menu.

Users can also specify a gateway of their choice in the browser settings. The default gateway used is dweb.link, which is run by Protocol Labs. When Brave detects an address which is an HTTP gateway URL to IPFS content, or a native IPFS address such as ipfs:// or ipns:// it will prompt the user to install and enable the native IPFS node, or to use an HTTP gateway. Brave has integrated IPFS into its desktop web browser for Windows, macOS, and Linux.

Brave browser tor disconnected