-`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.
A `fields` attribute may also be added to profile metadata to represent user-defined fields. It is an array name-value tuples, eg:
```json
[["<name>", "<value>"], ...]
```
In the context of a full metadata object:
```json
{
"name": "Alex",
"avatar": "https://...",
"fields": [
["Pronouns", "ye/haw"],
["Lifestyle", "vegan"],
["Color", "green"]
]
}
```
While protocol-level fields like `lud16` and `avatar` can influence the behavior of a user's account, custom fields are used for display purposes only. Clients should display custom fields in a confined area of the user's profile, and not make assumptions about their meaning.
Custom fields should be displayed in the order they are defined by the user, and entries may be duplicated. The name and value can be any string, although clients may truncate or ellipsize long values, and may limit the total number of fields displayed.
-`{<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:
