Dustin Dannenhauer on Nostr: DVMs are more infrastructure imo, I don’t see them as something users will interact ...
DVMs are more infrastructure imo, I don’t see them as something users will interact with directly (at least for most DVMs). The most used DVM right now is feed sorting algorithms, and clients make this user friendly and call the DVMs in the background (the user may not even know it’s DVMs that are doing the work).
We haven’t really had multi DVM use cases yet (although folks are working on them).
I think of DVMs as modules that could comprise agents, and the space is still so early. For example, we need libraries where you can call a DVM just like you would call an API (a python library for this is on my to do list).
Many people building agents are using lots of APIs right? DVMs would replace these API calls and offer some neat tradeoffs.
We haven’t really had multi DVM use cases yet (although folks are working on them).
I think of DVMs as modules that could comprise agents, and the space is still so early. For example, we need libraries where you can call a DVM just like you would call an API (a python library for this is on my to do list).
Many people building agents are using lots of APIs right? DVMs would replace these API calls and offer some neat tradeoffs.