Twitter — Tracking Production Actions?

I don’t want to post the link to this (perhaps, it was left public unintentional?) but here is what I stumbled upon recently. This is a log of production maintenance of IT systems in Perth, Western Australia (as far as I could say):

Good idea but shouldn’t companies keep this sort of information private?

8 comments on “Twitter — Tracking Production Actions?”

1. John Piwowar on February 18, 2009 at 4:57 pm said:

   Looks like an “Enterprise 2.0″ sales opportunity! :-) It certainly reads like corporate IM conversations I’ve had in the past…the only time we resorted to using “public” messaging services was when we doing maintenance on the internal IM servers.

   Reply ↓
2. Philip Douglass on February 18, 2009 at 5:29 pm said:

   Agreed — and I believe this is the niche that Yammer, among others, is supposed to fill.

   Reply ↓
3. Wayne on February 18, 2009 at 8:06 pm said:

   A lot of people don’t realise the types of security issues even banal information like this can pose.

   We don’t use internal IM products, but all our staff use encrypted IM clients.

   Reply ↓
4. Alex Gorbachev on February 19, 2009 at 6:27 am said:

   Thanks all for the comments!

   John, your last name read in Russian means beer brewer. Very nice! :)

   Reply ↓
5. Connor on February 19, 2009 at 8:13 am said:

   All that was missing was:

   “Here is SYS password, here is public facing IP address”

   :-)

   Reply ↓
6. Amardeep Sidhu on February 19, 2009 at 10:04 am said:

   Oh…new use of twitter :P

   @Connor :D security demystified ;)

   Reply ↓
7. Aman.... on February 19, 2009 at 11:29 am said:

   Now that’s what is the real use of “tweeting” ;-).

   Reply ↓
8. John Piwowar on February 19, 2009 at 4:41 pm said:

   @Alex Yup, my great-grandparents on both sides were Polish, so not too far away. :-) I assume yeast and hops were once a part of the family business. I intend to take up the hobby someday and live up to the name. Strictly consumer-side for now, though. :-)

   Cheers,

   John P.

   Reply ↓