upleb.uk

Public git repos — served from a NIP-34 GRASP relay at git.upleb.uk

summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorWilliam Casarin <jb55@jb55.com>2022-11-10 12:14:18 -0800
committerWilliam Casarin <jb55@jb55.com>2022-11-10 12:20:32 -0800
commit7569773ad6e162333155905f9f1ea620c732ff71 (patch)
tree2feb30e506692285b790606c36c4510c385f88a3
parente7f74d21c48e255181d93eda317f36f9702a14ad (diff)
NIP-20: add a note about client handling
-rw-r--r--20.md13
1 files changed, 13 insertions, 0 deletions
diff --git a/20.md b/20.md
index e76942a..9a96f6d 100644
--- a/20.md
+++ b/20.md
@@ -68,6 +68,19 @@ Event rejected, insufficient proof-of-work difficulty
68 ["OK", "b1a649ebe8...", false, "pow: difficulty 26 is less than 30"] 68 ["OK", "b1a649ebe8...", false, "pow: difficulty 26 is less than 30"]
69 69
70 70
71
72Client Handling
73---------------
74
75`messages` are meant for humans, with `reason:` prefixes so that clients can be slightly more intelligent with what to do with them. For example, with a `rate-limited:` reason the client may not show anything and simply try again with a longer timeout.
76
77For the `pow:` prefix it may query relay metadata to get the updated difficulty requirement and try again in the background.
78
79For the `invalid:` and `blocked`: prefix the client may wish to show these as styled error popups.
80
81The prefixes include a colon so that the message can be cleanly separated from the prefix by taking everything after `:` and trimming it.
82
83
71Future Extensions 84Future Extensions
72----------------- 85-----------------
73 86