a work on process

I really liked this story about the NPRbackstory twitter account. The panel at SxSW about newspaper APIs (which NPR was tagged onto) was one of the highlights, filled with promise, and it’s good to hear about a tangible (albeit experimental) use of one of those APIs to begin to contextualise breaking news.

All too often we lack the memory or the back-knowledge to appropriately interpret the stories that dominate the news (I was a little surprised and disappointed that the BBC stories about Khamnei’s comments on Britain didn’t note that “blame the British” is a common off-hand comment in Iran). News organisations often have vast resources that could help us develop some of that back-knowledge but they’re under-utilised. It’s rarely helpfully presented by web-based news outlets, but for a radio station it’s particularly hard to get that out. Twitter provides a nice way of passing on some tidbits and it’s great that NPR are using it for more than driving traffic to their very latest content.

Recommend this post:

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

 

Obsession Times Voice

14 June 2009 (1:20 pm)

By James Stewart
Filed under: Notes
Tagged: , , , , , , , , ,

I didn’t write much (outside of twitter) about SxSW 2009. In part that was because life rushed off in other directions immediately afterwards, and in part there wasn’t much that really inspired me to write. There were numerous good sessions at the conference, but far too many “social media consultants” talking without real experience and far too much focus on “monetising.” Many of us with a longer view of the web and/or more of a technical bent expressed considerable frustration with such sessions and the voting process that had allowed them to dominate the programme.

One session I wish I had made it to was Merlin Mann and John Gruber’s. For months now I’ve had Gruber’s subsequent write-up open in my newsreader awaiting a link from this blog. In it he deftly sums up what so many of the panels seemed to miss, that the starting point for a successful blogging (and, I’d say, most any) venture has to be passion (obsession), and a next step has to be craft. The rest may follow, but it needs those starting points:

What’s so great, so amazing, about this racket is that it doesn’t have to be that way. You can obsess over your work, build an audience based on deep mutual respect, and eventually opportunities to earn money from it will present themselves. I don’t know how it works, I only know that it does.

Recommend this post:

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

 

I’m working on a wordpress project at the moment, and pushing that blogging engine quite a bit further than I have before. We’re going to be using categories very extensively and one of the first tasks has been to allow category paths without any preceding /category/ or the like. By default, wordpress wants the category with a slug of ‘case-studies’ to live at:

/category/case-studies

but we want it to be simply:

/case-studies

So far, so straightforward. I installed the pathless-category-links plugin and all was well. Until I started using subcategories. All subcategory links started returning 404s. It seems I’m far from alone in that problem, but I’ve not yet seen a solution offered, so a little digging was required.

What was happening with subcategories (at least in my setup) was that the wordpress method that parses the query string was identifying the top-level category name as the category name and the subcategory name as the ‘name’ (ie. the post slug to look for). What was needed was a check to see whether that ‘name’ maps to a category slug and if so, correct wordpress’ assumption.

The code I’m using is:

if (! function_exists('jys_pathless_category_links_query_string')) {
  function jys_pathless_category_links_query_string($qs) {
    parse_str($qs, $query_vars);
    if (isset($query_vars['name']) && get_category_by_slug($query_vars['name'])) {
      $res = array('category_name' => $query_vars['category_name'] . "/" . $query_vars['name']);
      return http_build_query($res);
    }
    return $qs;
  }
}
 
add_filter('query_string', 'jys_pathless_category_links_query_string');

(NB: This will break if you have permalinks set up as recommended by the plugin author (’/%category%/%postname%’) and a post in your top-level category with the same slug as your subcategory. But hopefully that’s rare enough that we’ll be okay!)

Recommend this post:

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

 

The past two weeks haven’t really left time to compile my selected links, though there have been many. A few days at SxSWi (on which more, later) followed by travelling with the family and the inevitable work backlog moved blogging way down the priority list. So here’s a mammoth selection to get me caught up. Particularly interesting has been the discussion around the future of newspapers (represented here by Clay Shirky, Steven Johnson and Russell Davies), which seem to have finally pushed beyond “how t ind a good business model for papers” to looking at where the real value for society lies and how we can preserve and extend that in a changing landscape.

Recommend this post:

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

 

Somewhere between Ruby on Rails versions 2.3.0 (RC1) and 2.3.2 (final) a change was made to the arguments required for one of the methods the theme_support plugin requires. I must confess I hadn’t spotted it, but github user knapo kindly sent me a message with a patch. That patch is now applied in the main repository, as are a few tweaks to the ActionMailer integration to better handle multipart emails. You can get the new version from github.

Perhaps more significant than those small patches is that I’ve now pushed up a new rails app for use in testing theme_support. The tests are a series of cucumber stories, and the app is very barebones designed entirely to test the various features. I could do with tightening up the way the test app and the main plugin repository are connected, but it’s a start and has been very helpful with the aforementioned patches. Any improvements to the test suite would be much appreciated. You can, of course, find it on github.

Recommend this post:

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

 
Next Page »