Hacker News Reader

It's 'unfortunate' because it reflects poorly on your company. The developer didn't do anything wrong.

The rest of your explanation is just specious, as pointed out by other people, and also reflects poorly on your company.

View on HN

It's nice to see somebody from Twitter actually posting here on HN and all. But when the reply is, as you say, somewhat specious, it doesn't really do anything to enhance Twitter's credibility. And they are kinda "swimming upstream" in this regard already.

It's just poorly done damage control. I would expect someone in charge of developer relations at Twitter to come up with an actually concrete plan, if they actually cared about the developer community, and not just talk about how "flexible" Twitter is in private or how "disappointing" it is to get this private matter get exposed. The rest of us developers need to see things like this to properly decide technology product direction, and at least for me, it speaks for how much I will continue to push for removing reliance on Twitter as a platform in favor of something more open, transparent, and predictable.

Reply on news.ycombinator.com