IPFS

Now that go-ipfs-config supports optional types, we should go through and clean up as much of the existing config to use it so we have a consistent story on defaults, etc.

This work will be easier to do after ipfs/go-ipfs-config#151

The first step is to enumerate the various config keys we want to cleanup.

Here is what I've noticed:

• ipfs.block.get
  • docs say it returns a Block, but it returns a Uint8Array
  • docs are missing the preload option
• ipfs.block.put
  • docs say it can also take a Block as a parameter, but it can only be a Uint8Array
  • docs say it can take a cid as an option, but the implementation ignores such a parameter
  • docs say it returns a Block, b

When a contact is already added, open the contact profile or the existing conversation

The error check is done here: https://github.com/berty/berty/blob/097eb0229f22e2abce3addd750c8dce98e92845f/js/packages/components/modals/InvalidScan.tsx#L126

We shouldn't show the invalid scan modal but navigate instead

• OS: Linux
• Version of IPFS Desktop: 0.16.2

Describe the bug
npm warns about a deprecated module called requests

npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142

Cooking Recipes - Around 50GB of formatted and unformatted cooking recipes. Source

This one does not seem to have any providers. ipfs dht findprovs QmTXo6GforwsuGAd8behjgvKCsMMBdG1xMZJF4qa9W7CHB doesn't print anything.

Siderus Orion - Easy to use IPFS desktop client for macOS, Windows and Linux Source

This project is no longer active and the maintainer has taken it down

@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

Is your feature request related to a problem? Please describe.
On the Import page, clicking "import options" shows the desired import path that can be changed by the user. Unfortunately any changes to this setting will not be used the next time you go to the Import page.

Describe the solution you'd like
When focus of the text field is lost, it should save to the extension's storage so

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
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. upload a file whit exists same name

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots

![image

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 Naming Providers support. Naming providers can be either DNS - for use with DNSLink - or even naming services such as ENS and IPNS.

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

Status

The number of notifications I have now is killing me xD There should be a clear all button and perhaps a record in the blockchain of the timestamp it was clicked so as to not re-display them when the browser cache is cleared.