4 ms·
I think that is due to bots causing performance impact and the easiest way out is mandatory login + banning/rate-limiting searches for authenticated users. I ca
by miduil 4y ago
I think that is due to bots causing performance impact and the easiest way out is mandatory login + banning/rate-limiting searches for authenticated users. I can't remember where I read about this though, overall GitLab had lots of bot/scraping performance issues in the past and the GitLab project has so many issues that it's particularity expensive to maintain.
- kevincox 4y agoThis may be a case where a CAPTCHA test may be a good alternative to logging in. That could have less tracking potential.