Replies on repo ↔ Issues on repo ↔ Tasks on anything
This is the confusion weird space Issues are in from my point of view.
GitHub doesn't have replies, nor tasks, so it seems like Issues just map onto any discussion, idea, bug, feature request, etc...
Whereas here we already have:
Discussions: replies, zap messages, community/group chat/thread/forum
Tasks: danieldaquino (npub13v4…l3l8)'s general spec, we're using in #communikeys
I don't see what's lost if you just use the same event kind (Task) for Issues on a repo.
Benefit is huge for product managers that have to manage projects beyond just repos.
And anything that is not a Task, is better suited for the reply / forum / chat sections.
I'm really trying to step away from copy-pasting GitHub UX. We have more (specific) content types here and can channel them according to our goals more efficiently.
nielliesmons / Niel Liesmons
npub149…g722q
2025-05-07 09:44:37
in reply to nevent1q…eltx
Author Public Key
npub149p5act9a5qm9p47elp8w8h3wpwn2d7s2xecw2ygnrxqp4wgsklq9g722qPublished at
2025-05-07 09:44:37Event JSON
{
"id": "f0b3bf4412b3fdeb25fb9a7ac106f07a2186791b1ee2bc0425a3c0eb556be9cb",
"pubkey": "a9434ee165ed01b286becfc2771ef1705d3537d051b387288898cc00d5c885be",
"created_at": 1746611077,
"kind": 1,
"tags": [
[
"e",
"ff361becddab3a2ebcb5cbcd9de2c68b263a3243170c85536bed388abc53966e",
"wss://niel.nostr1.com/",
"root",
"a9434ee165ed01b286becfc2771ef1705d3537d051b387288898cc00d5c885be"
],
[
"e",
"a155d6bd7c1e3207fedd672fa3fb53cb210f095398d4e163d93e4f052f533a31",
"wss://nos.lol/",
"reply",
"a008def15796fba9a0d6fab04e8fd57089285d9fd505da5a83fe8aad57a3564d"
],
[
"p",
"a9434ee165ed01b286becfc2771ef1705d3537d051b387288898cc00d5c885be",
"wss://nostr.wine/"
],
[
"p",
"a008def15796fba9a0d6fab04e8fd57089285d9fd505da5a83fe8aad57a3564d"
],
[
"p",
"8b2be0a0ad34805d76679272c28a77dbede9adcbfdca48c681ec8b624a1208a6"
],
[
"p",
"d04ecf33a303a59852fdb681ed8b412201ba85d8d2199aec73cb62681d62aa90"
],
[
"p",
"846ebf79a0a8813274ec9727490621ad423f16a3e474d7fd66e6a98bfe4e39a4"
],
[
"p",
"17538dc2a62769d09443f18c37cbe358fab5bbf981173542aa7c5ff171ed77c4"
],
[
"t",
"communikeys"
]
],
"content": "Replies on repo ↔ Issues on repo ↔ Tasks on anything\n\nThis is the confusion weird space Issues are in from my point of view. \n\nGitHub doesn't have replies, nor tasks, so it seems like Issues just map onto any discussion, idea, bug, feature request, etc... \n\nWhereas here we already have: \n\nDiscussions: replies, zap messages, community/group chat/thread/forum\nTasks: nostr:npub13v47pg9dxjq96an8jfev9znhm0k7ntwtlh9y335paj9kyjsjpznqzzl3l8's general spec, we're using in #communikeys\n\nI don't see what's lost if you just use the same event kind (Task) for Issues on a repo. \nBenefit is huge for product managers that have to manage projects beyond just repos.\nAnd anything that is not a Task, is better suited for the reply / forum / chat sections. \n\nI'm really trying to step away from copy-pasting GitHub UX. We have more (specific) content types here and can channel them according to our goals more efficiently. ",
"sig": "185000a9f3f9693d248268d80144e9cd0f4baa0da2a4191860dacc76adf1676901156b3452eefd58677b7bc6525932cba5ba090ce94d2d3356faef746d0eea10"
}