Nostr Web Client

query: https://github.com/vertex-lab/npub.world/blob/main/src/lib/relay.js

bullshit, we use the DVM.

searchDVM: https://github.com/vertex-lab/npub.world/blob/184127e5250c241694b245d9822532ee190c48ea/src/routes/api/query/%2Bserver.js#L31

profile: https://github.com/vertex-lab/npub.world/blob/184127e5250c241694b245d9822532ee190c48ea/src/routes/%5Bnpub%5D/%2Bpage.server.js#L31

Reply to this note

Please Login to reply.

Discussion

fiatjaf 8mo ago

You can talk all day, I have the screenshot, and screenshots never lie:

https://straycat.brainstorm.social/profile.html?pubkey=990694581c58124489d0b08dfa4d2a7523a713b16a829a0bc161ad82bffdc915

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?

fiatjaf 8mo ago

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?

nostr:nevent1qqsgt9hxvc95n8j5fcc3pgg9peday23amzq0wuwyk276ahu4rffk96gpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtczyrgyanen5vp6txzjlkmgrmvtgy3qrw59mrfpnxhvw09ky6qav24fqqcyqqqqqqgugs66h

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?

Five 8mo ago

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.

Why don't you just do it? DVMs are pretty simple to implement.

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, 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.