Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
I've posted on this before but when they went live with the RSS log I made some good money mining those activity logs for "File and Fire" goods. That is the crap your employer archives about you and when they need an excuse to fire you; they dig it out and show you to the door.
It was easy to correlate Killing Boss X to if those telecommuters were playing WoW when they should have been working. We'd get excuses "that wasn't me that was someone using my account.... " and in some cases Blizzard ended up getting involved. Mental Note: When you VPN into work we can see what IP address you are coming from. The connection log Blizzard keeps also indicates which IP address you are on... as well as the MAC address as part of the data link layer. So telling me it was someone else playing doesn't explain the fact it was the same IP and MAC address and pulling your IM log shows periodic and errante WASD typoes in your IM pop ups. Oh and the fact you accidentally responded to a popup from HR with '/random 100' and 'L2P N00b' were kind of dead giveaways. I had 6 months of WoW paid for by a client so I could monitor a list of character names on specific servers to track play times.
I would not be suprised if this is actually a direct reponse by ActiBliz to expedite those types of situations so they don't want to deal with the hassle of the suits.