I signed up for a Twitter account three days ago as I thought it would be a good alternative to putting back a shoutbox on my blog.
It was neat, simple and one of the hottest things to hit the web today. Well, over at North America and Europe probably because I’ve yet to see a Pinoy blogger or Asian blogger to use Twitter. Anyways, it was delightful to know that Twitter can be used with most IM clients like Jabber, AIM, and yes GTalk. Strange enough, Yahoo! Messenger is not yet supported, in the future perhaps?
Anyways, I set up my Twitter to work with my GTalk account and unfortunately, I can’t get it to work. I followed every single step listed in the Settings>Phone & IM page, added firstname.lastname@example.org to my friends’ list in GTalk yet nothing happened. A new friend called Twitter is suppose to appear but it doesn’t. I opened my GAIM client, signed up for a new Jabber account, started the process all over again but to no avail. So what’s wrong? I have no freakin’ idea.
I’m not alone
Googling around for a possible fix, this problem is not an isolated case as Blog on Travel commented on Digital Inspiration’ little walk through on how to Use Google Talk with Twitter. He said:
Unfortunately Twittering through Gtalk is so slow! It has not worked yet for me. I tried it several times and got nothing sent yet! The contact keeps on going offline when I send messages.. and responds in about 4 minutes to a simple “help” command.. They will need to invest money in servers… or maybe yahoo will buy this service like they did with MyBlogLog.
Lucky for him, GTalk is just slow to send his messages to Twitter. I on the other hand have not yet even verified my IM account with Twitter. Talked to Jaypee this morning about this little problem of mine over at GTalk, he signed up for his own Twitter account and tried to get his IM working with Twitter too. Like what happened to me, he ran into the same problems.
Get better servers
So what’s wrong with Twitter? I guess Blog on Travel is right, the folks over at Twitter needs to get their hands on better servers or even sell it to Yahoo! so that it can be integrated with Yahoo! Messenger as well. I gave up on fixing this myself as the problem is clearly on Twitter’s side. So after publishing this post, I’ll go write the Twitter guys an e-mail for help.
If you do have a fix for this, please tell me about it in the comments thread below, I’ll greatly appreciate it.