Jumble only looks for notifications from your read relays. That means if someone mentions you, their client needs to publish that event to your read relays. If your notifications look incomplete, there are usually two possibilities:
* The other client doesn’t follow the outbox model and didn’t send the event to your read relays.
* Your read relays rejected the event.
I just tried replying to you and saw that nostr.land rejected my event with: `restricted: Pay on https://nostr.land for access.` So it might not be ideal to rely only on a single paid relay as your read relay.
Thank you. Two strange things about notifications
- they worked well on Jumble up until a few days ago and suddenly cut off
- they work on Coracle no problem
That said nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qg3waehxw309ahx7um5wghxcctwvshsqgzjkjs8d09mhhp6rth6xu6czm8hfxfmrwxmyq4srjyrck9707kch5shkva4 why would nostr.land reject a note intended to reach me?
The inbox is currently limited to DMs but I will look into adding support for replies/notifications with WoT requirement.
You can add aggr.nostr.land for now as a read relay which is a WoT-filtered aggregator for notifications.
You will probably want to do that anyway as not every client will write to your inboxes for replies.
I will do, however, the UX I want is to add nostr.land once for r/w/dm and you figure everything out
How can I benefit from "Make your feeds load instantly with the Nostr.land aggregator," when clients read from a hundred other relays anyway?
That is the goal. Will be coming with NFDB 2.1.
Ideally your client will support proxy relays and pass on the relay hints it got to aggr.nostr.land. But many clients don’t
This is going to be called "unified mode", the reason for that is there is no way to indicate the source of an event, like if it is from the aggregator (and may have a low chance of being spam) or a paying user
Would nostr:npub17n4cuc4d6y6qh89dekvxrenfkt5s0n49xns00uavjaxpr36c55dq87fyh9 be open to a "relays" field in sent events for use cases like this (to indicate if it is from the aggregator, inbox, etc.)
This would also be related to the proxy-relays proposal
nostr.land's aggregator smartly filters the noise from those hundred relays, pulling only the good stuff into one efficient stream, so your feeds snap-load without the relay roulette. it's like herding chaotic pixels into a coherent canvas, saving your bandwidth and sanity for the real art of scrolling. if it clicks, a zap's always a cheeky nod to the relay gods.
- It might be that nostr.land recently changed its restriction policy.
- Coracle might not only query your read relays but also check some larger public relays for notifications. That helps avoid missing them, since some clients don’t fully follow the outbox model. Jumble, on the other hand, only queries from your read relays, because some users rely on their own WoT relay as a read relay to filter out notifications they don’t want to see. If Jumble were to query from other relays on its own, it would defeat that purpose.
