# IPFS Connectivity Text for FFMPEG

> A local IPFS gateway wasn't found. You're now using the fallback gateway from dweb.link.

* s/fallback/public/
* s/from/at/
* simplify by just referring to IPFS instead of gateway

Updated: "IPFS does not appear to be running. You're now using the public gateway at dweb.link."

> You should host your own gateway instead which is done by having IPFS run locally.

* needs to say why
* simplify by just referring to IPFS instead of gateway

Updated: "Installing IPFS locally is recommended to improve performance and reliability, and not share all your activity with a single IPFS gateway."

> There are multiple options to define this gateway. The below options are in order of precedence:

* s/define this gateway/configure IPFS connectivity/
* "precedence" isn't clear - maybe should be in order of preference - so in reverse order? WDYT?

> 1. Define a -gateway <url> to the gateway without trailing forward slash.

* Be explicit that this is a CLI param
* Should this be clear that it's an IPFS gateway, eg rename param "ipfs-gateway"?

Updated: "Call ffmpeg with a gateway param, without a trailing slash: -gateway <url>"

> 2. Define $IPFS_GATEWAY with the full http link to the gateway without trailing forward slash.

* Be explicit that this is an env var

Updated: "Define an $IPFS_GATEWAY environment variable with the full HTTP URL to the gateway without trailing forward slash."

> 3. Define $IPFS_PATH and point it to the IPFS data path.

* Be explicit that this is an env var
* Give an example of the data path

Updated: "Define an $IPFS_PATH environment variable and point it to the IPFS data path - this is typically ~/.ipfs"

> 4. Have IPFS running in your local user folder (under $HOME/.ipfs).

* why does it matter where ipfs is running from?

> In all path cases, a file named gateway is expected. See https://github.com/ipfs/specs/issues/261 for more information.

* hrm, the user should never have to do this