Earlier this week over on the official Twitter blog, Biz Stone detailed how the company was moving towards adding true geolocation functionality into Twitter.

The announcement detailed how in the near future the Twitter API will allow developers to add longitude and latitude information to any tweet sent, essentially allowing your followers to exactly pin point you when ever you update. Of course Biz was keen to stress that this planned service, which offers similar functionality to Google Latitude, is strictly an opt-in extension to the existing Twitter website.

Since the announcement, the web has been a flurry with suggestions as to why this move is both good and bad. The various posts suggest a number of advantages such as finding people local to you with relevant interests, down to disadvantages such as harassment from local companies who know you are in the area and attempt to sell you things.

What are your thoughts on the annoucement, is this a service you would use, do you want people knowing your location, and what are your very own geolocation pro’s and con’s, be sure to let us know.

A word of warning, when using Twitter this month, be it on the web or via your favorite app just be careful not to give your details away. The guys over at Twitpwn have declared July to be the ‘Month of Twitter Bugs‘, but according to them they do not intend harm, they just have a desire to expose vulnerabilities with current systems in order to force them to be fixed, they also claim they will give warnings, read on to see what they said in full:

I’ve decided to declare July 2009 as “Month of Twitter Bugs” (MoTB). I’m doing so in order to raise the awareness of the Twitter API issue I recently blogged about. MoTB could have been easily converted to any other “Month of Web2.0 service bugs”, and I hope that Twitter and other Web2.0 API providers will work closely with their API consumers to develop more secure products.

Each day I will publish a new vulnerability in a 3rd party Twitter service on the twitpwn.com web site. As those vulnerabilities can be exploited to create a Twitter worm, I’m going to give the 3rd party service provider and Twitter at-least 24 hours heads-up before I publish the vulnerability.

So while it may sound harmless enough (if developers take notice of warnings) we do recomend to change your password, just in case.

A few days ago Twitter announced, via the API Wiki, that a “Sign in with Twitter” feature was now available. This sign in feature will allow users to sign into (participating) third-party sites with their Twitter login information. This release of this service can be seen as a direct response to the similar services offered by Facebook and Google. Facebook’s service “Facebook Connect” seems to be missing a trick, as where as Twitter’s solution is realtively an ‘open’ solution, Facebook Connect comes with a long list of do’s and don’t for those implementing it.