IPFS

UX problem

if someone pins something via pin remote add but their node is in offline mode, it just hangs forever and fails to pin the thing in a very opaque way

Potential fix

When in offline mode, we could check if CID is present in local datastore, and if so, show a warning that node is offline and pinning may fail if there is no other provider.

The check for presence in lo

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 i18next-node-fs-backend

npm WARN deprecated i18next-node-fs-backend@2.1.3: replaced by i18next-fs-backend

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

Describe the bug
Any number of peers past 1000 gets cut of in the toolbar
To Reproduce
Steps to reproduce the behaviour:

1. Connect to over 1000 peers (Enabling AcceleratedDHTClient and DHT server mode helps with that)
2. Look at the extension icon

Expected behaviour
The number does not get cut off

Screenshots
<img width="32" alt="Screen Shot 2021-08-05 at 12 37 28"

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/

ipfs-webui had admin-level access to IPFS node (minus private keys, which are not exposed over HTTP).

Would not hurt to add a basic warning when a less technical user is social-engineered into pasting something to the console.

Prior art from Discord:

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.