The first beta of WordPress 3.5 is out, and along with new and improved functionality, one feature is being removed: the blogroll. Well, technically it’s only being removed on new installations. If you have an existing WordPress site with links in the Link Manager, it’s not going away until a future release, and even then it’ll be moved into a plugin. (Lorelle writes about the history of blogrolls in WordPress and what to do if you want to keep yours.)

The move reflects changes in blogging trends, as well as the ongoing struggle between search engines and the SEO industry. In the old days, it was trendy to list sites you liked in a sidebar. Search engines took note, and then SEO practitioners started taking advantage, and so blogrolls lost their value.

One of the sessions I attended at WordCamp LA was a talk on optimizing WordPress. One of the measures I’ve been looking into is reexamining the plugins I use. (Sure, there’s no such thing as too many if you’re actually making use of them, but more code needs more resources.) I’m actually using two plugins to increase the value of my blogrolls here and at Speed Force:

  • Better Blogroll to show a small, randomized subset on the sidebar instead of the full list of links. (This keeps it from being clutter, and prevents the links from fading into the background by being the same on every page.)
  • WP Render Blogroll Links to list them all on a page.

I keep thinking, do I really need these? Well, I definitely don’t want a long blogroll in the sidebar. If all I want is a links page, I can just write one, and if I really want static short list in the sidebar, I can add them manually. It only really matters if I want to keep that random subset. Otherwise, I can pull two more plugins out of my installation.

But then, do I even need the links page at this point? My current links here mostly fall into one of three categories:

  • Well-enough known to not need the promotion.
  • No longer relevant to this site.
  • Other sites I maintain.

I might want to just drop the list entirely.

Speed Force’s links are both more extensive and more targeted to the site. It’s probably worth keeping that list around, but maybe just as a links page.

Does anyone actually look at those sidebar links anymore?

Lately I’ve been linkblogging via Twitter, and using Alex King’s Twitter Tools to build a weekly digest in WordPress. The problem is that since I’m pulling the posts from Twitter, I’m stuck with Twitter’s limitations: Short descriptions, cryptic URLs, and unreadable links.

So I wrote a plugin to process the links. When Twitter Tools builds a digest, the plugin calls out to the remote site, follows redirects, retrieves the final URL and (if possible) extracts the page title. Then it replaces the cryptic-looking link with a human-readable link, transforming this:

Check out this site: http://bit.ly/9MhKVv

into this:

Check out this site: Flash: Those Who Ride the Lightning

If it can’t retrieve a title, it uses the final hostname. If it can’t connect at all, it leaves the link unchanged.

The download is here, and that’s where I’ll put future versions:
» Plugin: Twitter Tools – Nice Links.

Future

One thing I’d like to add at some point is cleaning up the title a bit. They can get really long, even without people trying to stuff keywords and descriptions in for SEO purposes. All it takes is a page title plus a site title, like this one. That’s a much more complicated problem, though, since there isn’t any sort of standard for which part of a title is the most important. I suppose I could just clip it to the first few words.

I’d also like to clean up duplicate text. Often the link title and tweet content are going to be the same, or at least overlap, especially if it’s generated by a sharing button or extension. That should be easier to check.

As usual, the first thing I tried after installing the Internet Explorer 9 beta last week was to see how it handled all of my websites. It does just fine with everything except this one. It shifts the header image off to the right. This is particularly odd because it’s just the standard Twenty-Ten theme that’s the default for WordPress 3, customized with one of my own photos.

Oddly, it was just fine in the last IE9 preview. Even stranger, the sample 2010 page looks just fine. It’s not my customizations, though. I’ve checked on two other locally-installed WP sites.

There’s a short discussion thread at the WordPress forums, and a bug report. As of today, it’s marked as fixed, but here’s the question:

Is it worth fixing in WordPress?

I haven’t found any indication as to whether this is a bug in the IE9 beta or a deliberate change. If it’s a deliberate change, it’s an odd one, because it takes behavior that used to be the same as every other web browser out there and changes it to something different. If it’s a bug in IE, though, that’s where it should be reported and fixed, not in just one of the sites affected.

That said, I’m probably going to try the workaround on at least one of my sites the next time I get on a machine with IE9.

Weblog Tools Collection recently spotlighted a WordPress plugin to automatically tweet old posts. It seems like a good way to bring attention to a site’s archives, as long as it’s used sparingly. The frequency can be as high as once an hour, which IMO is a good way to lose all your followers, but one post every few days seems like it might be reasonable and even interesting.

I’ve already got a setup in place to show a “flashback” post on the front page, but most of the blog’s traffic seems to come from searches these days. Every once in a while I’ll happen to look at the front myself and say, “Oh, yeah, that was a good one!” and post a link on Twitter or Facebook.

This new plugin posts automatically, and picks an article at random. That’s helpful, because it can find old posts that I’ve forgotten. On the downside, because it’s random, there’s no quality control. It could just as easily pull out something completely inane that was funny for about a week five years ago as it could dredge up a forgotten gem. And there’s always the risk of promoting “Happy New Year!” in August — which is exactly what happened when I tested it on Speed Force.

You can filter out categories, but I think it might be more useful to filter on tags. Sure, it can take a while to go through the archives tagging posts that you feel are worth a second look, but it would certainly improve the signal/noise ratio with this scheme. Even better, there’s a lot more you can do once you’ve tagged your “classics.” Highlight them on archive pages, list some of them in the sidebar, build an index, etc.

Hmm, this might be an interesting project at some point.

Update (August 23): Well, I’ve disabled this for now — on both blogs — because of the lack of control. I’d rather forget to post “Hey, remember this?” than have it clutter up people’s accounts with old linkblogging digests or something similarly pointless. When I have time, I should work on that classics project, both tagging posts and hacking on the plugin.