tag:blogger.com,1999:blog-1747328950487801053.post8462428948150570085..comments2010-04-21T06:49:49.986-07:00Michael Musehttp://www.blogger.com/profile/00870153589336899162noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-1747328950487801053.post-38451179913697277982010-04-21T06:49:49.969-07:002010-04-21T06:49:49.969-07:00Absolutely - the twitter location database would definitely be part of this. The idea was that rather than creating arbitrary ids and making everybody use them, we just create basically usernames for every venue. That way, a regular old Twitter user could see a hash like #WebsterHall and know what it is, and use that hashtag in Twitter or any other public forum without needing a thick client to search a database and pull lists of places you can 'check in' to. Plus, at the time we launched this, Twitter had made no formal announcement of plans for this. Facebook will one day have their own ID #s for their own service, and maybe even Google Buzz or some Apple or Microsoft LBS depending how ridiculous it gets. The idea here was to create a compelling enough user generated hashtag that all the bigwigs would be happy to fall in line because the convention was sound enough.Michael Musehttp://www.blogger.com/profile/00870153589336899162noreply@blogger.comtag:blogger.com,1999:blog-1747328950487801053.post-23443056700594792082010-04-20T22:18:49.914-07:002010-04-20T22:18:49.914-07:00I think using the new Twitter metadata feature instead of creating hashtags might be a more easier and efficient way of doing this. For example, you can give each venue an id (like loc_id:nyc1001) and just put it in the metadata field.­http://www.blogger.com/profile/16110824513677932840noreply@blogger.com