From c0c8c45a1119ca78771a99b075fa36f54f85da04 Mon Sep 17 00:00:00 2001
From: Chris Waring <106938+cwaring@users.noreply.github.com>
Date: Fri, 29 Jul 2022 22:34:28 +0100
Subject: [PATCH] fix: patch to disable emoji rendering
---
.../ipfs-as-a-first-class-citizen-in-ffmpeg-who-s-next.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
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 e27dde1d..c9534e64 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://<gateway>/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_).