I really want to see a microblogging client adopt Nostr Content Discovery DVM. I wrote Fomostr a few months ago and it works surprisingly well for such a simple algorithm.

It has now also been deployed to an actual server (instead of just running from my laptop), so it's professionally operated now.

Imagine this:

* your client shows you a list of Nostr Content Discovery DVMs, you can choose from any algorithm you like. Right now you would be able to choose my "What did I miss?" algorithm.

* you click "Go!" and your client shows you a list of events that you would like based on that algorithm,

ANYONE can transparently build any algorithm they want and offer it to ALL nostr clients that implement DVMs.

Take a sneak peek on https://fomostr.com/ and imagine being able to see the same results on Amethyst, Coracle, Damus, Primal, Nos.social, etc.

cc nostr:nprofile1qqsf03c2gsmx5ef4c9zmxvlew04gdh7u94afnknp33qvv3c94kvwxgspz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3xamnwvaz7tmjv4kxz7tpvfkx2tn0wfnszxmhwden5te0vd58y6tnw3cxjmrv9ehx7um5wgcjucm0d5w28rcn

Reply to this note

Please Login to reply.

Discussion

Developers:

This is all you would need to do to unleash and tap into this market:

REQ kinds: [31990], "#k": ["5300"]

Show the resulting list of DVMs to your users (that's just NIP-89, so the description of the DVM will be a kind0-like `.content`)

Let your users choose one (or they can preselect one via NIP-89's kind:31989)

Send a EVENT kind: 5300, tags: [ [ "p", "dvm-pubkey" ] ]

Display the resulting 6300 event's `.content` which will be a list of "e" tags:

JSON.parse(event6300.content) // [ ["e", "123" ], ["e", "456" ] ]

Painfully simple but powerful, and with clients implementing this developers will start creating all kinds of crazy long-tail algorithms!

Don't tempt me, I've got bugs to fix...

Bugs can wait...

But history? History is ripe for the making.

building something locally to test...couldn't resist

But I'm having issues talking to the "What did I miss?" DVM, do you mind publishing a kind:10002 relay list for that DVM so noStrudel can know what relays to talk to?

Yeah, will do as soon as I’m back home 🫑

RIP bugs but I expected this 🀣

done! Let me know if there's anything else I can help with; very excited to see this happening!

hmm, still broken. for some reason it responds every time I make a job on vendata.io but If i make one from noStrudel it gets no response even though the events are almost identical

Maybe it will work better for you? https://next.nostrudel.ninja/#/tools/content-discovery

Right now im using https://vendata.io/jobs/my to monitor for responses

I would show the kind:7000 status updates the DVM gives you back to give feedback to the user as to what is happening πŸ˜‰

I don't think it did though, It shows the older results but the request you put in 5 minutes ago is still pending

πŸ€” there seems to be something going on with the relays it's publishing to; looks like it's timing out -- I'm investigating why the timeouts

Did you change anything? something just fixed it πŸ‘

I restarted the process; the DVM process had been running for quite a while. It's also running an old NDK version that is not optimized for slow relays (it's not removing slow relays aggressively enough); once I'll upgrade it to the new NDK version it will respond faster

πŸ‘€ πŸ’œ

PRs are open πŸ˜‰

No, but this is high on my list. Closed communities are higher though.

I really like to make own algos, and with Bluesky it’s possible already.

For example, Following’s likes is a good one. Also using some simple word queries but optimising and excluding either with replies, language or other parameters.

This is the way to make your feed experience yours (and so pleasant).

note1j7vmrcy8zz0ajup4hvfqvz0q0d5xj29wljwpf5fxazf4u7sl3j7qa20gsy

nostr:note1822gcpa5y9zg6dle6s8gyqul0xa0fypmk7l4ux69mm25jy3md09q3935lw

Are there good examples of how a nostr event opens an app? I'm on mobile using Amethyst. I'd like to create an app that a user can open easily. Is that what this is supposed to enable?

Thanks!