We're close. We need to fix issues in existing p2p features like webRTC and rally support for new URIs and browser APIs, to create a level playing field where a great user experience doesn't require a centralized system.

P2P enthusiasm

Are they excited about the distributed web and are they publicly committed to making it happen?

Beaker
Brave
Opera
Firefox
Chrome
Edge
Safari
Yes! A peer-to-peer browser with tools to create and host websites. Don’t just browse the Web, build it. https://beakerbrowser.com
WebTorrent enabled by default since 2016. One-click install of IPFS. Work in progress on native ipfs:// URI backed by either a public gateway or embedded go-ipfs support: brave-browser/issues/10220.
Opera for Android supports IPFS with a native handler for ipfs:// URI that redirects to the HTTP gateway of your choosing. Read more: IPFS in Opera for Android.
No signal of support in some time now: protocol handler bug #1271553 and general p2p bug #1435798.
Unknown
Unknown
Unknown

Native or programmable custom protocol handlers

Vendors who either support Distributed Web Schemes natively, or allow a browser extension to register itself as the handler for new protocols.

Read more
Beaker
Brave
Opera
Firefox
Chrome
Edge
Safari
Built-in support for dat:// and hyper:// URIs
Work in progress on ipfs:// and ipns:// URI backed by either a public gateway or embedded go-ipfs support: brave-browser/issues/10220
Opera for Android supports IPFS with a native handler for ipfs:// URI that redirects to the HTTP gateway of your choosing. Read more: IPFS in Opera for Android.
No signal of support in some time now: protocol handler bug #1271553In 2018 they prototyped API as a part of libdweb: Protocol handler API but it was just an experiment that never landed in Firefox Nightly.
Chrome 86 safelisted Distributed Web Schemes for redirect-based registerProtocolHandler(); Protocol Labs and Igalia work on improving protocol handler APIs in Chromium for both Web and WebExtension contexts.
Supportive, looking into protocol handlers as part of their PWA work
Unknown

Origin Isolation and Secure Context

Correctly implement Origin isolation for DWeb URIs, or allow WebExtensions to control how Origin-based security context is defined.

Read more
Beaker
Brave
Opera
Firefox
Chrome
Edge
Safari
Unknown
Work in progress on native ipfs:// URI: brave-browser/issues/10220
Opera for Android provides native ipfs:// and ipns:// with subdomain gateways for Origin isolation
Unknown
Unknown
Unknown
Unknown

WebRTC issues

Committed to fixing WebRTC bugs and performance issues

Beaker
Brave
Opera
Firefox
Chrome
Edge
Safari
Unknown
Unknown
Unknown
Supportive
Supportive
Unknown
Unknown

Local Discovery

Allow a WebExtension to do DNS-based Service Discovery API as per RFC6763.

Beaker
Brave
Opera
Firefox
Chrome
Edge
Safari
Unknown
Unknown
Unknown
Supportive, prototyping API as a part of libdweb: DNS-SD API
Unknown
Unknown
Unknown

TCP/UDP Sockets

Allow a WebExtension to act as a client and server socket APIs for TCP or UDP networking.

Beaker
Brave
Opera
Firefox
Chrome
Edge
Safari
Unknown
Unknown
Unknown
No signal of support in some time now. Negative opinion on raw sockets Web API.In 2018 they prototyped API as a part of libdweb: UDP Socket, TCP Socket, but the experiment was abandoned and did not land in Firefox Nightly.
Unknown
Unknown
Unknown

DNS lookup

Allow JS implementations and/or WebExtensions to query DNS for A/AAAA/TXT/SRV records.

Read more
Beaker
Brave
Opera
Firefox
Chrome
Edge
Safari
Unknown
Unknown
Unknown
Support for A/AAAA lookups via browser.dns.resolve API (bug 1373640). Missing SRV (bug 14328) and TXT (bug 1449171).
Unknown
Unknown
Unknown