<html><head></head><body><div dir="auto">From experience it takes a couple of seconds and it's just client JS.</div><br><br><div class="gmail_quote"><div dir="auto">Le 17 juin 2025 07:27:41 GMT+02:00, Mark Seemann <mark@ploeh.dk> a écrit :</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail"><div dir="auto">Hi<br><br>I'm currently just a lurker here, so my opinion may not count as much as those who actually contribute, but perhaps other readers have the same questions as I do.<br><br>- What does 'small' mean? Are we talking about a second of work, minutes, hours?<br>- Do clients need to install custom software to interact, or is that work done via existing protocols?<br><br>TIA<br><br>Mark Seemann<br><br>-----Original Message-----<br>From: ghc-devs <ghc-devs-bounces@haskell.org> On Behalf Of Ben Gamari<br>Sent: 16. juni 2025 23:04<br>To: GHC developers <ghc-devs@haskell.org><br>Subject: Placing GitLab behind Anubis<br><br>Hi all,<br><br>As you may know, for the last few years we have used a variety of strategies for dealing with the problem of abuse and spam on gitlab.haskell.org. The currently-employed and seemingly most effective technique has been to require manual approval of new account requests.<br><br>This has always been an uneasy compromise. Not only does this approval process add considerable friction to the contribution process, the increasing prevalence of ill-behaved web crawlers has rendered the approach less and less effective at prevent that form of abuse.<br><br>For this reason we now exploring alternative approaches. One promising strategy employed by other FOSS GitLab deployments (e.g.<br>gitlab.freedesktop.org) is the Anubis proof-of-work system. Anubis works by forcing the client to perform a small (but non-negligible) amount of work before requests are serviced. This will mean that GitLab users'<br>clients will periodically be asked to perform small amounts of work.<br>While Anubis primarily targets crawlers, it may be that the slight increase in per-request cost might also allow us to lift our manual account approval requirement.<br><br>Ultimately, the only way to find out is to try. If there are no objections, I will place Anubis in front of GitLab starting next week.<br>During this process we will assess the effectiveness of Anubis at prevent both spam and over-zealous crawlers. This may require a bit of iterative parameter tuning but I am hopeful that the end result might be a more accessible and faster GitLab instance for us all.<br><br>Let me know what you think.<br><br>Cheers,<br><br>- Ben<br><br><br>[1] <a href="https://github.com/TecharoHQ/anubis">https://github.com/TecharoHQ/anubis</a><hr>ghc-devs mailing list<br>ghc-devs@haskell.org<br><a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs">http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs</a><br></div></pre></blockquote></div></body></html>