Ok Brightkite, this is what I need

Party time is over, so I feel it safe to write a formal, public request for some of the things I really need from Brightkite. I realize that some of the things I’m going to ask for are probably not that high a priority for Brightkite, but I thought that by making a list like this I’d always be able to point back to it should the need arise.

Oh, and I’m serious about most of these. Darn serious. Seriousness level = 10.

Favorites. It is time. Dare I say, past due? I can not even begin to count the number of times I’ve seen a post on Brightkite that I’ve wanted to save for later, acknowledge its greatness, or simply file away into a list of great Brightkite objects. Anything and everything should be favoritable. I know one of the new terms on the Webz is “likes” – and you can use that if you’d like too.

Flickr preferences like Twitter preferences. The granularity of the Twitter preferences is one of the reasons I was able to begin using Brightkite painlessly. In The way Brightkite fits I wrote:

“Brightkite will update Twitter with any of your activity on Brightkite, but again, there are layers upon layers of options.  Remember I said that you don’t have to switch away from Twitter if you use Brightkite the way I do?  Here is how I have Brightkite set up to notify Twitter.”

“Layers upon layers of options” is not an understatement. You get to choose precisely which actions on Brightkite will notify Twitter, the way your Twitter messages are crafted, and more. Somehow, I need these types of options for sharing photos on Flickr through Brightkite.

I don’t mind if every single photo I post on Brightkite goes to Flickr. For me, it is more a matter of the metadata saved with the photo on Flickr that is important. I choose my titles carefully on Flickr. If Brightkite has its way it simply saves the current location (no matter how messy) as the title. Sometimes this works, othertimes it doesn’t.

What can I say? I’m picky. But Brightkite, usually, allows me to be my picky-self. So, you’ve spoiled me. Your fault Brightkite. You’ve created this animal.

Messages on the Web site like messages on the iPhone. The way that direct messages work on the iPhone is, in my opinion, a lot nicer than the way they are styled on the Web site.

Fix Childs, PA. This really isn’t a “wish list” type of request – because something is obviously fubar for my hometown of Childs, Pennsylvania on Brightkite. Posts, check-ins, photos, etc. are showing up from all over the world. No idea how this happened but it started a while ago.

Odd request: Move these two check-ins and one post. So now we’re getting really nitty – but my friends and I went to Goal Line Sports Bars (which I’ve now created a location on Brightkite for). I’d like the check-ins and posts found here (by myself and CamouflageNoise) to be moved to this location.  I suppose, at the end of the day, I’m asking to be able to move posts and/or check-ins myself via the Web site. So if this situations arises again, I can do it myself.

Hashtag support. If someone uses a #hashtag make it clickable to a post search for that hashtag.

Automatic wall creation. Walls are awesome. No doubt about it. However, if someone does a search – say for No Reservations – I think that it’d be nice to click 1 button and have it create a wall for you with the results of that search. (This is sort of related to the #hashtag support, because for me if I’m following an event, it would be nice to be able to go from a friend’s post to having a wall created for that event with two clicks).

A desktop application. Right now I’m using Fluid and the iPhone web application for Brightkite. But the iPhone web application is, in a matter of speaking, not a good solution to this problem.  Perhaps there is a Brightkite desktop application that I am not aware of that rivals the likes of Twitterrific or TweetDeck but I do not know about it.

Forward /username URLs.  Ooops!

Viddler video. We’ll talk.

I have said it before, I like Brightkite better than Twitter. But, is the above too much to ask? Thanks Brightkite.