Starting From The Assumption That IM At Work Is Bad...
from the wrong-assumptions dept
An article talking about a new tool for companies to monitor and block instant messaging conversations seems to start with the assumption that instant messaging at the office is bad. While it certainly can harm productivity if misused, it also can make many workers much more productive. The article notes that many employees use IM, but that few companies monitor or block IM usage and immediately complains that the industry isn't taking a "proactive response." Perhaps that's because they realize it's not a problem?Thank you for reading this Techdirt post. With so many things competing for everyone’s attention these days, we really appreciate you giving us your time. We work hard every day to put quality content out there for our community.
Techdirt is one of the few remaining truly independent media outlets. We do not have a giant corporation behind us, and we rely heavily on our community to support us, in an age when advertisers are increasingly uninterested in sponsoring small, independent sites — especially a site like ours that is unwilling to pull punches in its reporting and analysis.
While other websites have resorted to paywalls, registration requirements, and increasingly annoying/intrusive advertising, we have always kept Techdirt open and available to anyone. But in order to continue doing so, we need your support. We offer a variety of ways for our readers to support us, from direct donations to special subscriptions and cool merchandise — and every little bit helps. Thank you.
–The Techdirt Team
Reader Comments
Subscribe: RSS
View by: Time | Thread
No Subject Given
The problem is, this can be a pain, as it means we can't even upload/download from our own FTP servers, we can't SSH into our own servers, we can't provide support to our customers via VNC/RDP, and we can't use support from our suppliers who only provide IM support (even the Java IM clients don't work!) So it's actually reducing productivity by blocking these protocols.
I probably agree though, 90% of IM usage would be for personal use, not that many companies use it for support yet.
If companies are worried about people wasting time on WebMail and blogs, imagine the amount of waste that IM would create!
Plus there's the danger of IM viruses and spam.
[ link to this | view in chronology ]
Re: No Subject Given
[ link to this | view in chronology ]
Re: No Subject Given
The company I currently work for block everything outgoing except HTTP[S]
I have used Miranda IM in such environments quite successfully, with all 4 major IM services, jabber was not very stable unfortunately :( http://sourceforge.net/projects/miranda-icq/[ link to this | view in chronology ]
Re: No Subject Given
[ link to this | view in chronology ]
No Subject Given
One of the guys my buddy works with is a contractor and works offsite. They used to communicate via IM almost exclusively. Now, they have to communicate via the phone or through (ick) Lotus Notes.
[ link to this | view in chronology ]
Re: No Subject Given
[ link to this | view in chronology ]
Surprising...
I suspect the real issue is around making sure all that IM time (web surfing time, etc) is "productive" vs. personal.
[ link to this | view in chronology ]
Corporate controlled IM
[ link to this | view in chronology ]
From the POV of the security guys
There are a number of problems with "Internet IM" -- some of these do not apply to a purely internal "walled garden" private messaging system.
Basically, Instant Messaging fills the small gap between the functionality provided by phone calls and email, but the cost and risk is often seen as outweighing the negligible benefit that can come from filling this gap.
[ link to this | view in chronology ]
Re: From the POV of the security guys
Of course with *any* system for external communications there's going to be some security risks. However, assuming that all IM is bad is a solution that will backfire, just like companies who originally wanted to ban the phone realized just how stupid that plan was.
[ link to this | view in chronology ]