diff --git a/src/_blog/ipfs-as-a-first-class-citizen-in-ffmpeg-who-s-next.md b/src/_blog/ipfs-as-a-first-class-citizen-in-ffmpeg-who-s-next.md index 032d74e2..e27dde1d 100644 --- a/src/_blog/ipfs-as-a-first-class-citizen-in-ffmpeg-who-s-next.md +++ b/src/_blog/ipfs-as-a-first-class-citizen-in-ffmpeg-who-s-next.md @@ -70,11 +70,11 @@ I wanted to do much more in the IPFS ecosystem, specifically to enable broad eco Starting in [FFmpeg 5.1](https://github.com/FFmpeg/FFmpeg/blob/master/Changelog) you’ll enjoy “native feeling” IPFS support. The support is implemented through rewriting your `ipfs url` to a url that your gateway will handle. -ipfs://QmbGtJg23skhvFmu9mJiePVByhfzu5rwo74MEkVDYAmF5T +ipfs://QmbGtJg23skhvFmu9mJiePVByhfzu5rwo74MEkVDYAmF5T to: -http:///ipfs/QmbGtJg23skhvFmu9mJiePVByhfzu5rwo74MEkVDYAmF5T +http://<gateway>/ipfs/QmbGtJg23skhvFmu9mJiePVByhfzu5rwo74MEkVDYAmF5T * The red color is the auto-detected gateway to use. * The orange color is the protocol to use (can be either _ipfs_ or _ipns_). @@ -104,4 +104,4 @@ KODI and media aside, you can expect more broad ecosystem support for IPFS to be We are specifically keen on implementing IPFS in the lowest layers of the architecture to enable broad, transparent ecosystem support. Now that we have IPFS in FFmpeg, it is relatively easy to integrate it into anything that relies on FFmpeg. -There are more tools that we are considering integrating with IPFS, but we are also reliant on your input! We have set up an IPFS integration repository [here](https://github.com/ipfs/integrations). If you have a tool or application where you think IPFS support would be of value, please drop us a note! \ No newline at end of file +There are more tools that we are considering integrating with IPFS, but we are also reliant on your input! We have set up an IPFS integration repository [here](https://github.com/ipfs/integrations). If you have a tool or application where you think IPFS support would be of value, please drop us a note!