00:02 <whot> karolherbst: it's triggered via a webhook, if you grep damspam for do_not_litter you'll find the entry points

11:00 <DragoonAethis> bentiss: One of the GitLab workers is stuck again, but this time it's "ProcessCommitWorker" instances, not mailers

11:01 <DragoonAethis> They were stuck for a day and killing the process helped them go through, but I haven't seen that get stuck yet

11:05 <karolherbst> whot: ah, so I guess there is no great way to get notified of new ones otherwise?

11:47 <karolherbst> I wonder if there is a better way

12:47 <DragoonAethis> karolherbst: why webhooks don't work for your use cases?

12:48 <DragoonAethis> (Emoji reaction notifications are not coming in the audit even stream or anywhere else AFAIK)

12:48 <karolherbst> Want to know about those across the entire gitlab instance

12:48 <karolherbst> they are sometimes used for personal attacks or targeted harassment

12:49 <karolherbst> and was wondering if a bot could detect if somebody e.g. uses the clown emoji in rapid succession and ping somebody to look at it

12:49 <karolherbst> though might be good enough if that simply gets integrated into damspam or some new bot projects will have to opt-in, it's just such a hassle to roll out

12:50 <karolherbst> I mean the real bug is that gitlab just doesn't give you the tools to deal with it, but they also ignored everybody bringing it up, soo...

12:59 <pinchartl> karolherbst: how about disabling emojis ?

12:59 <pinchartl> :-)

13:00 <karolherbst> can't do that afaik

13:00 <karolherbst> and there is good use for emojis

13:00 <karolherbst> and it's not really about the emojis itself, it's more about identifying people who like to harass others more easily

13:00 <pinchartl> nothing that an emoticon won't solve

13:00 <karolherbst> like there are sometimes accounts who sign-up, put up 10 "negative" emojis and just never show up again

13:01 <pinchartl> is clown a harassing emoji ?

13:01 <karolherbst> and then we could also just delete those emojis. They aren't like a big issue in itself, and it often only annoys the targets, but it's also not great to scroll through issues and see that clown emojis are just left there

13:01 <karolherbst> "such a clown"?

13:02 <pinchartl> -_-'

13:02 <karolherbst> others use apes as racist attacks as well

13:02 <karolherbst> I've heard gnome has to deal with those target at black community members

13:02 <karolherbst> *targeted

13:03 <karolherbst> so at first it would be good to know what's going on and how widespread the issue is, because so far I only see it when I look at certain issues as a drive-by thing

13:04 <karolherbst> sometimes people get reported, but of course you always have instances where it doesn't get reported

13:04 <karolherbst> anyway, I've seen the clown one used to target specific accounts in the past

13:05 <karolherbst> like used on all the comments from the same account on the same issue

13:23 <DragoonAethis> I don't think you can add something like that "quietly"

13:23 <DragoonAethis> But you could use the API to add a webhook to all projects, then regularly add it to projects where it has been removed

13:23 <DragoonAethis> And it can have a user-friendly name attached, so that people know not to remove these from their projects

13:25 <karolherbst> mhhhhhhh

13:26 <karolherbst> yeah. well.. I don't mind doing it targeted for now, it is just a bit harder to tell how much of an issue this actually is anyway

13:29 <DragoonAethis> well, you could also do it the nasty way from the Rails console if you have access

13:29 <DragoonAethis> You could query the emoji reaction tables directly and monitor what you want, however you want it

13:33 <karolherbst> might be enough to do it hourly and just fetch whatever is new the last hour, but not sure how difficult that would be, also developing against the console sounds like pain

13:33 <karolherbst> but I don't have access anyway

13:33 <karolherbst> but also don't want this level of access anyway

23:04 <whot> karolherbst: there are REST endpoints for emojis which is what damspam uses, it just gets notified by the webhook so it doesn't sit there idling across all issues. i'm not sure if the `updated_at` of an issue changes when an emoji has been added, if so then it'd be relatively simple to check if any of the issues in the last N hours got an emoji added and then remove unwanted

23:04 <whot> emojis

23:05 <whot> and I don't think those endpoints need admin rights, just a normal auth token will do

23:07 <whot> adding a new webhook for all emojis would be trivial too once you have the code ready to actually react to it :)