IPFS

go-ipfs 0.8.0-rc2 dispatches remote pin request but does not act on its status, so without manual inspection it is possible to miss the fact that MFS pinning (Pinning.RemoteServices.*.Policies.MFS, #7913) stopped working.

I believe we should keep checking pin status every RepinInterval until its pinned or failed, and if it's the latter, print ERROR into remotepinning/mfs logger. Pi

• Version:

0.55.4

• Platform:

Linux p1 5.4.0-1048-aws #50~18.04.1-Ubuntu SMP Tue May 4 17:40:02 UTC 2021 x86_64 x86_64 x86_64 GNU/Lin

In Settings : 'Add a new side account' button

Step #2 in Side account creation

(a very light & quick version of onboarding, with only nickname step)
![side account mode copy](https://user-images.githubusercontent.com/37345040/99953009-dd7db900-2d80-11eb-9f6f-e

QmfFLsxJsviSncH5LGkwss53Vn2v6ebZYb3bJYtZ5P25HM

this is the a sample file hash.

browse this file hash will freeze the window, and got high cpu usage.

and the log said: error: [web ui] unresponsive: [object Object]

@D4nte commented on Thu Apr 22 2021

When not passing any filter in the browser, I understand that filter dnsWsOrWss is being used.
When trying to connect to an ip4 ws address, it fails due to the filter, however the error returned by libp2p is very obscure (see below).

Would there be a way to make this error point to the filte

Small UX improvement idea:

Companion should keep track of errored loads from local gateway and attempt to reload respective tabs (if still present) when API state changes from offline to online.

When there are too many data-sources, the RPC call fails with "payload too large"

Affected subgraph

Error:

Payload is too big to load: Unexpected RPC error, error: Transport("Unexpected response status code: 413 Payload Too Large"), component: BlockStream

• [Source](https://github.com/pancakeswap/

Describe the bug
Basic text is rendering as an "image" and isn't select-able.

Expected behavior
Being able to copy + inspect text data.

Screenshots

These are all "images" and cannot be selected as text:

![text_image](https://user-images.githubusercontent.com/1001

This was cut from the v0.2.0 release for present time constraints however making ipfs-http more accessible as "the" ipfs binary would make the project more accessible to anyone just wanting to try it out. At the moment I see the following obstacles:

• http/README.md has no tutorial on how to try out ipfs-http
• ipfs-http supports only `i

Summary

This is the main tracking issue for DNSLink support. If there is a programmable DNS service out there, we should have support for it.

Ideally even doing things like detecting the provider from the domain name and doing the right thing.

Status

Please add a sign up button to main page.