It wasn't clear to me at first, but now I think we should reframe DVMs as bots, instead of as a standard for RPC communication via Nostr events.
"Bots" are often seen as useless, playful things, but if we call them "DVMs" it's clearer they can also be useful tools. Ultimately it doesn't matter, it's all marketing.
Finally, we can also reframe HTTP/JSON APIs as yet another type of DVM. Zap providers, for example, are an HTTP/Event-hybrid DVM. Mazin (nprofile…7rj8) 's translator API is another type of HTTP/JSON DVM that follows an existing standard (which is to copy some other translation provider I forgot) and is implemented in some clients (Damus?). Primal, Nostr.Band and Nostr.Wine also offer trending feeds HTTP/JSON-based DVMs, but they're all incompatible among each other (meanwhile Snort and Iris use the Nostr.Band API while Primal and Yakihonne use the Primal API, I don't know who uses the Nostr.Wine API), we should try to get them to standardize these (or offer these feeds as custom relays, which would be better).
That would solve our problems instead of creating more.
fiatjaf /
npub180…jh6w6
2025-05-02 15:10:54
in reply to nevent1q…kfak
Author Public Key
npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6Published at
2025-05-02 15:10:54Event JSON
{
"id": "bbac49af6d33a2261c5a4a0b1977a15dae3e54ecf547ba1c0cb37777e51e436d",
"pubkey": "3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d",
"created_at": 1746198654,
"kind": 1,
"tags": [
[
"p",
"3d842afecd5e293f28b6627933704a3fb8ce153aa91d790ab11f6a752d44a42d",
"wss://nostr.wine/"
],
[
"p",
"40b9c85fffeafc1cadf8c30a4e5c88660ff6e4971a0dc723d5ab674b5e61b451",
"",
"Gzuuus"
],
[
"p",
"d8881295f6442dc93481f888ddb5e74aeaaddac9457e2fb7bd09e68f4d5c8db7",
"",
"Vincent"
],
[
"p",
"da18e9860040f3bf493876fc16b1a912ae5a6f6fa8d5159c3de2b8233a0d9851",
"wss://purplepag.es/",
"Dustin"
],
[
"p",
"155b5f0000ea709dcf7b9e924d5289c28c9b4166b0439ad583fc60bce7a96bad",
"",
"ots_nbot"
],
[
"e",
"0fee3586d63f82e69103e3c58565b5aebe39d42bda94b55bb03295cbaad1496a",
"wss://inbox.relays.land/",
"root"
],
[
"e",
"2f964a79bf2b6eb38eeebaa41d7e6f10ba112908495dcc16c94624925017b6a8",
"wss://relay.primal.net",
"mention"
],
[
"e",
"34672f23685862a5e34c6df2247671452d4727027ac8928346e20c891bfdb2f6",
"",
"mention"
],
[
"e",
"f0392b5ccd2a9139a924678b2ded957956e9e5ac7c9812d4f08e3d4a7d376ec3",
"",
"reply",
"40b9c85fffeafc1cadf8c30a4e5c88660ff6e4971a0dc723d5ab674b5e61b451"
]
],
"content": "It wasn't clear to me at first, but now I think we should reframe DVMs as bots, instead of as a standard for RPC communication via Nostr events.\n\n\"Bots\" are often seen as useless, playful things, but if we call them \"DVMs\" it's clearer they can also be useful tools. Ultimately it doesn't matter, it's all marketing.\n\nFinally, we can also reframe HTTP/JSON APIs as yet another type of DVM. Zap providers, for example, are an HTTP/Event-hybrid DVM. nostr:nprofile1qyghwumn8ghj7mn0wd68ytnhd9hx2tcpzamhxue69uhkjmnzdauzumn0wd68ytnhd9hx2tcprpmhxue69uhkxun9v968ytnwdaehgu3wwa5kuef0qyv8wumn8ghj7cm9d3kxzu3wdehhxarj9emkjmn99uq3samnwvaz7tmxd9k8getj9ehx7um5wgh8w6twv5hsqgpass40an279ylj3dnz0yehqj3lhr8p2w4fr4us4vgldf6j639y955x7rj8 's translator API is another type of HTTP/JSON DVM that follows an existing standard (which is to copy some other translation provider I forgot) and is implemented in some clients (Damus?). Primal, Nostr.Band and Nostr.Wine also offer trending feeds HTTP/JSON-based DVMs, but they're all incompatible among each other (meanwhile Snort and Iris use the Nostr.Band API while Primal and Yakihonne use the Primal API, I don't know who uses the Nostr.Wine API), we should try to get them to standardize these (or offer these feeds as custom relays, which would be better).\n\nThat would solve our problems instead of creating more.",
"sig": "ccb4eac9c55bf2fc2c317deb312051ee5725b1262dedfdd38c14c6a94ea2cb7f609d996abbcdaeeb0c772b1ae12ad268d99b2eb230631b3c0ee5ae29e0bc4051"
}