apparently nostr.wine and eden.nostr.land (paid relays) are both dead at the moment, so only nostr.plebchain.org is working for me. still a bit too broke to subscribe to puravida.nostr.land and nostr.inosta.cc.

Reply to this note

Please Login to reply.

Discussion

dead as in appearing to work but apparently not publishing my posts

I see that you have 2 times the wine filter relay with 2 differents npub. Any reasons?

What do you mean dead? Nostr.wine is working perfectly at the moment in all regions AND your posts are being written to the relay and visible in global.

Do you have a clustered setup?

We use regional mirror relays behind a geo load balancer.

very nice

They stream events to each other so that the databases stay local. Definitely makes maintenance a bit of a pain but I think it’s the best UX.

i'm not seeing them on nostrgram.co though. i don't know how reliable it is but i have been searching around for something to check which relays are actually publishing and it's the only one i've found.

I don’t know how clients aggregate their seen on relays data but I don’t trust any of them.

I sent you a post from #[4]​ on how to query a relay directly via web socket. This is the only true way to verify whether your event is being written to a specific relay.

it's increasingly looking like i'd have to make my own web tool to run such a check across, say, the whole list of relays from nostr.watch.

it should be possible to query a relay to see if it has a certain record, right?

Yes, you’ll have to make a [“REQ”] with the appropriate syntax and filter.

See: https://github.com/nostr-protocol/nips/blob/master/01.md

Yeah perhaps that would be useful. Nostr.info has a little web socket playground on the Relayr page as well but you’d still need to query one at a time.

nostr.band does a lot of aggregation but you’ll find their results aren’t perfect either. Accurate/precise timely aggregation is a difficult challenge.

Also nostr.wine blocks a LOT of aggregators due to their insane bandwidth consumption.

aggregating would be a bigger project, so i was just thinking client-side and if it's a bit slow, that's fine, because you're not going to be doing such a check super often anyway.

The key issue is it’s only captured at a point in time. The next time you check it could be different.

And who has been checked is also a subset of the entire network. Never full visibility.

It’s still valuable, however it’s decaying data.. the longer ago it was seen the less likely it’s still there.

Tor user?