dweb

We have DAEMON_START metric which shows duration and count of times we need to start up our own daemon. However, we do not have a metric to show how often there are users who are already running an ipfs daemon.

The webui is available when running the go implementation of IPFS, so if we see a lower count for this NO_DAEMON_START metric, then we could potentially redirect any users who are alread

Seems that Firefox (around version 96-97) changed somethign and is now way more aggresive when a gateway does not start returning response immediately.

For example, first load (empty ipfs repo) of http://dist.ipfs.io.ipns.localhost:8080/go-ipfs/v0.11.0 in Firefox 97 produces:

![2022-02-11_19-09](https://user-images.githubusercontent.com/157609/153646056-9bc942ec-bec7-4f0a-b61b-53db7bf6896

• Add a new attribute called loading to the omnibox which should be "true" or "false"
• Inside attributeChangedCallback detect the changing of loading and change the content of the submit button to a loading indicator or

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

Expected Behaviour

Github Actions should run existing integration tests successfully on windows-latest machine

Actual Behaviour

Integrations tests run on the windows-latest operating systems are failing.

Extra Information

Here is a CI run that failed: https://github.com/FleekHQ/space-daemon/runs/1524767049?check_suite_focus=true

The issue appears to be with a wrong `Ipfsnode

The tab bar background is transparent when you open the support menu. To reproduce just tap the "Help & Support" button from the side menu.