What do you mean “break further down from event kind”?
You mean the kinds the DVM will take into account? That’s a param for the DVM:
[ “param”, “kinds”, … ]
What do you mean “break further down from event kind”?
You mean the kinds the DVM will take into account? That’s a param for the DVM:
[ “param”, “kinds”, … ]
No, the kinds to classify nip89s apps by. Right now it's only by event kind. We need to do “I use DVM npub1XX for kind:68001:job-req-feed-generation"
So, you can filter nip89 apps not only by kind, but by each individual type job being offered.
Each job type will be it’s own kind by suggestion from nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6
I initially left just one and then a j tag but a kind per job type makes much more sense.
(I haven’t published the revised NIP yet; I’ll try to push it today)
Yep, that makes a lot more sense :)