Hacker News new | ask | show | jobs
by eyelidlessness 1087 days ago
They asked with more than passable benefit of the doubt what the user intended. And they asked quite a ways after the user noticed local degradation. “Surprised” might be the wrong term, but it definitely doesn’t seem like a specific guard was in place for the scenario.
1 comments

Was there a guard needed? I don't think so. It seems GitHub didn't saw any degraded performance and barely noticed the issue, and odds are they presumed the author screwed up with their GitHub actions configuration. Once they determined it was plain old abuse, I'd guess some GitHub employee said "what a moron" and proceeded with his day.
What are you basing this on?
> What are you basing this on?

To start off, based on the fact that GitHub is around for over a decade and this was the first time this sort of attention-seeking stunt was made public.

Do you have any indication this sort of stunt is relevant?