Any update on this bug from the Discourse team? Would be great to know if it will be fixed, it has been reproduced here on Meta.
And does anyone know what the ‘hidden’ site setting DISCOURSE_RATE_LIMIT_SEARCH_USER does? It’s (AFAICT) not documented anywhere, but seems possibly relevant to this issue.