Notifications broken?

Some dipshit script bombing the site earlier. Had to purge the queue.

Bot spammed over 13k comments.
😔

#notMyBot

@SortOfTested @C0D4 Oh what? When was this? I was kinda inactive yesterday

@ScriptCoded
Had to be within the last 8 hours, as I only saw this after waking up this morning.

@ScriptCoded
Like 30 minutes ago. The fun bus pulled up, it was crazy. Even the fat kid in the babylon 5 t-shirt got laid. Or something.

#10PointsIfYouGetTheRef.😋

Got the same, had over 99+ yesterday from that bot, made it all but impossible to find the real interesting ones :/

And today, still lists 99+ but it was empty except that I found two under the comment tab in notifications.

Think the api will need some time limit unfortunately.

it seems so.

@dfox

@SortOfTested Oh damn. (didn't get the reference, but managed to Google it :p, worth a watch?)

@Voxera I know there was some talk the other day about bots not being allowed in the first place. Hopefully that won't become a full stop...

@ScriptCoded hopefully not.

Buts can be useful but they need restraint.

And API’s need to be a bit restrictive, at least for new users.

Like a ramp up period to prove your not ddosing by mistake ;)

@Voxera > Butts can be useful but they need restraint

I know that @rutee07 would have something to say about that

📍

Seems like notifications are slowly draining. I haven't used the [Clear] button and now I'm down to 80 out of 99+. Notifications slowly appear in the list and I'm able to click on them one-by-one. They appear at the rate of 1-2 per hour or so.

It feels like MQ (or any other component in that branch) might be short on memory.

Is this the offender?

7.2k already.

Looks like dR can be easily ddos'ed :)

@netikras yup.

@-assmaster (because search never frikkin works)