Dustin Dannenhauer on Nostr: I don’t like using kind 6xxx for both job results and schema definitions. Also, I ...

I don’t like using kind 6xxx for both job results and schema definitions. Also, I don’t think we should be trying to solve privacy and schema definitions at the same time. Privacy needs a whole other angle, and I think it’s important to keep a good flow without privacy for workflows that don’t need it (which also makes it easy for new devs to see what’s happening to start to participate). I have some other thoughts on privacy we should talk about sometime…


What if, for DVM schema requests we used a kind number of an int + the kind request? Like 35300 instead of 5300? It really does feel like a separate flow, that should then kick off the actual DVM job request and result response. Overloading kinds only makes things way more complicated, especially for clients