npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/nips/05.md, branch Giszmo-patch-2 [no description] https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/nips/atom?h=Giszmo-patch-2 2023-04-07T14:45:06+00:00 fix grammar and typos 2023-04-07T14:45:06+00:00 vivganes vivek@vivekganesan.com 2023-04-07T12:08:03+00:00 urn:sha1:3cec80d99ebbee6b72aae31f1856181d04971244 Revert "Merge pull request #227 from erikwestra/nip-05-security-proposal" 2023-02-09T21:59:50+00:00 Matthew Lorentz matt@lorentz.is 2023-02-09T21:59:50+00:00 urn:sha1:9d0b59d381a3d70dcf9947fd6bb194b259b05f9e This reverts commit 6d55463c89e6c944bcd49c93f90b16a0ce5fce1e, and d87763781dc1213d7c1b53ab0a4172f8237cbdf3 reversing changes made to a1a090160b610c69513725ae871efdb346cbd82d. clarify and change account account_uris to account_paths. 2023-02-09T20:13:35+00:00 fiatjaf fiatjaf@gmail.com 2023-02-09T20:13:35+00:00 urn:sha1:d87763781dc1213d7c1b53ab0a4172f8237cbdf3 Suggested additions to NIP-05 to enhance security 2023-02-05T21:11:26+00:00 Erik Westra erik@global.id 2023-02-05T21:11:26+00:00 urn:sha1:cf053d2a418db8ea489f6857d017eacc12cc97b5 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. fix: typo 2023-02-03T13:40:57+00:00 Jeff Jing zgayjjf@qq.com 2023-02-03T05:04:21+00:00 urn:sha1:025beb332cfb90e56ce39c27bba909f05b04147d NIP05 Improve CORS header check command 2023-01-06T15:18:20+00:00 Luke Childs lukechilds123@gmail.com 2023-01-06T12:37:55+00:00 urn:sha1:01a3090c6ab872621e01019c58f8cac38c354c25 merge NIP-35 into NIP-05. 2023-01-04T13:34:24+00:00 fiatjaf fiatjaf@gmail.com 2023-01-04T13:34:24+00:00 urn:sha1:8c3c42171503fd07e24bb8681fc01419974a2ac0 clarify nip19 purpose. 2022-12-30T00:02:32+00:00 fiatjaf fiatjaf@gmail.com 2022-12-30T00:02:32+00:00 urn:sha1:0ca9be82247d9c1f93ac4319042d2364b7d18b30 Make it clear that NIP-05 Keys should be in Hex 2022-12-29T23:52:54+00:00 Lyle Pratt lylepratt@gmail.com 2022-12-29T23:38:14+00:00 urn:sha1:a37a27afb905b71c1beda7c5a9ec12938d8b8a87 There has been some confusion about whether npub keys are supported by this spec. According to @fiatjaf only Hex keys are supported. https://twitter.com/fiatjaf/status/1608606752987316224?s=20&t=6fJLD3077byuoTm96kva1g update NIP-05 addressing reflectivity. (#128) 2022-12-29T14:01:35+00:00 majestrate jeff@lokinet.io 2022-12-29T14:01:35+00:00 urn:sha1:d41834fa5169d15ffd1519a773ee495c6076ecd3