Nostr Web Client

Trying to think of new DVM use cases.

This program uses nostr to fetch DVMs that can perform image generation based on the user prompt. The DVM replies with a bitcoin lightning invoice that is paid by the backend and a image link is provided. The program then uses the open sourced "jspaint" project to apply that AI image as the backdrop for drawing.

Pros:

- I didn't have to make a new account anywhere to get a high quality AI image

- I could pay in bitcoin

Cons:

- Publishing a DVM event, listening for a reply, and then paying the invoice, and then publishing the result seems to be slower than traditional APIs

- While abstracting nostr to the backend, it doesn't really offer any new concept that can't be done with traditional APIs

I'll need to think about this more, but thought it was worth a note.

https://m.primal.net/HauY.mp4

Dustin Dannenhauer 1y ago

The neat thing is you don't have any relationship (permission’d or otherwise) with the image DVMs. Someone could come out with a new one tomorrow and you immediately get to use that.

APIs will still need to exist, DVMs are like little workers waiting to jump on any task you throw out into the Nostr ether.

Reply to this note

Please Login to reply.

Discussion

lemon 1y ago

Very true and it is my favorite part about DVMs, honestly.

Google sign-ins, emails and passwords are a nuisance nowadays. Beyond a nuisance, a liability. Hacks, data leaks and de-platforming are a very real possibility with any new service sign-up.

The network effects of nostr and DVMs are not yet realized. While there are only like 3 DVMs that reliably do image generation, there will be more to come. Whereas to test new APIs, each service is a new sign-up, another credit card link, and new programming documentation to learn.

Still optimistic!