Event JSON
{
"id": "017df54760204baf6cd747b8187a374c15d714de411548b9c537c1092e8c6f9a",
"pubkey": "a008def15796fba9a0d6fab04e8fd57089285d9fd505da5a83fe8aad57a3564d",
"created_at": 1726735721,
"kind": 1621,
"tags": [
[
"alt",
"git repository issue: nip34 issues: compatibility with gitworkshop.dev and other clients"
],
[
"r",
"0e88ddbfbabec2b29a15e134277c1b364d836be0"
],
[
"a",
"30617:e4336cd525df79fa4d3af364fd9600d4b10dce4215aa4c33ed77ea0842344b10:voyage",
"wss://relay.mutinywallet.com/",
"root"
],
[
"p",
"e4336cd525df79fa4d3af364fd9600d4b10dce4215aa4c33ed77ea0842344b10"
]
],
"content": "nip34 issues: compatibility with gitworkshop.dev and other clients\n\nits not explicit in nip34 but gitworkshop.dev uses the first line of the content as the title of an issue. voyage is using the `subject` tag for titles.\nIt was probably a coin flip about which approach is better. using the first line of content, means it's less effort for other client to implement, and at a minimum they can just display the `content` and it will look fine.\nmany clients now display nip34 issues and expect the above format. This means in amethyst, Nostter, nostrudel, coracle, gitworkshop, etc your issues are getting displayed without their title.\nWould you consider switching approaches? The nip should probably be explicit about this.",
"sig": "6e4c8f9103664a78bf2a2459fbe0faafd399c5fb65180a6d1284535a66f740dcb1700ab097ca04e5426e2ca89ebda4ec179698f6b7f84734b8ca6442e6616817"
}