nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s would you use a DVM that dubs video?

nostr:note1e5fq59jnlyeq6qjjfva4qhhfucxafj8m4v3u2jgy78neae68al6sxw63wd

Reply to this note

Please Login to reply.

Discussion

10000%

publish it!

Would this be DVM be Kind 65006 then from your NIP90 implementation? How would I reserve that number?

No, use a new kind in the video manipulation range. Look at the repo. Just send a PR reserving it and we can iterate on the details on the PR 🙌

https://github.com/nostr-protocol/data-vending-machines

Sick! Just created the pull request! Looks like it’ll be kind 5201 based on the range in the repo. Let me know your thoughts and feedback when you have time.

Awesome! I’ll have a look in a few hours 🙌

Left a minor comment

Just committed the requested change 🙏

One more small thing I didn’t see before

Thinking about this more and wondering instead if a DVM if it should be natively accessible in the client by commenting in a Kind 1 message

As opposed to forcing the user to go to some other DVM client

The “DVM” in this case would be listening for video reply comments where it’s “npub” gets invoked and would then reply back with content