DVMs are largely a solution to a problem that we created by not having topical relays. 😅
Discussion
Accurate 😂😂😂
The topical relay model is a different workflow:
1. You decided to write about a topic.
2. You client determines that the topic is "sourdough bread baking".
3. Your client writes the event to the "bread baking" relay and adds "sourdough" as a tag.
4. Everyone in the sourdough community forum immediately sees your event. Nobody else sees your event. The moderator (human or AI) can immediately moderate the event, as they know what a sourdough forum event should look like and they oversee the content on that relay.
5. You open your "notifications/chat/kind01" client and can see the responses from the sourdough forum in it.
6. You can respond there, only to them, but you can also allow your wider fren group to see the discussion, by broadcasting it to more relays.
The thing with relays, is that you could also write that "sourdough bread baking" event from Nostrudel or Primal, so long as you had the relay listed and could somehow indicate that it was the one you wanted to write to.
How is a relay determining it? I think I'll just leave this to the devs lol cos I won't understand the answer maybe lolol.
But let's say I make a post about a particular plugin or vst for music production. But I haven't mentioned the words 'music production' or whatever other words, but I want it on that relay. How would a client determine this, it couldn't possibly have all the possible words and brand names associated with a topic. And what about let's say I was also mentioning it was for the audio of a film. Would it then determine to post instead to a film relay? Or post to both?
I have no idea. Lol, I assume there are ways:) lol
Well, we could have relay selection boxes, when you post, so that you could determine it, manually. If you were responding to a music production thread, that would also be a hint, so we could just write the response back on the relay that it came from. It should be possible to post to n number of topical relays, so that the post ends up everywhere, that it might be useful, same way we do with general posts.
The basic difference is that the person publishing the post curates where it will go and how it will be defined/labeled/tagged. They then send it off to the appropriate relay. Then, everyone reading from that relay (because they are interested in the same topic or are part of the same community) can see it and respond to it.
The people who want to read it have it _sent to them_ over the relay. Or they go to a client where there's nothing but Stuff Like That.
They don't have to go dig it out of the gigantic heap of Bitcoin memes and EXTRA LARGE TEXT RESPONDING TO EXTRA LARGE TEXT.
Relay selection can be handled client side. This requires smart clients and smart relays working together, I think. Relay auth can be used to help protect relays from non-topical posts.
Also DVMs seem like an overly-complex way to reinvent REST APIs lol.
ROFLMAO
Like, why are we doing this complex Nostr interaction to get feed data? Just use an API, bro.
We have over 100k “feedback” events from DVMs on our aggregator that just say something along the lines of “I’m processing your task”
Absurd waste.
I'm not really sure, why it has to have an event. Seems more like a service a client would just offer, outright, as a feature. Not everything needs to generate an event or be a NIP.
The idea is to standardize everything so that nobody has to implement a bunch of proprietary APIs. I certainly get the appeal of that but the design is wasteful and slow.
Lots of the services “offered” by DVMs are just wrapping centralized services with more latency. For example, most search DVMs just use NIP-50 on one or more of the 3 search relay implementations. Using this instead of connecting directly to the relay(s) is so much more work.
With NIP-50:
1. Connect to search relay
2. Open search filter
3. Relay finds matching events and returns them
3. Display returned events
With DVMs:
1. Make a DVM request event
2. DVM makes NIP-50/search API request
3: DVM parses just the event IDs and returns a list of those in a nostr event
4. Client pulls response event and requests event IDs from all relays? Some relays? Only the NIP-50 relay(s) that supplied the DVM with the results?
5. Relay(s) finds matching events and return them
6. Client displays events
🤯
What happened to my numbering…
After 3 comes 4 - you get the idea 😂
Just saw that nostr:npub1fq8vrf63vsrqjrwqgtwlvauqauc0yme6se8g8dqhcpf6tfs3equqntmzut has got an elasticsearch version on github. 👀
https://github.com/layer-systems/search
nostr:npub1ecdlntvjzexlyfale2egzvvncc8tgqsaxkl5hw7xlgjv2cxs705s9qs735 nostr:npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzuskcqsyn nostr:npub1qdjn8j4gwgmkj3k5un775nq6q3q7mguv5tvajstmkdsqdja2havq03fqm7
I'm going to need to study up more on ElasticSearch
Well I start to like elasticsearch. But I'm still a noob at it :D
Interesting. That is one heck of a stack
Haha I hacked this together. Don't know if it event works right now 😂
Can you check, and fix it, if it doesn't?
#askingforafriend
It works! (More or less) Maybe some stuff is not build perfectly fine but it works :)
DVM's go waaaay beyond Topical feeds tho.
Probably one of their worst use cases tbh.
Yes, it's too broad. I could see it adding real value as a sort of "personal search worker" for finding something more unusual than "dev stuff" or "Catholic stuff" or "stuff about biking".
They're more like "categorized computation workers" that you pay cash for.
Any computation, not just filtering kind 1's, that's just one of the categories of things they do.