I see OP edited their post claiming getting to HN's front helped.
I think the likelihood GitHub did something within 10 minutes of a post appearing on HN's front page is approximately zero.
Nobody in GitHub Trust & Safety is sat there watching HN.
An executive or communications professional who might have heard it got on HN, or seen it appear in a tool monitoring Microsoft and GitHub's mentions across the internet, and who then flagged the post, Trust & Safety would probably spend *more than 10 minutes* noticing the email or Teams message, then trying to find the right ticket internally. Then after locating the ticket you still have to investigate the facts, discuss, and click buttons to ban/delete the user.
It's (much) more likely this sat in a queue until someone got to it and the timing of it being on HN is a complete coincidence.
I think you wildly underestimate how much more empowered the people monitoring social media escalations are versus the standard front-line support. In a clear-cut case like this I can absolutely imagine someone getting pinged and pressing the 'kill bad thing' button immediately after the post hitting the front page, because I've seen this happen many times.
It’s not a coincidence if they had already found the problem, wrote up the solution, primed it for action, and then it sat in some “management queue” for essentially forever, until someone called someone with a go.
Where I work we're hosting our own gitlab instance and the previous company I worked for hosted their own Bitbucket. For most developers I know it's either a self hosted git platform instance or Github enterprise.
> A regular cinema ticket is $22.83 to the nearest movie theater and that isnt a "premium" thing like IMAX
For about that price you can get a monthly subscription to a lot of local cinemas and unlimited viewings here. In my city all three cinemas are in this system so we just go see a movie whenever we want. Doesn't include IMAX ones and chains of course.
Rest in peace, Picard.
reply