Announcing RSS Feed Sponsorships

Up until this morning the only way to promote a product or a service on this site was through ads placed with Fusion. The Fusion ad network is fantastic, but ads placed there are shown across its entire network. But now, if you have a product or service you’d like to promote directly to the fine readers of shawnblanc.net, you can sponsor the RSS Feed.

Feed sponsorships are week-long, exclusive, and very affordable. Your promotion will reach a handsome audience of tech- and design-savvy Mac nerds. This is a fantastic opportunity for freelancers, developers, designers, and anyone else with a product or service in need of exposure.

More info on pricing, reach, and schedule can all be found on the sponsorship page.

To book your sponsorship, or if you have any questions, please email me.

Announcing RSS Feed Sponsorships

(dv)

I’ve been hosting with Media Temple for three years, and this past weekend I finally upgraded from the (gs) Grid Server to a (dv) Dedicated Virtual server.

The (gs) gets a lot of flack, but in my experience it has been a good service. It’s inexpensive, easy to set up, and will keep your site ticking through moments of extreme traffic. In the three years I’ve been on the Grid my site never had a problem being Fireballed or other similar link-tos.

I have been wanting to upgrade to the (dv) for a while. For one, a (dv) is actually cheaper than my (gs) hosting because of some memory upgrades I added on to my Grid’s database. Secondly, the (dv) is just a better hosting environment than the (gs).

In spite of the fact I should have migrated I kept putting it off. Why? Because I am not a developer — working with databases, ssh commands, and nameservers makes my palms sweaty. However, as of a few months ago the traffic on this site has outgrown what the (gs) is meant for. So I had to migrate.

All in all the migration was not as difficult as I had feared, and chances are most visitors to the site never even noticed. There were only a few hiccups I encountered. The biggest was that the /etc/hosts file needed editing to work properly with wp_cron.php and the Super Cache plugin (so far as I can tell this is a very common edit that most WordPress installs have to make to work properly on a default (dv) server from Media Temple). Also I encountered an error when importing my Mint database and after troubleshooting ended up losing about 36 hours worth of incoming traffic data.

Some articles and references I used:

Now that things are settled I am so glad I upgraded and only wish I had migrated sooner. I’ve quickly learned my way around Plesk (the hosting control panel for the (dv)). I’ve always liked Media Temple’s account center dashboard for the (gs) — it’s nice and simple — but there is significantly more power and flexibility with the (dv) and Plesk than I ever had on the (gs).

And the speed. It is instantly noticeable when navigating this site. The (dv) is loading uncached pages at least 3 times as fast as the (gs) did, and in some cases it’s 14 times faster (these are unofficial benchmarks based on statistics from the WP Super Cache Plugin).

Finally, I cannot say enough good things about Media Temple’s customer support. I exchanged emails or spoke on the phone with TJ, Ryan, Jason, Paul, and Chris. They were all extremely friendly and brilliantly helpful.

If you’re looking for hosting, I recommend Media Temple. I don’t have a partnership with them, but if you set up your new service using this link I will get a small kickback.

(dv)

Over the past few weeks I have piping this site’s RSS feed over to my personal Twitter account. For years I have only ever posted links to my own site on Twitter when they were major posts which I especially thought were worthy of highlighting.

But the tipping point for me to set up automatic re-posting of links and articles to Twitter came for two reasons:

  1. I really appreciate it when cool dudes like Marco or Rands tweet links back to their own articles.

  2. More and more I have been finding interesting news and good reads via Twitter (some days, more so than what’s in my RSS reader). And even though much of the content I’m finding in Twitter is the same as what’s being delivered to my RSS reader, lately I’ve been interacting with Twitter much more than my RSS feeds.

But there were a couple drawbacks to having this site’s RSS feed systematically re-posted to my personal Twitter account.

  1. Some folks don’t care a dime about my nerdy posts, but have great concern about what I eat for lunch.

  2. Some folks are already subscribed to my RSS feed and would prefer to keep it there and nowhere else.

For those who do want to get this site’s posts in Twitter, it is not hard at all for you to follow another account. And the noise level is identical to what it would be if the posts were coming through my personal account.

So really, the only drawback I see is that I have to start over with a new account. But come on… what a pathetic and prideful excuse.

Follow shawnblanc.net on Twitter

Share This Post on Twitter

It is surprisingly simple to add a little bit of code to your website to allow for sharing of posts on Twitter.

In WordPress using the_title and the_guid functions you can build a dynamic “retweet” link for each post that works on your home page and on individual post pages.

The code I’m using here looks like this:


<a href="http://twitter.com/home?status=<?php the_title(); ?> - <?php the_guid(); ?> (via @shawnblanc)">Retweet.</a>

The advantage of using the_guid instead of the_permalink is that it’s the shortest URL your WordPress site automatically generates. And assuming you use clean, human-friendly, URLs set in your WordPress preferences, these post ID URLs will simply re-direct to your desired permalink.

For example, below are two different yet legit URLs for my review of Yojimbo. The first one is what’s generated using the_guid and the second is the actual permalink URL and is what’s generated using the_permalink.

The second link, which is the standard, permalink address to the Yojimbo article is more human friendly and makes for better search results. However, it also has 29 more characters than the first link listed. The second link is best for normal use, the first is best for Twitter.

What I like about this way of implementing a Twitter-sharing feature is that it uses plain and simple code, rather than a plugin. Plugins are great, but I like to keep their usage here to a minimum.

I have yet to see anyone really use these Twitter-sharing links yet. In the past few weeks of testing this, I’ve seen amongst my own little readership that people are much more inclined to re-tweet something already tweeted. Which leads me to my next point…

I have added the shawnblanc.net RSS feed to my Twitter using Alex King’s Twitter Tools plugin. Which means all new posts (articles and links) on shawnblanc.net are automatically tweeted. (Example.)

For months now I have been finding the most interesting news and best reads via Twitter (much more than via my RSS feeds). Even though much of the content I’m being told about in Twitter is the same content that’s being delivered to my RSS reader, I interact with Twitter much more than my RSS feeds.

And so I assume it’s more than likely that you’re doing the same. There will certainly some overlap for those of you who follow me on Twitter and get my RSS feed, and if that bugs you I am sorry. Nearly every RSS feed I am subscribe to I also follow the author on Twitter, And I have never once been bugged to see them plug their own content.

Share This Post on Twitter

How to Disable FeedBurner From Uglifying Your Clean URLs In Order to Track Clicks as a Traffic Source in Google Analytics

A few weeks ago I noticed FeedBurner was adding metadata to my permalinks. In Mint I could see that those of you coming from your feed reader (Google Reader especially) were landing on pages with extra code added to what is an otherwise clean and crafted URL:

?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A%20shawnblanc%20(Shawn%20Blanc)&utm_content=Google%20Reader

This excess metadata is added by FeedBurner when you click through their feedproxy, and is used in Google Analytics. This way, you can track your feed’s click-throughs right alongside your other statistics.

So far as I can tell, this tracking code was automatically turned on by FeedBurner for shawnblanc.net about a month ago.1 Since it’s been running for a few weeks, if I look in my Google Analytics account I can now tell that my top three traffic sources (and mediums) are:

  1. Direct (none)
  2. Google Search (organic)
  3. FeedBurner (Feed)

There are additional feed stats as well. Such as what feed reader people are using, the bounce rate and average time on your site for reader visits, and more. It’s fantastic feature if you’re into excess data and you don’t mind the URL invasion. But personally, I don’t care. I prefer the simple broad strokes: how many visits? how many subs?

And so today I finally got around to logging into FeedBurner and turning off the Feed Click Tracking option. And you can too if you want.

  • Go to: Analyze → Configure Stats
  • Uncheck: “Track Clicks as a traffic source in Google Analytics”
  • Save

  1. I’m not sure, but Google may have simply turned this on for everyone. (Or at least everyone with FeedBurner and Google Analytics on the same account for the same website.) And unfortunately for some folks it was resulting in 404s and server errors when their subscribers tried to click through the feed to read a post.
How to Disable FeedBurner From Uglifying Your Clean URLs In Order to Track Clicks as a Traffic Source in Google Analytics

A Public Service Announcement

Lately I haven’t been doing much writing (online) or reading (online). But today I opened up Fever for the first time in a few weeks and with my fresh cup of coffee spacebared through quite a few interesting things, and some very link-worthy ones.

If you too have not been reading (online) lately, I’ll be curating some worth-while stuff for you today from my reading this morning.

A Public Service Announcement

Ordinary and Uncomfortable

While I wasn’t looking a lot of random categories managed to sneak their way into the post meta. I noticed it’s taking longer and longer to peruse the list of categories, finding just the right twenty-seven that match the post. Too much!

It’s funny, because I don’t even make a big deal of categories here. The WordPress search engine does a great job of finding any and all instances of a longed-for word or topic.

Even if I did parade the list of every post’s category you’d be sure to ignore it — as even the names are redundant and ordinary. For instance, there was Software, Software Reviews, and then, just, Reviews. There was Apple, and iPhone, and Technology; even a Life and Journal category.

Looking deeper, I could see how nearly every post was mingled within in a slew of uneventful definitions; far from simple and enticing. So this morning I deleted all but ten categories and renamed the unimaginative ones.

Journal and Life got the axe as Life in Full Color emerged in their stead. (Speaking of which, this is a category I very much want to add more to. I think this site would do well to have a more personal touch and some transparent stories. Posts such as “Marketing Shoes” and “Josephine” come to mind as the type of writing I’d like to do more of in the future.)

While shoring up the categories I also took time to read through a lot of older posts. And I remembered how I try to forget that so much of what I used to write is riddled with embarrassing grammar, poor attempts at wit, and a generally dull use of the english language.

I like to assume that I’ve always written as I do now. Though I suppose from my own point of view I have — insofar as I have always written as well and honestly as I can at that moment. But now, when I read what two years ago I thought was well written, I want to edit the snot out of it. But I restrained; I want to leave my previous links and articles as-is.

Hopefully in another two years time I’ll look back at what I’m writing now and feel the same abashment I felt this afternoon.

Ordinary and Uncomfortable

By far and away my favorite thing to write is an in-depth review. And based on feedback, they are also, by far, your favorite thing to read.

Currently, there are nearly 30,000 words worth of software and hardware reviews hidden on this site. And until today there wasn’t a one-stop-spot for all the reviews I’ve written. Which is why I felt it was high-time these articles became first-class citizens by receiving a dedicated table of contents page.

A Dedicated Table of Contents Page for Reviews

Testing a New Design for Link Posts in the shawnblanc.net Feed

Link posts outnumber articles on shawnblanc.net three to one. And I’ve been considering a change for how link posts show up in the RSS feed.

Up until today, a link post could be identified in my RSS feed by its duplicate “sub-title”.

staging.shawnblanc.net RSS Feed Item

If you arrow out or click on the item’s primary title link you arrive at the post’s permalink here on shawnblanc.net. Clicking the “sub-title”, which is in the body of the post, takes you to the linked-to article.

This isn’t a new technique. And how it’s done is actually quite simple — the sub-title is hand written into the post’s body, and on shawnblanc.net link posts are coded to not display the main title.

What I like about this design for the RSS feed is that the default “ element for the article points to shawnblanc.net/example-permalink/ rather than to the linked-to article. (This is the same as how kottke.org, Subtraction, Justin Blanton, and many others do it, but is the opposite of Daring Fireball or Waxy Links.)

More and more weblogs writers are adapting link posts as part of their publishing routine. But most of them do not post dozens of links every week.

This past July, John Gruber posted 200 linked list items to Daring Fireball. Andy Baio posted 136; and Jason Kottke, 146. I, on the other hand only posted thirteen. If you add June in there too, then John, Andy, or Jason each posted more (or nearly as many) links as I have in the entire life of this weblog (367).

Which is why, in my opinion, the behavior of a link post in its RSS feed should not be defined based on the type of post it is, but rather by that post’s relationship to the website publishing it.

Authors who publish only a handful of links may want to consider a different type of link post behavior in their RSS feed, as compared to those who post half-a-dozen per day.

In my interview with John Gruber, his attitude towards his Linked List was that it’s not the individual links that are important so much as it is the whole day’s worth:

As for what I link to and what I don’t, it’s very much like Justice Stewart’s definition of obscenity: “I know it when I see it.” There’s a certain pace and rhythm to what I’m going for, a mix of the technical, the artful, the thoughtful, and the absurd. In the same way that I strive to achieve a certain voice in my prose, as a writer, I strive for a certain voice with regard to what I link to. No single item I post to the Linked List is all that important. It’s the mix, the gestalt of an entire day’s worth taken together, that matters to me.

The intense frequency of the Daring Fireball, Waxy, et al. links warrant a more direct-to-link style of RSS behavior.

I am not convinced that this is also the best feed behavior for shawnblanc.net. But based on a lazy poll I did on Twitter it seems a lot of people wish it were. The advantage to the DF-style link post behavior is primarily that it saves a click. But according to the shawnblanc.net feed and click-through stats, the majority of this site’s readers seem have no trouble clicking directly on the sub-header and going directly to the linked-to article from their feed reader if they want to.

Moreover, the primary reason I prefer this site’s current link post behavior is that it falls in line with my own feed reading habits.

The way I read online is that at some point in my day I will open up my aggregator and read through what’s new. I rarely read an article in my reader. Instead I open up the interesting stuff in Safari in the background, and then go to Safari’s open tabs and start reading.

At this point it’s common to have a dozen articles ready to read. Which is why being sent directly to someone’s linked-to article is not the best design.

Since I’m reading articles by folks I’m familiar with, the majority of the open tabs in Safari are websites I recognize. But when I come to a tab with a site I don’t recognize my first thought is usually, “What is this? How did I get here?”

Not because I’m confused, but because I don’t always remember exactly who’s link post I read and clicked through to that sent me to whatever it is I’m now staring at. Nor do I remember what it was they had to say about this link that prompted me to visit. It is very much like coming back to the middle of a conversation without being able to ask, now, where were we?

Through an email dialog, Sean Sperte gave me some wise input, saying that when someone clicks on the title link it indicates their desire to read more. Which means it is up to the author to decide what “read more” means. Does it mean, go to the link I’m talking about right now? Or does it mean, this trail is best begun on my site. On shawnblanc.net I think the latter is more appropriate.

Which Brings Us to the New RSS Format Experiment

Though I’m not too keen on moving to a DF-style format for my link posts, I am certainly wanting to move away from the duplicate “sub-title” design. My desire is to make the link-posts very easy to use and read while maintaing a clean design and logical behavior.1

In truth, I have always had these goals but they were not easily attained in WordPress. To implement this new feed and on-site post formatting required the use of custom fields. No problem if you publish from your WordPress web interface. But I don’t. I am a hard and fast MarsEdit user.

Unfortunately, MarsEdit has never had support for custom fields in WordPress. Which meant that for me to change my link-post behavior in the RSS feed I would have to publish all link posts from my WordPress Web interface. And that just isn’t going to happen. But praise the Lord, the latest builds of the 3.0 alpha, which I’m fortunate enough to help with testing for Daniel, now support custom fields in WordPress.

Which means that with this new feature in MarsEdit all I needed was a simple plugin, a few tweaks to my site’s theme and RSS code, and now a world of opportunities for RSS link post behavior have opened up.

The previous formatting for a link post in the RSS feed looked like this (as also seen in the screen shot at the beginning of this article):

  • Main Title (pointed to https://shawnblanc.net/example-permalink/)
  • Sub Title (duplicate text as Main Title, and points to the linked-to item)
  • Commentary, additional content, etc.

The new, experimental, formatting looks like this:

  • Main Title (points to https://shawnblanc.net/example-permalink/)
  • Commentary, additional content, etc.
  • Visit This Link ➚ (points to the linked-to item)

New RSS format

The design and behavior on shawnblanc.net has remained unchanged. (Though the back-end code has not.)

Since this is a new design, and the duplicate “sub-titles” were very good at allowing for quick identification of a link post, I am debating over the need for another way to quickly and easily identify a link post versus a full-length article. Sean Sperte does this by placing check marks next to his “asides” posts; Gruber places a star next to his articles. As of yet, I haven’t implemented any type of identification.

Feedback Please

As readers who interact with this feed every day, I would be delighted to hear your guys’ feedback (positive or negative) on the new format. And especially if you encounter any problems with the feed.

Subscribe to the RSS Feed here: https://shawnblanc.net/feed.

Email me here: [email protected].


  1. Some people have commented on the current feed format as being more friendly to page views. While this is true, it has nothing to do with why the feed is formatted this way. Those that have been reading this site for any length of time know that I’m not into gaudy ads, non-legit pageviews, or un-interested readers. This whole site has been built with care for the readers and for the author. Having a link-post behavior that sends readers here first is not a gimmick but rather a design decision that I think suits the personality of shawnblanc.net the best.
Testing a New Design for Link Posts in the shawnblanc.net Feed

Eighteen months ago a handful of readers had a fun time taking a 7-question survey regarding shawnblanc.net. At that time this site was eight months old, had about 1,500 feed subscribers, and I was in the middle of my software review kick.

Now this weblog is over two years old with about 4,000 feed subscribers, and all sorts of reviews, interviews, and other interesting things in the archives. Which is why today seemed like a good day to post another survey.

There are two new questions. The others are either identical to last year’s, or just slightly updated. And the last one is no longer my favorite, though you’ll still geek out over it.

Click on the topmost link or right here to take the short survey. In a few days I’ll publish the results so you can see more about the other nerds who you’re reading with.

Thanks.

— Shawn

The Second Short shawnblanc.net Survey