@graf The actual solution is an MRF. But I do not have the time to implement it. Pleroma already has a built-in rate limiter on the registrations endpoint, so an nginx patch should not be needed. The built-in rate limiter is enabled by default, but could be misconfigured depending on the setup. In other words, we're already doing all the things we're supposed to be doing by default, but this is still happening to some servers. I'm not sure the nginx approach is the right solution. It's a bandaid. Configuring the built-in rate limiter will fix it, and a new MRF could stop duplication spam.