brchsiao
> Y Combinator is fundamentally a nexus of people, like a university. It doesn't make a product. What defines it is the people. Jessica more than anyone curated and nurtured that collection of people. In that sense she literally made YC.
You seem to be assuming that pg wrote this essay to boost YC's reputation. Actually it feels like he wrote it to correct an injustice. A large one, I'd add, considering it's gone on for most of a decade.
Everyone knows it's annoying to see the rich philosophize in armchairs while the rest of the world does the lifting. Is that all that's left to say? pg seems to be claiming that (a) unions indicate breakage for startups to fix, and that (b) fixing this breakage is in fact more profitable for startups if they do it good-naturedly instead of simply taking workers' pie. Is this false?
> Of course they wouldn't, you're already speaking with them. Slack is fine for trusted networks of peers (businesses), but not much else. I won't start chatting with any my friends using it, nor would I bother to sign up somewhere to get access to a random Slack channel/community instead of using IRC, where I also coincidentally wouldn't need any of Slack's features.
No, what I meant was, people no longer think of IRC as the tool to use to talk about projects and communities. They used to. That was its primary use case. That use case is shrinking, so IRC is becoming less popular.
> How do you determine the popularity of something? How many people use it. Android is extremely popular. Do most of the folks realize they're using an Android phone? Nope.
This isn't quite true, is it? Most Android users seem to know they're using Android. I could be wrong.
No one denies IRC's continued popularity as a protocol for broadcasting text over a network. Slack itself uses it. But it's dying out as measured by the number of people who say to their colleagues e.g. "get on IRC, I have something to tell you."
Mistakes happen. Many startups have survived bad publicity on HN. Your actions have not ensured you a spot in this roster. Even generously overlooking the juvenile behavior of your cofounder and ban messages, the narrative of livecoding.tv stored in the collective brain of HN is now "fails to respond to user and petulantly refuses to apologize for seven hours."
The best thing you can do right now is to identify the responsible individual in your company, apologize specifically, and abjectly, as a company, on behalf of this individual, remove all the ban messages, delete OP's account, explain how a cron job came to enter the story, and both explain and apologize for why this took two hours to resolve after you heard about it.
(Disclaimer: I was about to sign up for livecoding.tv for similar reasons as OP just yesterday. I'm disappointed to know this might've happened to me.)
Sure, separate business policy from code, but it seems unwise to assume your users are technically ignorant when your site is about inviting programmers to stream their work.