npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/nips, branch preventEmptyTags [no description] https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/nips/atom?h=preventEmptyTags 2024-04-24T16:18:27+00:00 Require tags to have at least one string 2024-04-24T16:18:27+00:00 Leo Wandersleb leo@leowandersleb.de 2024-04-24T16:18:27+00:00 urn:sha1:9b7883e98b892db176c1528ada25b4b062438b1b fixes #1193 Merge pull request #1187 from AsaiToshiya/AsaiToshiya-patch-7 2024-04-22T03:37:50+00:00 Alex Gleason alex@alexgleason.me 2024-04-22T03:37:50+00:00 urn:sha1:cab47cf0f179f578bf9d3be0e61a5a2224053f33 README: add status kinds of NIP-34 README: add status kinds of NIP-34 2024-04-22T03:35:48+00:00 Asai Toshiya to.asai.60@gmail.com 2024-04-22T03:35:48+00:00 urn:sha1:eb3a857288fe99d99b73e07dfa28ac548fc10efb NIP-34: add status events 2024-04-17T20:46:34+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-03-07T10:21:06+00:00 urn:sha1:403b5199a490b6a148063003e00924f5e79ba36c merge-commit and applied-commit-id tags enable discussion of patches to be mapped to lines of code accepted into the master branch NIP-34: clarify cover letters 2024-04-17T20:46:34+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-03-07T09:20:25+00:00 urn:sha1:0b62729e318497922822c39471ab31a869563ba5 remove cover letters from 'possible things to be added later' and add a clarification that can they can be added through patches NIP-34: optional tags to improve discoverability 2024-04-17T20:46:34+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-03-07T09:01:19+00:00 urn:sha1:8225a018c72c4d11b575ed4e57fa587d08c09027 earliest-unique-commit r tag enables clients to: - retrieve all repo events refering to a local git repo - group repo events with different identifers that refer to same repo - retrieve all patches for a local repo, irespective of the tagged repo event current-commit-id r tag enables clients to prevent accidental submission of a patch, which has already been proposed root-revision tag enables clients to filter out proposal revisions from a list of proposals NIP-34: optional additional repo maintainers 2024-04-17T20:46:34+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-03-07T08:25:49+00:00 urn:sha1:cb0d35a5f9f1b88a270f7fbbfbdb97e095e28d56 can be used by clients to tag multiple maintainers in patches helps clients identify whether multiple repo events for the same repository are complementary or in competion NIP-34: add repo-id standard 2024-04-17T20:46:34+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-03-07T08:03:48+00:00 urn:sha1:46ea8dcf9cedd1f64e9444b70ac0ed24e40bbe1a suggested guidance for repo-id NIP-34: clarify nip10 thread application 2024-04-17T20:46:34+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-03-07T07:59:16+00:00 urn:sha1:d607a288b5db72a84f3d6cc8fd42304d31e1f66b for consistancy and so that the intended order of patches is easier to ascertain enables additional patches to be appended to a patch set, supporting a PR-like workflow alongside patch-over-email-like workflow Clarify use of ambiguous terminology in spec of bunker token 2024-04-10T15:53:59+00:00 kuiperanon 164939804+kuiperanon@users.noreply.github.com 2024-04-09T16:25:05+00:00 urn:sha1:b765b3c0301958d46115b834872bbd0c8bac588c It's very confusing as to whether it refers to remote user pubkey vs remote signer pubkey. This is complicated further by the typo in the explanation of "remote signer pubkey".