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.
Discussion
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 :)