From c5a2c245edf89e738273683d5b1145f299cdcb3d Mon Sep 17 00:00:00 2001 From: Martti Malmi Date: Tue, 28 May 2024 14:11:24 +0300 Subject: [PATCH] 116: event content *must* be JSON encoded --- 116.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/116.md b/116.md index 6737ddb..60e6427 100644 --- a/116.md +++ b/116.md @@ -14,7 +14,7 @@ Relays should parse the event directory from the event path `d` tag and index th For backward compatibility, the event directory should also be saved in the event's `f` tag (for "folder"), which is already indexed by some relay implementations, and can be queried using the `#f` filter. -Event content should be a JSON-encoded value. An empty object `{}` signifies that the entry at the event path is itself a directory. For example, when saving `user/profile/name`: `Bob`, you should also save `user/profile`: `{}` so the subdirectory can be listed under `user`. +Event content must be a JSON-encoded value. An empty object `{}` signifies that the entry at the event path is itself a directory. For example, when saving `user/profile/name`: `Bob`, you should also save `user/profile`: `{}` so the subdirectory can be listed under `user`. In directory names, slashes should be escaped with a double slash.