ideas on spam/abuse

howto/gitlab.md

@@ -885,6 +885,20 @@ registered in the Rails app to pull CI jobs. [GitLab pages](https://gitlab.com/g
 simple HTTP server written in Go, made to serve GitLab Pages with
 CNAMEs and SNI using HTTP/HTTP2".
 
+### Spam control
+
+TODO: document lobby.
+
+Discuss alternatives, e.g. [this hackernews discussion about mediawiki
+moving to gitlab](https://news.ycombinator.com/item?id=24919569). Their [gitlab migration](https://www.mediawiki.org/wiki/GitLab_consultation) documentation might
+give us hints on how to improve the spam situation on our end.
+
+A few ideas on tools:
+
+ * [Tornevall blocklist](https://www.tornevall.net/about/)
+ * [Mediawiki spam control tricks](https://m.mediawiki.org/wiki/Manual:Combating_spam)
+ * [Friendly CAPTCHA](https://friendlycaptcha.com/), [considered for inclusion in GitLab](https://gitlab.com/gitlab-org/gitlab/-/issues/273480)
+
 ## Issues
 
 [File][] or [search][] for issues in the [gitlab project][search].