This NIP keeps track of extra optional fields that can added to events which are not defined anywhere else but have become _de facto_ standards and other minor implementation possibilities that do not deserve their own NIP and do not have a place in other NIPs.
-`display_name`: an alternative, bigger name with richer characters than `name`. `name` should always be set regardless of the presence of `display_name` in the metadata.
-`bot`: a stringified boolean of "true" or "false" (case insensitive) to clarify that the content is entirely or partially the result of automation, such as with chatbots or newsfeeds.
The `content` field has been used to store the stringified JSON of metadata fields. It has been deprecated in favor of using tags. Clients SHOULD write metadata as both tags and legacy stringified JSON until a reasonable number of SDKs and popular clients on each platform have adopted using tags on the user metadata event to avoid introducing breaking changes.
-`{<relay-url>: {"read": <true|false>, "write": <true|false>}, ...}`: an object of relays used by a user to read/write. [NIP-65](65.md) should be used instead.
These tags may be present in multiple event kinds. Whenever a different meaning is not specified by some more specific NIP, they have the following meanings:
