gitlab spam

[Moritz Angermann]

The second one is an issue if it consumes CI Ressource. Ideally we’d have
only “blessed” repos allowed to consume CI. The issue with this is that
(random) new users can’t fork GHC and have CI run against their change.

I’d still very much like to see a solution to this; it is a security
concern.

Moritz

On Tue, 17 May 2022 at 1:27 AM, Ben Gamari <ben at well-typed.com> wrote:

> Bryan and I discussed this in person but I'll repeat what I said there
> here:
>
> In short, there are two kinds of spam:
>
>  * user creation without the creation of any other content
>  * spam content (primarily projects and snippets)
>
> My sense is that the former has thusfar been harmless and consequently
> we shouldn't worry lose any sleep over it. On the other hand, spam
> content is quite problematic and we should strive to eliminate it.
> Once every few months I take a bit of time and do some cleaning (with
> some mechanical help [1]). It's also helpful when users use GitLab's
> "Report Abuse" feature to flag spam accounts as these cases are very
> easy to handle.
>
> Cheers,
>
> - Ben
>
>
> [1]
> https://gitlab.haskell.org/bgamari/ghc-utils/-/blob/master/gitlab-utils/gitlab_utils/spam_util.py
>
> _______________________________________________
> ghc-devs mailing list
> ghc-devs at haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20220517/3067d6d3/attachment.html>