oh, nice. can we implement nip-66 monitors as a part of our nostr server stack at nostr:npub1htdamfg82u4nj7zjqj82wnew7wke9vd2cp7r6nsaast5arxujc4qtu92zz?

are they working like that?

> our server stack contains any daemon or server side code used in nostr.

Reply to this note

Please Login to reply.

Discussion

Yeah, its totally possible. I've refrained from doing it myself because I like the separation of concerns.

...my agents are separate processes and they publish to relays.

nice. everything that a monitor should implement is defined on nip-66?

Yes. Let me know if you have any questions.

nice. soon we will add this in our stack. 🫡

also, i can see your are using svelte on nostr watch. can you help me on some small bugs?

im trying to get a list of notes from a relay and show them on a component using nostr-tools. but it doesn't work in any ways.

i can share the code as well.

Sure.

here is the code:

https://github.com/dezh-tech/mangostr/pull/12/files

in src/lib/components/latestnotes.svelte im trying to fetch some events. im not sure if this is the correct/recomeneded way. but it doesn't work...

Forget to commit that component?

Ah, wrong branch

yes, i didn't merged it yet. nip-11 works well. after fetching events ill merge it.

Submitted PR.

thanks a lot. merged. which relay address you used for test? i tried some public relays, they are not work well. even their nip-11 is not complete.

I used my personal relay, many relays ignore empty filters.

hmm. let me try more relays.

And yes, many problems with NIP-11s, it's one of many reasons why I wrote @nostrwatch/schemata; not on npm yet, need to fix NPM publishing in my CI.

nice, waiting for it.