danieldaquino on Nostr: I introduced the idea of tasks mostly as a generic thing, for task-tracking ...
I introduced the idea of tasks mostly as a generic thing, for task-tracking applications that are not git-specific.
However, I also imagined that there are people using NIP-34 issues already, and that they might want to track them in a workflow. So in the "XXD" draft, I introduce workflows that can track any nostr kind, including git issues and more generic tasks. The intent was to keep compatibility with NIP-34, but also provide a more generic task type for non-git applications.
Published at
2025-05-09 02:04:55Event JSON
{
"id": "e61eb0eefb8194054b08d52bfc657c6488a4ac62dabc3294202098241300a5d2",
"pubkey": "8b2be0a0ad34805d76679272c28a77dbede9adcbfdca48c681ec8b624a1208a6",
"created_at": 1746756295,
"kind": 1,
"tags": [
[
"e",
"22259d28ac5374102c6844d1c5dac9d83da09ba3f328e183f6b89abd32daea80",
"",
"root"
],
[
"p",
"a9434ee165ed01b286becfc2771ef1705d3537d051b387288898cc00d5c885be"
]
],
"content": "I introduced the idea of tasks mostly as a generic thing, for task-tracking applications that are not git-specific.\n\nHowever, I also imagined that there are people using NIP-34 issues already, and that they might want to track them in a workflow. So in the \"XXD\" draft, I introduce workflows that can track any nostr kind, including git issues and more generic tasks. The intent was to keep compatibility with NIP-34, but also provide a more generic task type for non-git applications.",
"sig": "c9281da6fc9ad95e251f9b7ead303a2e153d143628c8d7b33c9dd7acd582638f173a0d6d89e38f7f0fa328d935a3f4c784557e6f97b477261fd2ae8e6c3ea154"
}
