diff options
| author | jiftechnify <jiftech.stlfy@gmail.com> | 2023-05-16 21:50:04 +0900 |
|---|---|---|
| committer | fiatjaf_ <fiatjaf@gmail.com> | 2023-05-17 12:38:16 -0300 |
| commit | ccbdfb95c198c385595c18edac09d9c830fd9406 (patch) | |
| tree | 07ff8b9b9b72ee5d09ce8319ac13eb236dd04971 /30.md | |
| parent | 835ec2614164c593e686e829aae6cbac64997ae8 (diff) | |
allow underscores in an emoji shortcode
Diffstat (limited to '30.md')
| -rw-r--r-- | 30.md | 4 |
1 files changed, 2 insertions, 2 deletions
| @@ -14,7 +14,7 @@ Custom emoji may be added to **kind 0** and **kind 1** events by including one o | |||
| 14 | 14 | ||
| 15 | Where: | 15 | Where: |
| 16 | 16 | ||
| 17 | - `<shortcode>` is a name given for the emoji, which MUST be comprised of only alphanumeric characters. | 17 | - `<shortcode>` is a name given for the emoji, which MUST be comprised of only alphanumeric characters and underscores. |
| 18 | - `<image-url>` is a URL to the corresponding image file of the emoji. | 18 | - `<image-url>` is a URL to the corresponding image file of the emoji. |
| 19 | 19 | ||
| 20 | For each emoji tag, clients should parse emoji shortcodes (aka "emojify") like `:shortcode:` in the event to display custom emoji. | 20 | For each emoji tag, clients should parse emoji shortcodes (aka "emojify") like `:shortcode:` in the event to display custom emoji. |
| @@ -53,4 +53,4 @@ In kind 1 events, the `content` should be emojified. | |||
| 53 | "pubkey": "79c2cae114ea28a981e7559b4fe7854a473521a8d22a66bbab9fa248eb820ff6", | 53 | "pubkey": "79c2cae114ea28a981e7559b4fe7854a473521a8d22a66bbab9fa248eb820ff6", |
| 54 | "created_at": 1682630000 | 54 | "created_at": 1682630000 |
| 55 | } | 55 | } |
| 56 | ``` \ No newline at end of file | 56 | ``` |