This is something I've wanted to do since the day it was released 2 years ago....

This is the sunset notice for api.nostr.watch

If for some dumb reason you're using it, you have one monthfrom now before it goes offline forever.

If you're interested in alternatives, please inquire.

Reply to this note

Please Login to reply.

Discussion

Congrats sir 💪

what is the replacement?

NIP-66

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

are they working like that?

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

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.

Also, will eventually release an API that aggregates NIP-66 data, but I won't be hosting it, I don't want to contribute to centralization, and it's a largely fruitless endeavour that recieves little thanks and bucketloads of complaints.

|build|operate|shitpost|

cool.

BTW the link to the banner broke on jellyfish, it was the only relay that I could test banners against 😂

oppsss, our nginx is down. ill fix it tonight. 🫡

its up again! 🫡🪼

I just used this to get a list of all relays to check them for DVM events. Planning to add this as a regular feature for DVMDash

To be clear, I don’t mean replicating Nostr.watch. I mean a tool for seeing which relays have DVM events. I’ll miss Nostr.watch though…

You can aggregate NIP-66 events from relaypag.es and relay.nostr.watch instead.

https://github.com/nostr-protocol/nips/pull/230