Nice. I'd love that too. I've comment on the nip PR you just directed me to but I'll include my comments here for anyone who is interested
Love to see this and look forward to adding releases to nip34 clients.
Instead of referencing a nip34 announcement event in `repository` tag it should be referenced with an `a` tag so it will be indexed by relays. clients should look for an a tag with `30617` kind if repository is omitted.
The release event:
1. should be moved into this nip from the example section of nip51.
2. should be immutable and not a replaceable event. then trust attestations could be placed on the event eg. validation that the checksums of a reproducible build match.
3. should include an optional `["commit-id","<SHA1-commit-id-used-to-build-release>"]` tag
From a style point of view: I see most nips describe events using jsonc rather than a table of tags, which is easier to read. Is this now the standard?
lastly, the app event could support the maintainers tag like nip34 announcements This means clients could optionally interpret app events by the pubkeys listed with identical `d` tags as referring to the same app. `["maintainers", "<other-recognized-maintainer>", ...]`
DanConwayDev
npub15qy…yejr
2024-07-02 23:42:17
in reply to nevent1q…aw4n
Author Public Key
npub15qydau2hjma6ngxkl2cyar74wzyjshvl65za5k5rl69264ar2exs5cyejrPublished at
2024-07-02 23:42:17Event JSON
{
"id": "329fa898bdf5f3e34fde426d04605352c6677d6fc1542e50aabd894412753914",
"pubkey": "a008def15796fba9a0d6fab04e8fd57089285d9fd505da5a83fe8aad57a3564d",
"created_at": 1719956537,
"kind": 1,
"tags": [
[
"e",
"7fba60aa1cd8232156992ed5fe69a5c5cdd201b4b8bf2ade5152291036b2f67f",
"wss://relay.damus.io/",
"root"
],
[
"e",
"bfb858b7bc2fbfb72ded4e0f839799c75f0847b49b79134fc2a55c1e9459dbfc",
"wss://nos.lol/",
"reply"
],
[
"p",
"726a1e261cc6474674e8285e3951b3bb139be9a773d1acf49dc868db861a1c11",
"",
"mention"
],
[
"p",
"036533caa872376946d4e4fdea4c1a0441eda38ca2d9d9417bb36006cbaabf58",
"",
"mention"
]
],
"content": "Nice. I'd love that too. I've comment on the nip PR you just directed me to but I'll include my comments here for anyone who is interested\n\nLove to see this and look forward to adding releases to nip34 clients.\n\nInstead of referencing a nip34 announcement event in `repository` tag it should be referenced with an `a` tag so it will be indexed by relays. clients should look for an a tag with `30617` kind if repository is omitted.\n\nThe release event:\n1. should be moved into this nip from the example section of nip51.\n2. should be immutable and not a replaceable event. then trust attestations could be placed on the event eg. validation that the checksums of a reproducible build match. \n3. should include an optional `[\"commit-id\",\"\u003cSHA1-commit-id-used-to-build-release\u003e\"]` tag\n\nFrom a style point of view: I see most nips describe events using jsonc rather than a table of tags, which is easier to read. Is this now the standard?\n\nlastly, the app event could support the maintainers tag like nip34 announcements This means clients could optionally interpret app events by the pubkeys listed with identical `d` tags as referring to the same app. `[\"maintainers\", \"\u003cother-recognized-maintainer\u003e\", ...]` ",
"sig": "06cd03506c4ad2f50c9ccffb1a4fbb06df956d655b733aa0563f5227dc89099bd161ac2931e081e815f9c7b6a4cef677f3fceafab40e60dd47d15e446130889a"
}