(living summary: updated @ 2018-09)
This issue tracks browser extension support for various protocol schemes and URIs according to four stages of the upgrade path for path addressing and IPFS Addressing in Web Browsers memo, namely:
URLs:
ipfs://{cidv1b32}
→http://127.0.0.1:8080/ipfs/{cidv1b32}
ipns://{hash}
→http://127.0.0.1:8080/ipns/{hash}
URI:
dweb:/ip[f|n]s/{hash}
→http://127.0.0.1:8080/ip[f|n]s/{hash}
This issue also tracks (currently nonexistent) ways to address/workaround how Origin is calculated (Problem #2)
WebExtension APIs Universal APINo such thing yet (but see WIP work in comments)
web+fs
protocol is supported as a redirect: Support Custom Protocols in WebExtension #164 (comment)web+
prefix
Rob Wu wrote up a draft concept of having a webRequest.respondWithcapability [but it went nowhere so far]
– https://mail.mozilla.org/pipermail/dev-addons/2017-December/003466.html
The Protocol API allows you to handle custom protocols from your Firefox extension. This is different from the existing WebExtensions protocol handler API in that it does not register a website for handling corresponding URLs but rather allows your WebExtension to implement the handler.
More: https://github.com/mozilla/libdweb/#protocol-api
ipfs://
in address bar.libdweb
branch. More info in PR [PoC] libdweb experiment: protocol handler API #533 and /libdweb/docs/libdweb.mdweb+
prefix for non-safelisted protocolsweb+
prefix (context: Safelisting DWeb Protocols arewedistributedyet/arewedistributedyet#23)browser.protocol.registerStringProtocol
available to trusted extensionsRetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4