There are differences but not sure why they should impact this.
Even if filter is unable to accept zap event for some reason (if WoS stripped everything after filter.nostr.wine/ for example), at least one (?) of your other relays should get it.
We whitelisted the WoS pubkey on nostr.wine/filter but that shouldnβt be relevant to this problem.
Iβll try to see what the requests look like but Iβm not convinced this is us. Maybe a job for tomorrow.
Granted, it may not be a relay issue as other relays should receive it. (As you say, even if you delete the public key part etc.)
Thank you for reviewing our request.
WoS raises a similar issue.
Not being able to generate an invoice is very odd. I donβt think that part should have anything to do with our relay. Iβll do some more testing though.
#[0]
It is what is being raised in the tree below.
I can't Zap from Snort and Amethyst (maybe there are others) for those who have WoS address set in their profile.
Some people are able to Zap by deleting some relays, but I think the problem is not on the relay side but on the WoS side.
@#[1]
thank you for responding
Mentioned on Nostr to bring others into the conversation. Please join the conversation π€
#[3]
It seems that an error will occur if the following relay is included in the parameters when calling back to `livingroomofsatoshi.com`. These relays are only verified relays that I follow.
```
"wss://filter.nostr.wine/{NPUB_KEY}",
"wss://relay.nostrgraph.net",
"wss://nostr.plebchain.org",
"wss://relay.nostr.wirednet.jp",
"wss://nostr.guru",
"wss://relay.snort.social",
"wss://relay.nostr.or.jp",
"wss://nostr.lnprivate.network",
"wss://nostr-relay.nokotaro.com",
"wss://nostr.walletofsatoshi.com",
"wss://nostr.milou.lol",
"wss://test.relay.nostrich.day"
```
