The call/response design and storing every single note is absolutely insane. We had to block most DVM kinds from our aggregator.
Login to reply
Replies (30)
Totally, I moved to ephemeral events for dvmcp
I’ve been saying this since the start. It makes no sense.
The promise of job chaining and result reuse never materialised
@Pip the WoT guy and @franzap what say you? Is your WoT API better with or without the DVM part?
The fact that they don't use the DVM on their own website says it all.
Instead they use a normal HTTP API at https://npub.world/api/query and server-rendered profile pages apparently.
I thought they used their WoT DVM spec for something
GitHub
Web of trust related DVMs by franzaps · Pull Request #38 · nostr-protocol/data-vending-machines
We have been working on a few different web of trust services that, as of now, are fully operational.
We are starting with this draft spec and woul...
bullshit, we use the DVM.
query: https://github.com/vertex-lab/npub.world/blob/main/src/lib/relay.js
searchDVM: 
profile:
GitHub
npub.world/src/routes/api/query/+server.js at 184127e5250c241694b245d9822532ee190c48ea · vertex-lab/npub.world
Contribute to vertex-lab/npub.world development by creating an account on GitHub.
GitHub
npub.world/src/routes/[npub]/+page.server.js at 184127e5250c241694b245d9822532ee190c48ea · vertex-lab/npub.world
Contribute to vertex-lab/npub.world development by creating an account on GitHub.
nevent1qvzqqqqqqypzpa5rapcrtaadfazwpwvvl0v4xlskg4df9nfcem7yevcaka2h7hhjqy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qghwaehxw309aex2mrp0yhxummnw3ezucnpdejz7qghwaehxw309aex2mrp0yh8qunfd4skctnwv46z7qpqdtkw2j4nqyc9znq9tk8elu9r93pfcpakfe8frlyqz70adx9x9xnqwmvk20
Perhaps time to rethink it for the agentic era ... we have MCP and A2A now, too
So what can you do with the DVM that you couldn’t do with a vanilla API? What problem does it solve?
You can talk all day, I have the screenshot, and screenshots never lie: 
That third profile has multiple 🍇-verified reports as an impersonator
Brainstorm
hats off to you, master troll
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
In this case, you’re talking about providers of personalized WoT scores, right?
yes. Like me and u
Yes, I was thinking about that thoughtfully when drafting dvmcp spec and my article about dvms and the reflection pattern.
I built it that way because speed is more important than interoperability for npub.world which obviously will never use any other DVM as it's a Vertex product.
So does npub.world uses your DVM or not? If a competitor were to offer personalized PageRank scores via DVM then npub.world would not accept them?
It uses an HTTP/JSON-based DVM.
A competitor should investigate exposing the exact same API under a different hostname and then clients could decide to implement support for both at the same time without having to write two different integrations.
That would be easy enough to do but there’s no sense building out a spec that no one is going to use and if the spec is about to be upended anyway.
To my knowledge there are 2 teams eager to offer personalized WoT scores, team vertex and team grapevine, but 0 clients ready to consume them. Why is that?
We need at least one client to step up and say: I’m ready to ingest personalized WoT scores from a third party provider. Here’s how I want to use them and here’s an outline of the spec I want to use to ingest them. We could start with personalized PageRank to keep things simple and consistent. It can be used to rank any content whatsoever by author. Basically, an alternative to ordering content chronologically. You’ll quickly have two competing providers: Vertex and Grapevine.
Are there any clients interested in this?
I'm confused, why would you do that? npub.world is a product for end users. If you want to compete with it, you can use Vertex DVMs (or any other) from client, server or wherever you want.
I am no longer involved with Vertex but afaik there are a handful of clients already using it, not zero
Ah, I didn’t realize that (either of those things).
@Vertex do you want a competitor to offer personalized PageRank via WoT DVM? The point would be to demonstrate interoperability, which I think is important.
Or is the dvm spec gonna die on the vine? I’ve only partly been listening to the dvm debate. Most of my attention has been focused on trying to optimize the sync pipeline between strfry and neo4j.
Why don't you just do it? DVMs are pretty simple to implement.
In the veins of building in the open, I'll share my recent ruminations of WoT and Reputation in SatShoot:
Feedback welcome! ( @Pip the WoT guy !)
This plan is about 50% done and it will be complete after "Freelance mode" is implemented (switch between freelance and client role in the app) along with the ability to post your Freelance Services rather than merely Clients posting Jobs.
#wot #grownostr #ux #freelance #satshoot #vertex
View quoted note →
I suppose I may as well. I mean, people do keep saying you can just do things … 😂
Once I finish the optimization I’m working on, maybe that next.
no man, clients are using Vertex.
npub.world, Zapstore, @Sovran Money, and a big one I can't mention yet
ofc not. It's my client, and its sole purpose is to showcase Vertex.