I was looking into starting go-ipfs with additional flags: --enable-pubsub-experiment (pubsub) and --enable-namesys-pubsub (IPNS over pubsub) and the main concern I've found was use of resources:

In order to enab

I'd like IPFS companion to use a local gateway without exposing a local IPFS API endpoint. Unfortunately, if I do this, companion will direct all dnslink queries to the public gateway because my local IPFS node "has no peers".

If I configure companion to use a specific IPFS gateway, I expect it to always use that gateway.

There is a minor misspelling in the source file qri/api/context.go. The word "collissions" on line 14 should be changed to "collisions".

Note: Need to wait until ipfs-shipyard/ipfs-webui#1615 is merged to avoid throwing more conflicts on that PR's pile.

The need

Standardize visual presentation of modals throughout Web UI, including the following:

• Darker primary action text
• (Possibly) left-aligning modal content, though need to investigate how this works with code snippets etc
• Possibly li

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

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

If a user writes a subgraph referencing contract addresses from (for example) a testnet, and then accidentally deploys the subgraph to a graph node running mainnet, the subgraph will run but won't find any events. We can provide a better experience using eth_getTransactionCount to check that the contract addresses exist on

Please add a sign up button to main page.

This meta issue contains various ideas that may never be implemented, it's a good place to put things that could create useless noise in the issues section

Doc

• add various demonstration gifs in README.md files (#2080)
• add graphs (flow, DAG) to explain some particular parts

Code Quality

• switch moment.js usage to day.js and remove moment.js (#2174)

Bots