I will take your suggestions into serious consideration. If you're looking for something more like a narrative, you'd find that here (in the UI repo readme):

https://github.com/vcavallo/catallax-ui/blob/master/README.md

and here (in the Khatru POC implementation):

https://github.com/vcavallo/khatru/tree/escrow/examples/escrow

Reply to this note

Please Login to reply.

Discussion

After reading, I tried to come up with a better NIP design than yours. I failed.

The best I could think was that communication between agents would be private and not necessary through Nostr events, but could be. And the only public trails would be escrows announcing themselves (should be using a replaceable kind instead), task proposals -- published by whoever is proposing them, and then a summary of what happened, published by the escrow.

Mostly because no one is interested in what happens in between.

I much appreciate your attention and attempt to improve my rotten foundations! 😆

I'll reconsider things, adjust my relay and client and re-draft the NIP.

Here's the case for doing as much (and as little!) as possible in nostr. This is terrible UX and nobody will use it:

nostr:nevent1qqsgd0nt86hakncxas6ehskcqrt0rawqx92ktakzy7dnnqhm7xgtyhcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygy5y90592trxhy8lju73qdqhwmzhxne25v7zzw0t7wjaashdq0kygpsgqqqqqqsgnxnlf

Almost as bad as "if you want to reply to my nostr note, post the reply on your own twitter feed and tag me in a new note you write with a link to the tweet"

Can you make the case clearer for me? Not sure I understand and eager to learn?