Re:Gitlab.com Is Moving to 13.0
by dnsmichi on Monday May 11, 2020 @06:52AM
(#23140771)
Hi,
Developer Evangelist at GitLab here. Sorry that you had a hard time debugging the failure. I had gotten these reCaptcha questions myself recently. In the past months, there were numerous spam waves with flooding the issue tracker. You can see that with the increasingly high issue number, as their IDs have been burnt.
I agree that reCaptcha is not the best solution. We have an ongoing discussion which also includes replacing reCaptcha with hCaptcha. While I cannot make a promise, I recommend that you subscribe to the issue. Also, please add your thoughts in there too :)
Next to having captchas, there are other spam prevention ideas. One of them would be to follow a trust level model such as Discourse, but that needs more long-term planning and a fair model to let existing users becoming trusted.
Developer Evangelist at GitLab here. Sorry that you had a hard time debugging the failure. I had gotten these reCaptcha questions myself recently. In the past months, there were numerous spam waves with flooding the issue tracker. You can see that with the increasingly high issue number, as their IDs have been burnt.
I agree that reCaptcha is not the best solution. We have an ongoing discussion which also includes replacing reCaptcha with hCaptcha. While I cannot make a promise, I recommend that you subscribe to the issue. Also, please add your thoughts in there too :)
https://gitlab.com/gitlab-org/gitlab/-/issues/21998#note_325...
Next to having captchas, there are other spam prevention ideas. One of them would be to follow a trust level model such as Discourse, but that needs more long-term planning and a fair model to let existing users becoming trusted.
Please see https://gitlab.com/gitlab-org/gitlab/-/issues/14156#note_258... for more details.
Cheers, Michael