historical notes about Muon-based Brave (early 2018)
- Brave switched to Chromium in 2018 so I collapsed outdated notes that were related to Muon-based Brave build.
- IPFS Companion works perfectly with Chromium-based Brave, and this PR updates our docs to reflect that ( Add Official Support for Chromium-based Brave #609)
- We now work toward bundling go-ipfs with Brave, with the goal of having something similar to how Tor Tabs work.
- Follow → IPFS Integration - Roadmap and discussion brave/brave-browser#819
– @lidel, Q4 2018
ipfs-companion
runs in brave!
The following ipfs address styles resolve, either to a local gateway, or the public one.
In the case of ipfs://
style, brave prompts the user if it's ok to "open in an external application. The url shown is the gateway url rather than what's been entered in the url bar, which could cause confusion.
A nice feature of using the ipfs://
form is that it is preserved in the url bar. The other forms are translated to a gateway url.
NURI style isn't supported (just for completeness)
/ipfs/QmZyRCtk8MGpuWXn2d1QyTfLWKMTHrT2aHs2vDkfry5zKT is redirected to
file:///ipfs/QmZyRCtk8MGpuWXn2d1QyTfLWKMTHrT2aHs2vDkfry5zKT
Brave supports a subset of the the chrome-extensions api, so there are few issues to figure out.
Things to get workingWe can talk to brave about getting this enabled in muon.
contextMenus.create
(means no ipfs option appears when right clicking on a page)contextMenus.update
idle.queryState
runtime.openOptionsPage
(this causes the Open Preferences fail)Requested, brave/browser-laptop#9556 (comment)
MinorUncaught (in promise) {message: "Access to extension API denied."}
WebGL: http://127.0.0.1:5001/ipfs/QmPhnvn747LqwPYMJmQVorMaGbMSgA7mRRoyyZYz3DoZRQ/#/connections
gilescope and mikeumusgilescope and mikeumuslidel, luixxiul, koalalorenzo, Katamori, retotrinkler and 2 more
RetroSearch 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