Make sure anyone can write into your inbox relays. Otherwise you won't get zaps. In this case, none of them work.
GM.
Discussion
Don't really know what to think about the relais list getting more complicated like this. It was good and simple while we just had one relay list.
I don't know what this means ..
I just add relays to a list and hope for the best 😬
I don't want just anyone to write anything to our relay. But it's easy to fix for relay operators if they do what I was asking about.
I did it for our relay, and also added an improvement to our LNURL server that makes seeing received zaps even more bulletproof, even if other people's relays don't fix it:
The goal of an inbox relay is to allow people to send you events. If you don't allow it, you are not going to get them. Notifications won't show up.
This is why inbox relays are a separate list from Home relays, where you keep your own posts and let everyone download them from.
Be that as it may, it's not necessary to even have a special inbox relay in order to receive zap receipts, and it's obvious from our LNURL server's logs that a lot of people don't request receipts to be published to inbox relays. In fact, it's almost everyone I saw so far.
Also, since inbox relays can easily be spammed or DDoS'ed, I won't set one up until I have proper mitigations for that. Maybe you could point me to learning resources about this?
is it ok with just 1 inbox relay?
i'm using inbox.nostr.wine
I didn't get any replies at all using inbox.nostr.wine as most clients don't support NIP-65 yet (not DM relay lists).
Had to add in filter.nostr.wine fory DMs to work properly.
cool I have that already so no probs with that here yet ty
I would add it to the general relays section. I that way no one sends DMs to filter.nostr.wine. The general section also queries for your DMs in those other relays.
