On macOS, it's a fairly standard practice to display a pre-roll if your application needs some form of permissions, before calling the system APIs for the first time that will actually produce the system's requested-permissions window.

For instance, for any given end-user, the following window is likely A) intimidating, and B) possibly encourages insecure habits, such as simply clicking "acce

Filling from mobile so we don't forget. Good first issue if someone wants to fix this via a PR before I get to it next week.

Right now, when IPFS integrations are disabled via a toggle, extension assumes http://.

Most servers redirect http:// → https://, or have HSTS set up, but Companion should default to https://, because if someone did not set up redirect to a secure context,

Vulnerabilities

DepShield reports that this application's usage of kind-of:4.0.0 results in the following vulnerability(s):

• (CVSS 5.3) CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')

It'd be awesome if this SDK had a WebTorrent style AddPeer feature for adding peers manually.

It'd be extra awesome if it accepted simple-peer instances too (like WebTorrent) for WebRTC peers.

EDIT: Also [removePeer](https://github.com/webtorrent/webtorrent/blob/mas

Every now and then when the page navigates, it won't be updated in the omni-box

Might need to listen on a different event or more types of events

Also affects navigation buttons.