maybe nostr:nprofile1qqstq4j6pk2sgaupru6l7ah9nq0dueafq356jllwcy7uzlek9yx7hlspz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9mhwden5te0wfjkccte9ehx7um5wghxyctwvshsnpjku2 can help here dude.
Reputation + IP rate limiting
With ongoing DDoS of my server, ive added a backup zap-stream service and wrote some docs on how YOU could run your own zap-stream backend (the new one)
https://github.com/v0l/zap-stream-core/blob/main/docs/MANUAL.md
Discussion
Can it handle 600k requests per second? Thats the current connection rate
all from unique IPs?
Yea, 3M ips
well, nothing to joke about, but yeah I think it can work.
The idea is that u use the reputation of the client/author of the event to rate limit. No reputation, no responses.
Now, to get this reputation, you could compute it on your own or use a provider like Vertex.
If you do the latter, than the attacker could make you waste money for ranking throwaway pubkeys. That's were u use IP addresses to rate limit the pubkeys an IP could make you rank.