I forgot to say that k. (nprofile…wvxz) is right in the sense that HTTP services could also be considered DVMs.
It's hard for me to imagine that the feed-generator DVMs wouldn't be better as HTTP services rather than Nostr event publishers, or the Vertex DVM (which, by the way, is not listed in the official DVM specs, do not follow them strictly and is being used as an HTTP service even by their own website https://npub.world/ ).
In that sense every zap provider is a DVM: you call it via HTTP and it emits a kind:9735 event.
But today apparently people feel they're not being nostric enough if they do not turn what could have been an HTTP service into a service that listens on a bunch of relays for events and responds with events. I think a new NIP with clearer recommendations would address that, by which I mean we should tell people that sometimes it's better to do an HTTP service, and we can even standardize those HTTP services if they call for it (again, like NIP-57 did).
fiatjaf /
npub180…jh6w6
2025-05-02 10:57:25
in reply to nevent1q…wwnz
Author Public Key
npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6Published at
2025-05-02 10:57:25Event JSON
{
"id": "de2b152277803196c40619475267a96a11308beb846643083828f5743c4c36df",
"pubkey": "3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d",
"created_at": 1746183445,
"kind": 1,
"tags": [
[
"p",
"bd4ae3e67e29964d494172261dc45395c89f6bd2e774642e366127171dfb81f5",
""
],
[
"p",
"da18e9860040f3bf493876fc16b1a912ae5a6f6fa8d5159c3de2b8233a0d9851",
"wss://relay.damus.io/",
"Dustin"
],
[
"p",
"155b5f0000ea709dcf7b9e924d5289c28c9b4166b0439ad583fc60bce7a96bad",
"",
"ots_nbot"
],
[
"e",
"639a62d47ad1687c7908da4e5c3b65d86bf59bfbebb8f5bec3d350ed85e74fac",
"wss://inbox.relays.land/",
"root"
],
[
"e",
"cbe03e39ddd2cb14fdfff638cb6bb7c2231f51953415dc22dd165e2cb907c9dd",
"wss://relay.westernbtc.com/",
"mention"
],
[
"e",
"608ac5c394eadb178fcc46eb674c411a420257368c2295d5e68789291800fdae",
"wss://lockbox.fiatjaf.com/",
"reply",
"3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d"
]
],
"content": "I forgot to say that nostr:nprofile1qqst6jhruelzn9jdf9qhyfsac3fetjyld0fwwary9cmxzfchrhacragtgwvxz is right in the sense that HTTP services could also be considered DVMs.\n\nIt's hard for me to imagine that the feed-generator DVMs wouldn't be better as HTTP services rather than Nostr event publishers, or the Vertex DVM (which, by the way, is not listed in the official DVM specs, do not follow them strictly and is being used as an HTTP service even by their own website https://npub.world/ ).\n\nIn that sense every zap provider is a DVM: you call it via HTTP and it emits a kind:9735 event.\n\nBut today apparently people feel they're not being nostric enough if they do not turn what could have been an HTTP service into a service that listens on a bunch of relays for events and responds with events. I think a new NIP with clearer recommendations would address that, by which I mean we should tell people that sometimes it's better to do an HTTP service, and we can even standardize those HTTP services if they call for it (again, like NIP-57 did).",
"sig": "f6ba7da9544abebc4f1f697af8a333326fecfcdf5231c5f8b536ecf77fad47919482ee1946341fcc3aeb3ebf3ef6477aa9e8b4b8d2a4a0289280251f75045d07"
}