Iβm still confused why my relay has anything to do with this, why donβt they use their own relay? Unless they do it based on picking a single relay from your relay list. Maybe need to mark which one is your inbox relay and they would use that instead ?
nostr:nprofile1qqsdv8emcke7k3qqaldwv956tstu40ejg663gdsaayuuujs6pknw7jspp4mhxue69uhkummn9ekx7mqprpmhxue69uhhqun9d45h2mfwwpexjmtpdshxuet5qyf8wumn8ghj7ur4wfcxcetsv9njuetnn9mexk can you please not use damus relay for the DVM caching thing? Should be fine to have 1 relay like Primals own one. Maybe one or 2 backup ones, but not relays with strict rate limiting. You guys keep sending lots of requests at the very same time to my server, and it replies at the very same time to those requests, which triggers spam protection already on Damus relay.
Discussion
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.
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.