nostr:npub176p7sup477k5738qhxx0hk2n0cty2k5je5uvalzvkvwmw4tltmeqw7vgup and nostr:npub1wf4pufsucer5va8g9p0rj5dnhvfeh6d8w0g6eayaep5dhps6rsgs43dgh9 what say you? Is your WoT API better with or without the DVM part?
Discussion
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
https://github.com/nostr-protocol/data-vending-machines/pull/38
nevent1qvzqqqqqqypzpa5rapcrtaadfazwpwvvl0v4xlskg4df9nfcem7yevcaka2h7hhjqy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qghwaehxw309aex2mrp0yhxummnw3ezucnpdejz7qghwaehxw309aex2mrp0yh8qunfd4skctnwv46z7qpqdtkw2j4nqyc9znq9tk8elu9r93pfcpakfe8frlyqz70adx9x9xnqwmvk20
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
In this case, you’re talking about providers of personalized WoT scores, right?
bullshit, we use the DVM.
query: https://github.com/vertex-lab/npub.world/blob/main/src/lib/relay.js
You can talk all day, I have the screenshot, and screenshots never lie: 
That third profile has multiple 🍇-verified reports as an impersonator
hats off to you, master troll
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 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).
nostr:npub1kpt95rv4q3mcz8e4lamwtxq7men6jprf49l7asfac9lnv2gda0lqdknhmz 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.
no man, clients are using Vertex.
npub.world, Zapstore, nostr:nprofile1qqspu5lfqrpmh302622jzhh7y7ev340m690m8hvppk3svdn5edep8vspzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqgjwaehxw309ac82unsd3jhqct89ejhxqgkwaehxw309aex2mrp0yhxummnw3ezucnpdejqhv4kcu, and a big one I can't mention yet
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.
ofc not. It's my client, and its sole purpose is to showcase Vertex.