π npub.world vs Primal showdown.
Who has the best search?
Thread
Login to reply
Replies (65)
why i can't find myself. am i an impersonator? π
Same here, I can't find myself on npub.world. Tried searching by nickname and by npub π€·ββοΈ
Same π
Would you like to earn some #bitcoin? Send me a DM
search terms should have more than 3 letters, since we are using a trigram tokenizer. We should problably tell this in the UI @franzap .


most likely it's because we haven't been able to find your profile event. It is rare but can happen. Try changing it, we should detect the new event immediately.
what about i want to search for CIA?
yours is a popular name π
. Maybe we should add more rows in the results.
you get profiles that contain "cia" 

cool, thank you. π«‘
πππ
how to see my follower count in your graph?
that's coming soon
C IT o_0 n_n/
@npub1a2hc...dvza @npub13aa8...z3fg @npub1qqqq...ln03
we need to think about wot indexing in future and add weight to data. what do you think?
cool
Great job @Pip the WoT guy π€
@Vitor Pamplona when build-in-search of @npub142gy...xrj0 powered by @npub1kpt9...nhmz ? π
great work β
Would you like to earn some #bitcoin? Send me a DM
this is awesome; what's the dvm kind for pubkey search? going to put this in olas
the docs says source is defaulted to the pubkey sending the event, as it should, but when I omit it I get
"SearchProfiles: invalid search: the search parameter should not be empty for SearchProfiles"
the source parameter can be omitted, not the search parameter.
Here is a working nak command:
nak event --kind 5315 --tag param="search;jack" wss://relay.vertexlab.io
lol, jesus, nvmd, just actually read the response
that's it, I need to take a 15 minute break, brb π
no worries π
ah dude, we have a daily limit of 30 free DVM requests per day. We should probably have a chat on how to extend that for olas users. cc @franzap
you guys might want to consider ignoring unknown tags, like a "client" tag ;)
ah damn π
I am working on it. In the next refactor we'll parse only tags that follow the scheme:
"param", <key>, <value>
Where <key> is one of our parameters.
Very nice! Are you guys crawling all of nostr yourselves or is there an index/firehose for rent somewhere for this type of thing?
we are doing all ourselves.
and thank you :)
i wrote a firehose for nostr some time back for my fiat mining gig:
it just uses go-nostr's pool query framework to blast out requests in parallel
GitHub
hoover/pkg/nostr/firehose.go at master Β· Hubmakerlabs/hoover
Data aggregator for Nostr, Bluesky and Farcaster to Arweave AO - Hubmakerlabs/hoover
yeah I know, our Firehose is inspired by yours. Not the same because we want to aggressively filter spammers, and we use internal metrics for that.
was just sharing it for the benefit of who asked how you are drinking firehoses :)
i also wrote a spider that searches the db for relays to spam with queries and then it was running hourly to scan for updates to users directory events so follow lists were kept up to date (as they control access to the realy) but i have disabled that spider now, it's languishing on a sidebranch of https://realy.lol
Good going. I can think of a few clients if they integrated this I'd be happy to pay a few sats per search, because those clients do most other things well. Not sure how payment might work. If you've tried Keychat, the way they have an integrated cashu wallet that just pays 1 sat to the relay for each message you send is quite niceβwonder how to achieve a UX like that in an integrated search DEV context.
this is a very interesting question. @franzap and I were so busy building that we haven't though out the payment aspect yet π
Yeah lots to unpack. It would be nice if integrations like could handle their own payment, maybe drawing from the users NIP-60 wallet with an approval popup. That way clients wouldn't have to collect and then pay the integration provider later as if they were collecting VAT.
yeah true. But on the other side, asking the user for approval and making him pay can be taking away from the experience. Maybe clients can pre-pay for new users, or all users, and monetizing somewhere else if they wish so.
This is great!
Now compare against #Coracle.
Primal's search is garbage for searching for profiles, but excels for advanced search.
Coracle already has web-of-trust built into the search results for profiles, though, so I have generally been using it for that purpose for a while.
I think coracle performs search client side, right @ hodlbod ?
So comparing it in speed and "breath" would be unfair.
WoT is calculated client side, but additional results are loaded from some search relays. I am planning to integrate vertex though, at least as an additional backend
Nice work @Pip the WoT guy !
Thanks for pointing out things we can improve. π«‘
Looks like youβve built a useful service; congrats! Gotta love Nostr.
View quoted note β
Awesome! Nostr search using the page rank algorithm (powering Google search). Comes with a DVM so it can be integrated into everything else.
Incredibly useful. Fantastic work! Can't be overstated.
I love Primal search because it lets me search my own notes .. hope npub.pub has advance search ?
content is not coming anywhere soon. We'll remain focused on profiles for the forseable future
π€« 

Very thoughtful. Is DVM a must?
we can provide the same service in other ways, but a DVM is very straightforward to integrate and it has the benefits of being a native nostr event
I see. Thanks! The only thing left is the costπ€
This shit is amazing!
Nostrpunks dev community is so underappreciated!
Zaping them is highly recommend (even symbolic zaps only)!
View quoted note β
Good job!
Question: Are you providing any kind of proofs client apps can easily check to be more certain that Vertex is not lying?
Or even better: with the request one could add some params as to how or what kind of proofs should be provided by such dvms, depending on use-case.
I might sound vague but you get the point I hope.
yes this is something we definitely want to explore in the future.
One idea, specific for recommend follows, is to provide some kind3s (or their IDs), so the user can verify client side if and how he's connected to all the recommended npubs. We are talking about 2N +1 kind3s as the worst case where N is the number of recommendations.
@AβΏdel fgu starks to the rescue?
Could be an option.
We started some experiments to see how starks could be useful for Nostr.
Right now we are focused on delegate signature aggregation verification.

GitHub
GitHub - starkware-bitcoin/starkstr: Nostr x STARKs exploration project.
Nostr x STARKs exploration project. Contribute to starkware-bitcoin/starkstr development by creating an account on GitHub.
That's a cool use case!
Susan is a prominent investor in the cryptocurrency space, known for her insightful strategies and deep understanding of the rapidly evolving digital asset market. With a strong focus on Bitcoin and other major cryptocurrencies, she navigates the complexities of blockchain technology, market cycles, and regulatory landscapes to make informed trading decisions. Susan approach combines technical analysis with a keen eye on macroeconomic trends, allowing her to identify long-term opportunities while managing risk in the volatile crypto market. Her trading style emphasizes patience and adaptability, helping her capitalize on both bullish trends and market corrections. Investors following her moves are often drawn to her disciplined yet forward-thinking approach to crypto trading... Inbox π
Susan on WhatsApp: +13184079133
For more guide ππ―
This is a smart idea and could really save a lot of storage space & bandwidth for relays. Weβd be happy to implement it in @npub1h0rn...fv0g when itβs ready. π
Try the relay dashboard demo here!
H.O.R.N.E.T Storage
All-In-One Nostr Relay with Dashboard Panelπ Host Files as Scionic Merkle Trees or Blossom BlobsπΈπ³
You keep going .. itβs impressive !
I still have problem to handle some uses of starknet but itβs fault π
Muchos gracias. Gr8 work