nevent1qvzqqqqqqypzpa5rapcrtaadfazwpwvvl0v4xlskg4df9nfcem7yevcaka2h7hhjqy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qghwaehxw309aex2mrp0yhxummnw3ezucnpdejz7qghwaehxw309aex2mrp0yh8qunfd4skctnwv46z7qpqdtkw2j4nqyc9znq9tk8elu9r93pfcpakfe8frlyqz70adx9x9xnqwmvk20
I thought they used their WoT DVM spec for something
https://github.com/nostr-protocol/data-vending-machines/pull/38
Discussion
So what can you do with the DVM that you couldn’t do with a vanilla API? What problem does it solve?
the big promise of dvms (note the word promise), is that you can swap providers very easily. This means no vendor lock-in.
As if two API services use the same schemas.
So the ideal is a signed API response + interoperability