Hacker News new | past | comments | ask | show | jobs | submit login

Yes, you follow your teammates (your dev team, your account team, your CSR shift manager), plus management up the chain to the CEO, plus facilities for y our building, HR, and finally the hashtags for any project you may be a part of.

Which is completely nonsensical. Why put that burden on the user when a simple chatroom serves the exact same purpose, with better scoping? Why would I want my CEOs messages intermixed with my project related chatter? Why should I receive messages for projects that I have nothing to do with only because one of my co-workers is involved with them?

You'll probably say "then filter by hashtag". And I'll tell you: This is why many people consider twitter nothing more than a very poor re-implementation of existing chat technology. The hashtag emulates a chatroom (poorly) on top of a broadcast protocol. In fact the whole construct is so primitive and backwards than one has to wonder whether the twitter guys had ever looked at IRC, jabber or, well, anything, before they started their broken impl.

What they did successfully was to make person-centric scopes (rooms) the default. This obviously has a lot of mass appeal due to the inherent psychological effects (cf. "why babies cry"). But again, I don't see how this has a place in any productive environment.




Twitter isn't a chat system, even if people abuse it that way. If you want to continue casting the argument in terms of why Twitter is worse at group chat than IRC, I'll continue conceding that you're right about group chat and totally missing the point about Twitter. There is a difference between a status update (which people already organize their days around in big companies) and a chat message.


Twitter isn't a chat system, even if people abuse it that way.

Interesting level of abuse then. Those hash-tags seem to be mighty popular, probably only topped by "replies".

There is a difference between a status update (which people already organize their days around in big companies) and a chat message.

And what would that be? Twitter presents your "status updates" in exactly the same way that chat clients present their chat messages. Okay it's crippled as in you are not supposed to reply - but people are obviously not using it that way.

Furthermore you ignore the fact that nobody in your company has only a single, canonical status that could be summed up in 140 chars. Everybody is involved in multiple projects and teams, each of which has a different status.

There is a reason why all ticket- and project-management systems are project centric and not people centric. It's because the former makes sense and the latter doesn't.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: