cc nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr šŸ˜‰

Reply to this note

Please Login to reply.

Discussion

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