Thread

1. hermitcrab · 1790267696 · focus · HN ↗

   Author of the post here. Github finally took the offending page down approximately 10 minutes after the post appeared on the front page of HN. Total coincidence. I'm sure!

   Moral of the story. If you want even the most basic level of support from Github, you need to get on the front page of HN first.

   And it seems they are able to do things very quickly, when they want to. Bastards.

   1. ajmurmann · 1790267776 · focus · HN ↗

      It might not be a willingness issue as much as a bandwidth issue.

      1. locknitpicker · 1790267936 · focus · HN ↗

         Yes,evidently bandwidth from HN unblocks takedown requests of malicious content.

         1. ajmurmann · 1790268118 · focus · HN ↗

            Prioritization and escalation exists in most companies. I guarantee you that once an issue hits the HN front page, even engineers who might have totally different talks will get involved. (Never worked at GH or have talked to anyone there in years but this is how everything works pretty much everywhere)

            1. locknitpicker · 1790323553 · focus · HN ↗

               > Prioritization and escalation exists in most companies.

               Yes, indeed public awareness of a problem affects how an issue is reprioritized. Some companies even employ web scrapers to do sentiment analysis at each release, and visible issues do get bumped to high priority.

               It's amusing how some people in this thread try to pretend this doesn't happen, and make these bold assertions with a straight face in replies to people who were in actual meetings where issues were escalated because of this.

Unofficial Hacker News client; not affiliated with Y Combinator.