Tag: Twitter

Posted on
by

An experiment: I’ve modified* Twitter Tools to create digest posts as drafts instead of publishing immediately. That gives me a chance to edit a week’s worth of random thoughts and links down to the interesting stuff, clean things up a bit, expand things that could use more detail, and remind myself of items that I wanted to write more about later.

If it works out, and if the plugin still offers digests after it’s rewritten to use OAuth, I’ll probably use this same setup to make sure I keep on top of linkblogging at Speed Force.

*It was pretty simple. I just looked for the function that creates digests, then changed the post_status from publish to draft.

The Links

  • Why information storage is hard: The Universe Hates Your Data.
  • Interesting analogy: Facebook, Twitter, and the iPhone aren’t quite ecosystems. Maybe it’s better to think of web services as governments. (via ma.tt)
  • WTF of the week: A book I was looking at on Amazon didn’t have any active discussions related to it, so Amazon showed me some random forum threads. They included this question on used textbooks: “Is it Ok if I used it to bludgeon several people to death with it?” Be sure to read the responses. [Edit: Amazon’s forums have been shut down.]
  • I love how Twitter’s status blog describes Wednesday morning’s outage as “high whales.”
  • Dear CNN: A 4.0 earthquake in California, especially one that didn’t cause any damage, is not breaking news. It’s more like business as usual. (It’s worth noting that a full day later, they haven’t updated the story with anything substantive…probably because there isn’t anything to add!)
  • Very cool: the Sci-Fi Airshow is a gallery of photorealistic images of spaceships from various science-fiction TV shows and movies set at, well, an air show. (via Bad Astronomy and SciFi Wire)

Posted on
by

Twitter writes that link length shouldn’t matter, but the zillions of URL shortening services out there show that, for now, it does.

But why?

There are two main reasons to shorten* a link:

  • There’s a technical limit, such as SMS message length or email line width.
  • You expect people to manually enter the URL.

Right now, with Twitter messages limited to 140 characters and links forced to share that space with the rest of the post, URL shorteners are critical. But they’re working on a plan to accept longer URLs, and specifically shorten them for SMS messages. The full link will be available on the Twitter website, desktop clients, and other platforms that don’t have that hard and fast limit.

That will cut down on the demand for shorteners, but they’ll still be useful.

For one thing, there are other microblogging platforms out there like StatusNet.

For another, there’s email.

IIRC, the first URL shorteners launched because email programs often break up really long lines, including really long URLs. In plain-text messages, that leaves links not just unclickable, but inconvenient even to copy and paste, because you have to copy each line separately and paste them together. This will continue to be an issue as long as people continue to put visible URLs in email.

And then there’s the human factor. It might not be easy to remember http://is.gd/cGE8V, but it certainly takes a lot less time to write it on a scrap of paper than http://blogs.discovermagazine.com/badastronomy/2010/06/07/hard-to-port-eject-goose-eject/.

Which of those URLs would you rather type on your keyboard? Or worse, on your mobile phone?

*In this case, I mean making it really short and cryptic. There are plenty of reasons to keep links readable and sort of short.

Posted on
by

I’ve deleted redundant or trivial items, split some digests by topic, tagged, categorized and titled the rest, fixed typos and expanded abbreviations, reformatted quotes, links and lists, imported photos, and more…all in an attempt to make the archive a little more useful.

After trying to unify some of the more eclectic mixes of unrelated one-line remarks and links, I’ve decided it’s time to stop automatically importing “tweets” to the blog. Sure, the digests maintain quantity, but I think it’ll be better to keep the quality up instead. What makes a good status update doesn’t always make a good blog entry, and I’d frequently find myself either staying up late to edit that day’s “Line Items” post or rewriting it the following day. (Plus I was always worried about a bug in Twitter Tools that would cause a duplicate post about 30-50% of the time.)

I think the blog will be better off if I copy, expand or skip stuff from Twitter at my own pace and put it in a more suitable format to begin with.

Posted on
by

The major problem I see with the new retweet feature in beta on Twitter is that (for now) the posts are invisible to API clients. Since I do most of my Twitter activity through Twidroid (on my phone) and Twhirl (on the desktop), that means if someone I follow retweets a post using the new feature on the website, I won’t see it.

Update (Nov. 20): That was fast! Twidroid has released a new version that supports the native retweet capability, so now I can see them on my phone. It also lets you choose whether to retweet the classic way (open a post pre-filled with the original, so that you can edit it) or natively. If you use the native version and have multiple accounts, Twidroid Pro is smart enough to use the one that’s following the original poster. I haven’t quite figured out how it decides which account to use when retweeting someone you don’t follow, though.