Skip to content

Comment on 3 Problems AWS Needs to Addressparent

Comments

I certainly get tweets in this vein for my app @expandrive and storage service @strongspace. Especially if something is effecting availability.

Lots of users realize that there is likely a faster response from twitter than support@whatever.com because the developer has some amount of face at stake with the dirty laundry in public.

But it's not really "in public" though, is it? I mean really, how many people would you expect to go to search.twitter.com and type in "expandrive" in the twelve or so hours that they cache that post? That's the only way anybody would know that your dirty laundry was airing, and then only if they could parse what the airer was trying to say.

If you really wanted to "expose" something in public, you'd put it up on a blog or someplace that's actually on the public facing internet. Not that it would get you any more chance of the company hearing about it, but at least other people might see it.

And, of course, if you run a company that simply doesn't respond to things on Twitter, the customer in question will hopefully learn that they can send you an email and get a fast response.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.