ipfs/ipfs-companion

Allow setting "IPFS Node type" to none

Open

#1,045 opened on Jan 13, 2022

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (1,992 stars) (364 forks)batch import
P2effort/hoursexp/intermediatehelp wantedkind/enhancement

Description

Is your feature request related to a problem? Please describe. Some users may not want to run an external nor internal IPFS node in their browser, this may be due to resource constraints, bandwidth restrictions, etc.

Describe the solution you'd like Allow users to set "IPFS Node type" to none so ipfs:// and ipns:// addresses will simply redirect to *.{ipfs,ipns}.gateway.tld depending on the Gateway URL set in the settings. This allows src="ipfs://Qmfoo" to work without needing to run a node which benefits more minimal setups, it could also be useful as a fallback option if the internal node is found to of failed in some way.

Describe alternatives you've considered Alternative names for the none type, maybe redirect or Gateway URL to make it more descriptive?

Additional context I mainly got this idea after a user in the IPFS Matrix room was initially confused as to why it was required for you to run a node, they downloaded the extension and assumed that was all that was needed for ipfs:// links to work, but, it did not.

Contributor guide

Allow setting "IPFS Node type" to none · ipfs/ipfs-companion#1045 | Good First Issue