From acbc1c5fe582bd9dc43bc4e1351041baa6e79176 Mon Sep 17 00:00:00 2001
From: Tony Garnock-Jones <tonyg@leastfixedpoint.com>
Date: Mon, 23 Jan 2023 10:36:44 +0100
Subject: [PATCH] Link to FeepingCreature's post

---
 why-not-json.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/why-not-json.md b/why-not-json.md
index a4e950a..6d9334d 100644
--- a/why-not-json.md
+++ b/why-not-json.md
@@ -153,5 +153,9 @@ JSON itself does not offer any guidance for which of these options to
 choose. In many real cases on the web, poor choices have led to
 encodings that are irrecoverably ambiguous.
 
+**Update 20230123**. [This
+article](https://gist.github.com/FeepingCreature/d2fd982f485973a154abcaf0ccb4003c) discusses
+another subtle aspect of the problems caused by the lack of tagging in JSON.
+
 <!-- Heading to visually offset the footnotes from the main document: -->
 ## Notes