Filter.nostr.wine or just nostr.wine?

Are you using any other accounts in this phone that have it on their lists?

Reply to this note

Please Login to reply.

Discussion

Thanks for asking! 💜 It is filter.nostr[.]wine, no other accounts using it on any device. But I see it has many instances in the connected relays, which have an npub after the trailing "/"

Hum.. it should ask since that relay is not on your lists. I will do some debugging on this.

First of all, I cannot express how humbled I am to get assistance directly from you. 2nd of all, it just hit me that I might have added it to my private haven relay's blaster list. I am not at a terminal right now, but will let you know asap. So please don't sweat it too much until then 💜 many thanks for your time!!

So, no, it is not in my own blaster, but I think I figured it out: it happens when I add sendit.nosflare[.]com (the one the explanation text) to the broadcast relays. When I remove it, it stops.

Very interesting. They maybe sending the NOTIFY command back to the client. But the client thinks the notify is from them, not from nostr.wine and because it is on your lists, it displays. Can you talk to them to not broadcast a NOTIFY back to the client?

Not sure I follow, the invoice comes from nostr.wine, not from nosflare. It tells me I need to pay 18k sats to use it and shows a link to their terms. I am happy to relay any message, but I'm not sure which one of both you are referring to by 'them' 😅

Is it? If it only happens when using nosflare it's because when you send a note their relay sends to nostr.wine and since you are not a subscriber there, nostr.wine replies with the note to pay. Then nosflare sends it back to the phone. The phone doesn't know it comes from nostr.wine. it thinks it is a message from nosflare themselves.

Assuming of course that is what's causing the issue.

Hmmm... I mean, the message I receive is very clearly from .wine...

Either way, I agree that it makes sense that .wine sends me an invoice: it's their business model to host notes and other stuff

99% sure adding sendit.nosflare.com to broadcast relay is the cause. So unless we're in a 1% edge case, I think it might make sense to mention something about this in the explanation text for broadcast relays on the relay panel. Like: "you will receive invoices from any payed relayed that the broadcast relay is broadcasting to" . Or perhaps find a broadcast relays that excludes paid relays...

In my case, the fix is easy, since I have my own broadcast relay, I can just remove it. But please, let me know if you think I may be able to help you in any way. And many thanks for your assistance. 💜

Oh, ok, on second read I think I might have misunderstood you on first read. 😅 But I probably get it now. Maybe doesn't matter, but still: let me know if there's anything else I can do to alleviate workload from you in this matter.

To be clear, I had never heard of nosflare until I saw it in the explanation text for broadcast relays, on the relay panel.