That's right. I'm talking about SEO spam. Basically anything that has a url where the content includes input from the user will be spammed. I'm fine with, say,

That's right. I'm talking about SEO spam. Basically anything that has a url where the content includes input from the user will be spammed. I'm fine with, say, the spammers hammering the main repo's merge requests and issue tracker. Those are things any healthy project will check regularly-- I'm even fine just pruning the spam there by hand (and historically I haven't gotten a lot there anyway). But I don't regularly look at the global view of snippets, and I don't want to regularly prune the global user list for SEO spam in the user profiles. There's no good reason most FOSS projects need those things to be publicly viewable, anyway. But AFAICT Gitlab's admin settings only have a single setting that affects all these things across the board. So if you make snippets viewable only to logged in users, then nobody can clone from the main repo without logging in. It's quite frustrating, and Gitlab shows no interest in disabling or hiding features like snippets and user profiles.