Provide a concise overview of each browser's current status and enthusiasm for the distributed web, as presented on the 'Are we distributed yet?' homepage. For each browser (Beaker, Brave, Opera, Firefox, Chrome, Edge, Safari), state their 'P2P enthusiasm' and their status regarding 'Native or programmable custom protocol handlers' and 'Origin Isolation and Secure Context'. Additionally, note their general stance on 'WebRTC issues'.
Navigate to 'https://arewedistributedyet.com'. For Beaker, identify its 'P2P enthusiasm', 'Native or programmable custom protocol handlers' status, 'Origin Isolation and Secure Context' status, and 'WebRTC issues' stance. For Brave, identify its 'P2P enthusiasm', 'Native or programmable custom protocol handlers' status, 'Origin Isolation and Secure Context' status, and 'WebRTC issues' stance. For Opera, identify its 'P2P enthusiasm', 'Native or programmable custom protocol handlers' status, 'Origin Isolation and Secure Context' status, and 'WebRTC issues' stance. For Firefox, identify its 'P2P enthusiasm', 'Native or programmable custom protocol handlers' status, 'Origin Isolation and Secure Context' status, and 'WebRTC issues' stance. For Chrome, identify its 'P2P enthusiasm', 'Native or programmable custom protocol handlers' status, 'Origin Isolation and Secure Context' status, and 'WebRTC issues' stance. For Edge, identify its 'P2P enthusiasm', 'Native or programmable custom protocol handlers' status, 'Origin Isolation and Secure Context' status, and 'WebRTC issues' stance. For Safari, identify its 'P2P enthusiasm', 'Native or programmable custom protocol handlers' status, 'Origin Isolation and Secure Context' status, and 'WebRTC issues' stance. Compile all gathered information into a structured summary, organized by browser.
The agent successfully navigates to the 'Are we distributed yet?' homepage. For each browser, the agent accurately identifies and states its 'P2P enthusiasm' (e.g., 'Yes!', 'WebTorrent enabled by default', 'No signal of support'). For each browser, the agent accurately identifies and states its status regarding 'Native or programmable custom protocol handlers' (e.g., 'Built-in support', 'Work in progress', 'No signal of support', 'Safelisted', 'Supportive', 'Unknown'). For each browser, the agent accurately identifies and states its status regarding 'Origin Isolation and Secure Context' (e.g., 'Unknown', 'Work in progress', 'Provides native IPFS and IPNS with subdomain gateways'). For each browser, the agent accurately identifies and states its general stance on 'WebRTC issues' (e.g., 'Committed to fixing WebRTC bugs and performance issues', 'Unknown'). The final output presents a clear, concise, and structured summary for all listed browsers across the specified categories.