The inbox is currently limited to DMs but I will look into adding support for replies/notifications with WoT requirement.
Discussion
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.