Bringing IPFS support to Web Browsers
Responsibilities
Browser Users - Browser extension exposes IPFS features in a robust and intuitive form
Web Developers - Ensure smooth experience for web developers in browser contexts
Browser Vendors - Browser developers are addressing requirements of the distributed web
Current Projects
- IPFS in Web Browsers - Coordination point (tracking via issues)
- IPFS Companion - Browser extension that brings IPFS integrations
- Push forward new web standards for decentralized web
- Remove obstacles from using IPFS in Web Applications and make the whole experience feel trivial
- Incentivize users to install and use IPFS Companion.
M(P0)
Base32 CIDv1 is the default and can be used as authority in URLsM(P0)
Drop-in API Provider library is the default way of integrating IPFS with web apps and browser extensionsM(P0)
HTTP/WS /api/v1/ with proper access controls existsM(P1)
Docs or guidebook of developer best practices for writing decentralised web apps exists.M(PX)
It is possible to verify integrity of HTTP Gateway ResponsesM(PX)
URIs are officially registered (IANA etc)
M(P1)
Having IPFS Companion installed is enough to create and publish a website on IPFSM(PX)
A complete snapshot of a web page can be saved to IPFS and shared with one click
M(P1)
IPFS Companion enables real-time, bidirectional file sharing between two or more people over the internetM(P1)
IPFS Companion enables ad-hoc transfer between two people over local network
M(P1)
Free and Open IPFS-powered CDN for JS libs exists
M(P0)
Collaboration on libdweb results in landing vital APIs into FirefoxM(P0)
IPFS is a viable distribution channel for Signed HTTP ExchangesM(P0)
Brave browser ships with embedded IPFS