I’ve known our team’s business development architect, Mike, for a little over half a year now. So, I was a bit confused when I read a tweet from him saying:
When I asked Mike why he had sent me a greet tweet about our existing relationship, he had no idea what I was talking about. He was unaware of his own tweet… Oh, and Mike doesn’t have schizophrenia. We were momentarily dumbfounded as to how I could have possibly recieved a tweet from him that he did not send… or approve. Then, it came to us in noticing the little grey text beneath the tweet that simply says “Hashable.” Mike had downloaded Hashable‘s networking app due to all of their promotion efforts at SXSW.
A few days later, I received another tweet from Mike (also known as mike_zurk on Twitter). It read:
Mike and I were at SXSW hanging out on Sixth St. at the time, and I figured that @inthekisser was the handle for someone Mike had met whom he wanted me to meet at the conference…
But it wasn’t. Mike had no idea who inthekisser was. That tweet had also been sent by Hashable… through Mike’s twitter. A little spooky.
Mike then tweeted his thoughts:
Then, the director of products at Hashable, David Sebag, tweeted to me first thing in the morning:
And as I was about to take off from Austin-Bergstrom International Airport back to JFK, Hashable’s CEO Michael Yavonditte tweeted me:
I suppose I shouldn’t have been really surprised that Hashable was sending me false messages on my colleague’s behalf, pretending to be him with colloquialisms in the phrasing while introducing me to people he didn’t know. My fault.