nostr:npub13erq3cz7psnww6g03f57u9e43sftt96mq6vzplsrzs8wvhw275zslzxeey I have the same problem happening with https://coracle.social/, mentions are coming from a bunch of places.

nostr:nevent1qqsqqqxtafrva9ke2n6c5mvh0mqvnxuutyqgg6vu45300svetksxjxspz4mhxue69uhkzet8d9ejuat50phjummwv5hszrnhwden5te0dehhxtnvdakz7qg7waehxw309ahx7um5wgkhqatz9emk2mrvdaexgetj9ehx2ap0c3nawh

Reply to this note

Please Login to reply.

Discussion

nostr:npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl https://jumble.social/ fetches my notifications from my configured inbox relay, but also from wss://relay.damus.io and wss://relay.nostr.band, which I imagine are hardcoded and added to my list?

Because many people haven’t properly set up their inbox/outbox, I took the liberty of adding a few relays in some cases 🤣

Not an unreasonable approach, but you could do it maybe only for people that hadn't set it up?

We can try using only read relays to subscribe notifications. If too many people report not receiving notifications, I might roll it back. Some clients don't send events to the mentioned person's read relays, which is quite frustrating.

You can try wss://inbox.relays.land/ now 🫡

It is behaving magnificently. Thank you.

My pleasure!

Is this giving the Disrespector new material?

I've tagged the wrong person, I meant to tag nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn.