diff options
| author | Semisol <45574030+Semisol@users.noreply.github.com> | 2023-03-13 04:43:17 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-03-13 04:43:17 +0300 |
| commit | fffe868a405c9283e0a7a6947326e8c00c12aee7 (patch) | |
| tree | 66a79881a16c61909a18051639e638cfc87eb440 /39.md | |
| parent | a9139ee9a4e7f4859ab9ed1681cc70b9da58508a (diff) | |
NIP-39: minor readability changes
adds newlines in some places to make it more readable
Diffstat (limited to '39.md')
| -rw-r--r-- | 39.md | 12 |
1 files changed, 8 insertions, 4 deletions
| @@ -39,24 +39,28 @@ Identity names SHOULD be normalized if possible by replacing uppercase letters w | |||
| 39 | 39 | ||
| 40 | ### `github` | 40 | ### `github` |
| 41 | 41 | ||
| 42 | Identity: A GitHub username. | 42 | Identity: A GitHub username. |
| 43 | |||
| 43 | Proof: A GitHub Gist ID. This Gist should be created by `<identity>` with a single file that has the text `Verifying that I control the following Nostr public key: <npub encoded public key>`. | 44 | Proof: A GitHub Gist ID. This Gist should be created by `<identity>` with a single file that has the text `Verifying that I control the following Nostr public key: <npub encoded public key>`. |
| 44 | This can be located at `https://gist.github.com/<identity>/<proof>`. | 45 | This can be located at `https://gist.github.com/<identity>/<proof>`. |
| 45 | 46 | ||
| 46 | ### `twitter` | 47 | ### `twitter` |
| 47 | 48 | ||
| 48 | Identity: A Twitter username. | 49 | Identity: A Twitter username. |
| 50 | |||
| 49 | Proof: A Tweet ID. The tweet should be posted by `<identity>` and have the text `Verifying my account on nostr My Public Key: "<npub encoded public key>"`. | 51 | Proof: A Tweet ID. The tweet should be posted by `<identity>` and have the text `Verifying my account on nostr My Public Key: "<npub encoded public key>"`. |
| 50 | This can be located at `https://twitter.com/<identity>/status/<proof>`. | 52 | This can be located at `https://twitter.com/<identity>/status/<proof>`. |
| 51 | 53 | ||
| 52 | ### `mastodon` | 54 | ### `mastodon` |
| 53 | 55 | ||
| 54 | Identity: A Mastodon instance and username in the format `<instance>/@<username>`. | 56 | Identity: A Mastodon instance and username in the format `<instance>/@<username>`. |
| 55 | Proof: A Mastodon post ID. This post should be published by `<username>@<instance>` and have the text `Verifying that I control the following Nostr public key: "<npub encoded public key>"`. | 57 | |
| 58 | Proof: A Mastodon post ID. This post should be published by `<username>@<instance>` and have the text `Verifying that I control the following Nostr public key: "<npub encoded public key>"`. | ||
| 56 | This can be located at `https://<identity>/<proof>`. | 59 | This can be located at `https://<identity>/<proof>`. |
| 57 | 60 | ||
| 58 | ### `telegram` | 61 | ### `telegram` |
| 59 | 62 | ||
| 60 | Identity: A Telegram user ID. | 63 | Identity: A Telegram user ID. |
| 64 | |||
| 61 | Proof: A string in the format `<ref>/<id>` which points to a message published in the public channel or group with name `<ref>` and message ID `<id>`. This message should be sent by user ID `<identity>` and have the text `Verifying that I control the following Nostr public key: "<npub encoded public key>"`. | 65 | Proof: A string in the format `<ref>/<id>` which points to a message published in the public channel or group with name `<ref>` and message ID `<id>`. This message should be sent by user ID `<identity>` and have the text `Verifying that I control the following Nostr public key: "<npub encoded public key>"`. |
| 62 | This can be located at `https://t.me/<proof>`. \ No newline at end of file | 66 | This can be located at `https://t.me/<proof>`. |