From 70c92a56db67bf14cb993ab6313359609debd6d7 Mon Sep 17 00:00:00 2001 From: Anurag Lint Date: Fri, 16 Aug 2024 13:14:22 +0200 Subject: [PATCH] The 'content' field must be empty to send possible new attacks --- 100.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/100.md b/100.md index 09cd33c2..236facfb 100644 --- a/100.md +++ b/100.md @@ -29,7 +29,7 @@ This is the public key of the event signer and the corresponding public key asso #### Field `content` -The `content` field may include a description of the reason why the user wants to be locked, although it can be left empty. +The `content` field must be empty to prevent the attacker from publishing a malicious message that could result in a new attack vector. ##### Example @@ -53,7 +53,7 @@ To lock a user, clients will have an option that allows performing this action. Clients that implement this NIP MUST check if a `kind:1000` event has been issued. If so, they MUST either hide the events of that user or indicate through some visual mechanism that the user authoring those events has been locked. -Optionally, clients CAN display the `1000` locking event, indicating the reason included in the `content` field. If this field is empty, they can display a generic message. They can also indicate in the user's profile that the user has been locked. +Optionally, clients CAN display the `1000` locking event, indicating a message that the user may have been compromised or that the user has been blocked. They can also indicate in the user's profile that the user has been locked. #### Optional