Microblogging

Manton Reece has been working on an app/business/service that I think is really in the “own your own Twitter” space. Basically, why not own your own work, rather than just pushing it into Twitter.

It’s something I’ve thought about in the past. If I could post to Twitter and push those to my blog at the same time, it’d give me a full accounting for most of what I do on line (suck in Instagram, and you probably get the totality of it).

I’m interested to see what he comes up with. I think, often, that my Tweets only make sense in the context of the moment. A Celtics game or a concert, or whatever is happening on TV. Some are of the moment in a world sense, and make more sense standing alone.

For example,

Serial is pretty popular, so that stands up on its own alright (and, for fun, go search Bergdahl and Rand on Twitter. It’s amazing.)

This tweet, however,

only makes sense when you realize I was at the Celtics/Clippers game before the All Star break, that the Cs pulled out in overtime.

If you push your tweets/microposts to your blog, even if it’s within the context of your other tweets/posts, can you maintain that context of the moment? I’m not sure.

It’d be amazing if, whether via an app or later inside of your blogging applicaiton, you could add that context. If I could post from an app, that knows my location, and can determine I’m at the Celtics game, and add enough meta-data to that tweet to put it in the context of “Posted from the TD Garden during the Celtics victory over the Clippers”, that’d be pretty amazing.

And it’s not really out of reach today. That tweet could have had geo-data, which would put me at the Garden, during the time the game was going on. I mentioned “game”, which likely narrows the context down even further. If an app/web service could even let me go through my tweets later, tag them with context, and have that flow to my site, that would be a pretty amazingly wonderful service.

Twitter: “Set Doucheyness to full”

“As some of you may have already noticed the download link for the Tweetbot for Mac alpha no longer works. Twitter’s latest API Changes means now we have a large but finite limit on the number of user tokens we can get for Tweetbot for Mac. We’ve been working with Twitter over the last few days to try to work around this limit for the duration of the beta but have been unable to come up with solution that was acceptable to them. Because of this we’ve decided its best for us to pull the alpha.”

The recent Twitter API changes were restrictive, but there were at least rumors that Twitter was being “cool” about working with the existing developers and apps out there. You know, so Twitter’s users don’t suffer.

But this is a sign that Twitter is going full speed ahead on their doucherocket.

I get that they want to dissuade new developers from entering the space. I think it’s stupid and short-sighted and that, in the long run, Twitter is condemning themselves to a world where they’ll be a new AOL or Friendster. But I get that this is how they think they need to make money (rather than, say, making it possible to have developers build their apps in way that is complementary to Twitter’s advertising/revenue model).

This is just capricious, though. How should devs test their apps? A small group of beta testers with a required “Revoke Access” at the end?

I expect that, over the coming 12-24 months, a lot of folks Twitter usage will start to erode. Not enough for Twitter to feel it in their numbers, but it’ll be the early adopter, bleeding edge folks. The folks who get covered in the media, who set the tone for “what’s cool.” The folks who Twitter built their business on the back of.

Once a high profile user (i.e. celebrity) defects, I’m guessing it’ll be enough to get the ball rolling.

Twitter will revise these ridiculous requirements. It’s just going to take some time.

If I were Facebook, I’d be looking at building a status-type application and embracing the developer community.
(I don’t think app.net is the answer, but maybe it’ll ruffle a few feathers before imploding.)

(Via The Tapbots blog.)

Nifty Dorky Stuff of the Week

A quick update this Sunday, as I’ve just spent an hour or so dorking around with a couple of scripts/tips/techniques that crossed my radar this week.

Archiving tweets

Dr. Drang at leancrew.com pieces together an IFTTT recipe plus some python to give you a nice archive of your Tweets. If you’re a big dork, it’s worth the 20 minutes to get it all pieced together, so you can have a text file with all of your tweets. If you need some help pulling an archive of your tweets, there are some nice apps / tools / scripts to help you do that (or drop me an email).

But now I’ve got every stupid thought I put into Twitter sitting in a text file so I can go back and relive my inanity.

Quick fuzzy string-matching for file editing

Internet-dork-hero Brett Terpstra puts together a nice little ruby script to quickly let you find and edit text files (in the editor of your choice), based on a partial file name. It’ll come in handy for those folks who don’t do a good job remembering either the location or the name of that script they were working on.

Now, if someone could just help me figure out a way to get Coda 2 to let me do the Quick Search on sshfs mounted volumes, I’d be a happy nerd. (I’m guessing I need to get Spotlight to index the volumes, which I haven’t been able to do yet).

Twitter Updates for 2011-03-05