Maybe they do, I don't know. But I reply to the npubs Inbox relays (or relays in relay tag, if given) of the original request. And this has damus relay in it (among many others). So even if I get 20 requests at the same time to only my inbox relay, I will reply to 20 requests about the same time to the inbox relays of the sender. It would easily be fixed if the service uses 1-3 inbox relays that do not rate limit and is ideally in their control.
Discussion
everyone has damus in their inbox relays so thats why the dvm spams there right..
hah! i don't. i wish i could remove wine from mine too, because that isn't very expensive to get write permission for
but maybe also this is why i can never see people's messages consistently, perhaps i should add it lol
also, what irony... the nostr client for the hardware/OS ecosystem where everything is paid, has to be free... because apple users are such ninnies they don't realise that is part of the reason why their devices cost so much (not just because they are moderately high spec, that is part of it but not all) is paying for the operation of the spying machine called iCloud and their Apple login, and ensuring that maximal telemetry is extracted from every user
oh but they use e2ee lol whatever, it's not e2ee, that's a lie
Nah. The issue currently mostly is that 2 npubs send requests to all dvms at the exact same time, triggering rate limits when they reply (as they use the same ip). Primal users do not interact with dvms. The caching service does.