rain8128
c233b3ffd0
Update 02.md
2023-03-06 16:37:42 -03:00
shafemtol
b8e657bb37
NIP-08: Specify nonmatch behavior
2023-03-05 22:26:09 -03:00
ennmichael
d97928bd90
avoid using substr in NIP-04 example
2023-03-05 22:09:59 -03:00
Josua Schmid
c74f11b7a9
Update NIP-01 to clarify pubkey reference
...
We mean to reference any public key. "the key" was a bit unspecific.
2023-03-03 18:59:37 -03:00
ennmichael
ab6308c29a
NIP-20: fix a typo
2023-03-02 21:36:15 -03:00
c4949ea707
NIP-78: app-specific data.
2023-03-01 10:03:25 -03:00
b549a9809f
Update README.md
...
fixed a tiny tipo
2023-02-27 19:56:50 -03:00
Marco Argentieri
d70959aee6
Amend nip46 describe and delegate methods ( #304 )
2023-02-27 14:22:46 -03:00
Ricardo Arturo Cabral Mejía
2bf08b3487
docs: add nip-58 to readme
2023-02-25 16:01:02 -03:00
Mike O'Bank
5a80a906d4
Improve <subscription_id> specification
...
- "random" is not an accurate description
- I've noticed long (sha256 hashes in hex) being rejected by some relays. So there seems a need to specify a max length.
- "non empty", cause an empty string could be interpreted as `null`
To be decided:
- Max length number
- Are `subscription_id`s case sensitive?
- Will `subscription_id`s be white space trimmed?
2023-02-25 15:55:28 -03:00
Callum Macdonald
ab1f26a3fd
Add browsers to the extension list
2023-02-25 15:54:52 -03:00
379252f992
explicitly prohibit markdown on kind:1.
2023-02-25 13:54:27 -03:00
barkyq
127d5518bf
relay hint language update ( #291 )
2023-02-23 16:20:10 -03:00
Ricardo Arturo Cabral Mejía
405cf480e9
docs: add nip-58 badge event and profile badges ( #229 )
2023-02-22 22:11:55 -03:00
Brandon Lucas
2a4c44035e
Fix minor typo
...
Fix spelling of `coordinates` in Note
2023-02-22 21:49:29 -03:00
Alejandro Gomez
050317409d
NIP-57: add optional a tag for tipping nip-33 coordinates
2023-02-22 12:42:01 -03:00
Marco Argentieri
b1a5ad355a
NIP-46: Nostr Connect 🔌 connect your Nostr app with remote signing devices ( #153 )
2023-02-20 16:26:13 -03:00
Mike Dilger
524caa3856
More explicit explanation of the meaning of read and write relays
2023-02-19 17:56:30 -03:00
Semisol
6849f3bdf4
NIP-57: Add amount tag to zap request
2023-02-16 12:25:47 -03:00
SondreB
2a2c665e27
Update the key examples with a key pair
2023-02-14 19:44:11 -03:00
Adam B
23b863ad65
Minor change to make delegation token/string naming consistent
2023-02-14 14:33:50 -03:00
Chemaclass
04e7f0cef8
Fix readme sorting NIP-56/57
2023-02-14 14:33:01 -03:00
c80cb09e80
simplify description.
2023-02-13 14:06:35 -03:00
b00888cec7
add nip23 to list.
2023-02-13 09:00:09 -03:00
0499d52ef2
Merge pull request #220 from nostr-protocol/longform
2023-02-13 08:50:55 -03:00
b4493aa56a
rename coordinates: nitem->naddr, "i"->"a"
2023-02-13 08:47:23 -03:00
a85067ec68
Merge branch 'master' into longform
2023-02-13 08:42:47 -03:00
William Casarin
17ffd3ee4e
NIP-57: Lightning Zaps ( #224 )
2023-02-13 08:36:04 -03:00
Jeff Thibault
ffe6a49557
NIP-04: clarify how shared secret is computed
2023-02-10 10:34:45 -03:00
Matthew Lorentz
9d0b59d381
Revert "Merge pull request #227 from erikwestra/nip-05-security-proposal"
...
This reverts commit 6d55463c89d87763781da1a090160b
2023-02-09 16:59:50 -05:00
d87763781d
clarify and change account account_uris to account_paths.
2023-02-09 17:13:35 -03:00
mplorentz
6d55463c89
Merge pull request #227 from erikwestra/nip-05-security-proposal
...
Nip 05 security proposal
2023-02-09 14:43:06 -05:00
a1a090160b
rewrite ranges.
2023-02-09 13:43:53 -03:00
643de1b7da
change kind:1 description on README.
2023-02-09 13:41:54 -03:00
e91f8f2221
fix title->content typo.
2023-02-09 06:59:52 -03:00
Jimmy Song
a9dd1ce771
Added clarification for signature to be in hex
2023-02-08 16:39:31 -03:00
3f39a241b1
Revert "[NIP-26] Fix for multiple kinds in delegation conditions ( #208 )"
...
This reverts commit 6a11f4d4cd
2023-02-08 08:36:07 -03:00
William Casarin
f9e38ed00f
NIP-56: Reporting ( #205 )
...
Co-authored-by: Semisol <45574030+Semisol@users.noreply.github.com>
Co-authored-by: Leo Wandersleb <leo@leowandersleb.de>
2023-02-07 18:15:38 -03:00
Mike Dilger
b99ca748c8
Put NIP-65 in the readme contents
2023-02-07 17:43:22 -03:00
87525b0d20
Merge pull request #218 from mikedilger/nip65
2023-02-07 06:00:30 -03:00
Lio李歐
8c031aa710
Update README.md kind table ( #226 )
2023-02-06 21:15:08 -03:00
Erik Westra
2f72defd59
Merge branch 'nostr-protocol:master' into nip-05-security-proposal
2023-02-07 13:08:58 +13:00
e939751f04
Update 23.md
...
Co-authored-by: mplorentz <mplorentz@users.noreply.github.com>
2023-02-06 15:10:50 -03:00
694f2f056e
Update 23.md
...
Co-authored-by: mplorentz <mplorentz@users.noreply.github.com>
2023-02-06 15:09:32 -03:00
kdmukai
6a11f4d4cd
[NIP-26] Fix for multiple kinds in delegation conditions ( #208 )
2023-02-06 12:21:58 -03:00
5a5ef4a82d
encode kind into nitem
2023-02-06 08:11:11 -03:00
ea48646a0f
get rid of YAML frontmatter.
2023-02-05 21:18:38 -03:00
16b50a481f
rename nref to nitem and use the i tag.
2023-02-05 20:23:59 -03:00
Erik Westra
cf053d2a41
Suggested additions to NIP-05 to enhance security
...
Proposing a couple of changes to the NIP-05 protocol to reduce the chance of fraudulent use of "verified" public keys. At present, I could create an account on a well-known verifying server under a random name, and then send DMs pretending to be someone else, and there's no easy way for users to tell who the verifying account actually belongs to.
As well as displaying the name of the account on the verifying server, this PR suggests an enhancement to the JSON data being returned so that clients can redirect the user to the user's profile page on the server. This will make it much easier for users to check that someone who claims to have verified their Nostr account is who they claim to be.
2023-02-06 10:11:26 +13:00
Mike Dilger
870f96b988
spelling and wording
2023-02-05 03:56:07 +13:00
