Category Ideas

Taking Egypt personally

Although it’s quickly getting pushed out of the news cycle by the Super Bowl and its commercial trappings, plus a big digital media acquisition immediately in the wake of the weekend, the story in Egypt has captured my attention for the last two weeks or so.

Why?

It’s not really the politics. At this point, I’m far enough past my teenage years to understand with some comprehensiveness the scope of “revolutions” like this one, where one dictator is replaced with another (worst case scenario playing out, at least temporarily, at the moment) or with democracy (best case scenario) and all its factions, party politics, and pendulumatic swing of power from one sect of the upper class to another, indefinitely, until another coup brings another dictator to power.

In other words, I’ve seen this movie before.

But naturally, I’m drawn to the digital nature of this movement, to the Facebook pages serving as vital organizing tools, to the missing Google executive, to the protestors executing the time-honored urban hack of charging their mobile devices using the wiring in a streetlight’s base, to Andy Carvin’s retweet curation of reliable sources on the ground in and around Tahrir Square.

All of this appeals to me. No matter how it turns out, this period has been a coming of age for a Web-native generation in Egypt.

It’s a generation a bit like my own.

A brief history of January

With all the blogging I’ve been doing so far this month, a few of you have given me strange looks or short notes to the effect of “Hey, didn’t know you were still writing on that thing, ha ha.”

Right. Well. Don’t get too excited.

Just before I completely corrupted the data by importing more than 2,500 Delicious links as blog posts, I took a quick count, by month, of all the posts on this blog since I started it way back in February 2005 as a freshly minted graduate student in Mass Communications at San Jose State University.

And lately, January is big deal. Clearly, I have a New Year’s resolution problem.

Onward to the data, visualized as the most boring Excel bar chart in the history of boring bar charts.

Aside from the obvious fact that 2009 and 2010 were pretty dark years around this URL, a few amusing data points:

  • January has been my most prolific month, historically, and the top month for 2010 and 2009. In 2010, this was definitely a resolution issue.
  • As for the other spikes: In May 2005, the last month of my first semester in graduate school, and first semester as a blogger, I just plain wrote a lot. This was definitely a phase where I would link to someone else’s post and express my own opinion as it related to the topic at hand. Pretty basic blogging stuff. But In February 2006, I was importing Delicious links automatically, grouped together in a single post per day if I had saved anything new. Some people still do this, but I don’t really care for it. So that month’s numbers are a bit padded.
  • In June 2007, the all-time page view champion on this here website, I only published 11 posts, making it a mid-range month, ranked 36 of 73.
  • The 15 months with the fewest posts were all in 2009 and 2010.
  • Other than January 2005, which I included here with a zero because I think that’s when I wrote my first post or two on the original Blogspot blog where this all originated, there are no zeroes on this list. That’s right, even in the throes of whatever overarching busy-ness was keeping me away from regular blogging, I managed to get one in every month. That was a surprise to me.

The real trick, of course, is keeping up the pace when January’s over.

We’ll see.

Reintroducing Newstangle, or How I learned to stop worrying and love my blog

Let’s skip the usual rambling, expository introduction and get to the lists:

  1. Delicious is dying. Or it isn’t. Or it is. Depends on who you ask, I suppose.
  2. I like saving and tagging and sharing links. You may have noticed I worked for a company that made some tools to do that sort of thing.
  3. I’m having a hard time trusting any of the also-ran social bookmarking sites with my data.
  4. For a long time now, I’ve had intentions to implement some form of WordPress “Asides” on my blog, to use in conjunction with the “Press This” bookmarklet for light linkblogging.

The desired outcome:

  1. A handsome little way to display Asides on my blog. For the sake of this discussion, let’s just call all the “Asides” posts something like “Newstangle.”
  2. All of my Delicious links, minus some outdated stuff, imported to WordPress as posts with their tags intact.
  3. Some light repair and merging of tags.
  4. A page displaying all my Newstangle posts and tags in some sort of useful, browsable way.
  5. Perhaps a search box just for the Newstangle content.
  6. To send out automatic-ish tweets when I post a Newstangle link that lead to the link in question, and not my blog post about it.
  7. To point Newstangle.com at the Newstangle links over here.

So far: I’m done with steps 1, 2, 3, and 7. Halfway done with 4, really.

Not bad for an over-coffee-and-breakfast project, right?

Ingredients:

  • AsideShop for a pretty easy way to implement a version of Asides without messing around with templates. I’m a sucker for any plugin that lets me use tokens like %post_permalink% with my own markup, rather than getting too deep into PHP copy/paste missions.
  • The particular Delicious to WordPress Importer I used was an updated version of this one, and predated this other one, which even comes with a handy theme to make it more like Delicious. Your mileage will definitely vary.
  • Batch Cat to help clean up some of the damage I did importing more than 2,500 links to my default post category, which I actually use.
  • Tag Managing Thing, an oldie-but-a-goodie plugin for editing, merging, and deleting post tags.
  • And when I get around to adding some interesting tag listing ont he Newstangle category page, I might use some variation of the cool back-of-the-book index-style Archives template that came with my new Basic Maths theme.

It remains to be seen, of course, if I can stick with it, posting short links and notes on a regular basis, mixing in longer posts — perhaps about something other than this blog at some point — more frequently than I have of late.

Now then. What’s all this I hear about Flickr?

Basic Maths for Invisible Inkling

Believe it or not, I’ve redesigned this blog, yet again.

Well, sort of.

Ahem, more accurate:

Believe it or not, I purchased the Basic Maths WordPress theme by Khoi Vinh and Allan Cole.

So here’s the deal. I’m tired of redesigning this blog. For more than five years, yes, it’s been my primary — albeit periodic — sandbox to learn and practice my thin layer of front-end skills. But that process also became an excuse not to write.

“Oh, yes, I’ll definitely get back to blogging lots as soon as I finish the redesign! It’s going to be awesome!”

No. It might have been “awesome” in some theoretical corner of my mind, but what it would never be was “finished.”

So rather than fool myself yet again, as I had started to do with a modified Twenty-Ten theme that I was not nimble enough to set up as a child theme, leading to the tearing of garments and gnashing of the teeth when a recent WordPress update included updates to Twenty-Ten’s stylesheet… I have opted to drop a really small number of dollars for a wildly valuable and handsome theme.

Which I have already begun to customize, but not much. And as a child theme. Lesson learned.

For those of you too lazy to click through from Google Reader, a glance:

There are still plenty of tweaks I want to make, one at a time, over my morning coffee, for the most part, but I like where this is going.

I have a rough notion of how to use WordPress/PressThis/Asides/widgets to produce an interesting stream of the sort of short link-and-comment posts that I’ve used Delicious/Publish2/Instapaper for over the last several years, so stay tuned for a barrage of little things along those lines.

And honest, more actual writing.

With any luck, this blog post is the first in a series on some stuff I’m doing as 2011 starts, to reduce the amount of guilt I let orbit around my skull and the Internets. Actually, it’s the second post in the series, which includes the bit about shutting down ReportingOn.

So long, ReportingOn

In 2008, I was awarded a Knight News Challenge grant to build ReportingOn, a backchannel for beat reporters to share ideas, information, and sources. The goal of the project was to provide journalists of all stripes with a place to talk about content, not craft, or process, or skillset.

I taught myself enough Django — and sought out advice from friends and coworkers with little regard for their interest or priorities — to launch the first iteration of the site in October 2008. In July 2009, with fresh design and development from the team at Lion Burger, ReportingOn 2.0 launched.

And almost immediately, I stepped away from it, buried in the responsibilities of my day job, family, and other projects. To grow and evolve, and really, to race ahead of the internal and external communication tools already available to reporters, ReportingOn needed far more time, attention, and dedication than I could give it.

Yesterday, I shut down ReportingOn.

In its last state, it only cost a few bucks a month to maintain, but it has more value at this point as a story, or a lesson, or a piece of software than it has as a working site.

To head off a couple questions at the pass:

  1. No, you can’t export your questions or answers or profile data. None of you have touched the site in about a year, so I don’t think you’re that interested in exporting anything. But if you’re some sort of webpackrat that insists, I have the database, and I can certainly provide you with your content.
  2. Yes, the source code for the application is still available, and you’re more than welcome to take a stab at building something interesting with it. If you do, please feel free to let me know.

And a few recommendations for developers of software “for journalists:”

  • Reporters don’t want to talk about unpublished stories in public.
  • Unless they’re looking for sources.
  • There are some great places on the Internet to find sources.
  • When they do talk about unpublished stories among themselves, they do it in familiar, well-lit places, like e-mail or the telephone. Not in your application.
  • Actually, keep this in mind: Unless what you’re building meets a very journalism-specific need, you’re probably grinding your gears to build something “for journalists” when they just need a great communication tool, independent of any particular niche or category of users.

As for the problem ReportingOn set out to solve, it’s still out there.

Connecting the dots among far-flung newsrooms working on stories about the same issue is something that might happen internally in a large media company, or organically in the wilds of Twitter, but rarely in any structured way that makes it easy to discover new colleagues, peers, and mentors. Sure, there are e-mail lists, especially for professional associations (think: SEJ) that act as backchannels for a beat, but not enough, and not focused on content.

(Prove me wrong, kids. Prove me wrong.)

As for me, I’m working on another (even) small(er) Knight-funded side project a few minutes at a time these days. Watch for news about that one in the coming weeks.

Here’s what a “beat” page looked like. Note the PR/spam in need of a “flag as PR/spam” button.

Here’s a single question page. (Thanks Joey, Chris, etc.)

Here’s a profile page. (Thanks, Greg.)

Where we write, where we blog, where we share

Yes, this is going to be one of the posts where the person writing says something along the lines of: “Gee, I don’t really blog much anymore. You should follow me on Twitter.”

Sorry about that in advance.

At the beginning of this year, I resolved to “write more, but not here,” where “here” equalled Twitter.

Didn’t really happen.

Efforts to blog every day trailed off and failed, and in all honesty, I’ve had plenty of good excuses, given the busy-ness of buying a house, having another kid, and switching jobs, in that order.

When I started this blog, in its first incarnation, days after starting grad school, I followed a simple formula that lasted for a long time: Read blogs, link to them, react to them. I’ve done some original writing from time to time, sure, but so much of what I think of as “blogging” is about the read-link-react/debate/dispute/fisk space.

And that’s fine and good and necessary and conversational.

But I do most of that on Twitter these days.

And when it comes to sharing personal stuff (we moved! we had a kid! we bought the house!), most of that lives on Facebook, where I have more control (believe it or not) over who sees what.

Throw Foursquare and Instagram into the mix — and for legacy photo sharing from my dSLR workflow, Flickr — and I’m able to pretty selectively share what I’m doing, what it looks like, who I’m with, and how I feel about it.

So what’s this blog for?

I suppose its best remaining purpose is as a professional-looking archive of everything I’m thinking about next. More about the future, less about the present. Not engaging in the daily volleys of what passes for current future-of-news events (Wikileaks, #3 on your list is wrong/right/different, it’s a paywall/not a paywall, etc.) but writing now and then about the advances and movements in media and technology that seem to be just past the horizon.

That’s a goal, anyway. I won’t call it a resolution, but it’s a direction.

Now if I could just find some time to write…

…or maybe you should just follow me on Twitter.

Giant riot? I tuned into #sfscanner in the middle of the night…

Experimenting with Storify

For reasons that will be more obvious to some of you than others, I’ve been interested for some time now in a good tool for embedding tweets into, say, news stories. Or blog posts. Anywhere it might come in handy to use tweets to tell a story. I’ve been trying out curated.by a little bit, but it’s a little clumsy for my use case, I think. Or at least, the embeddable widgets it produces aren’t suitable.

But I just had a very easy time fiddling around with Storify. Check Nieman Lab’s own Storify experiment for a bit more detail about the startup, the launch, and the founder.

And here’s my embedded story about the weather:

Everything that comes next

Bit of an announcement to make, although if you follow me on Twitter, the first shoe of the pair dropped last night.

I’m joining Gannett Digital today, as Product Manager, Local Sites.

That means I’ll be working with more than 100 newspapers and broadcast news outlets, thousands of journalists, and helping them deliver information to a rather engaged audience of millions.

I like the sound of that.

For me, it’s a return to building and improving news sites on a large scale, but it’s also the same job I’ve always had in this business: Find, track, and develop the best ideas about the future of news, then hand them off to journalists packaged with the tools and training they need to put those ideas into action. And then keep bugging them about it until they do so.

For a variety of reasons, I left my position at Publish2 a few weeks ago. Thanks to all my friends there, plus everyone who made the job easy, especially the brilliant journalists in newsrooms across the country (and yes, around the world) who “got it” from the start, and were excited to try out everything I threw at them.

And now, onward, to everything that comes next.

Looser than average ends

Let’s just dig into the bucket of links I’ve been mailing myself from Tweetie, er, Twitter for the iPhone, and see what we can tie together here…

  • There is now a “Share on Twitter” bookmarklet for your Web browser that pairs rather nicely with the recently released “Tweet” button for your website. (An aside: There should be no such thing as a “retweet” button for your website. If the user is mashing the button to craft their own tweet about it, it’s not much of a retweet, is it? The old Tweetmeme method of making the user retweeting @tweetmeme seemed backwards to me, although I can certainly understand their motivation.)
  • Seth Lewis recently completed his Ph.D. dissertation on the Knight News Challenge. Judging by the abstract, it looks like an interesting academic take on how the News Challenge program has expanded the boundaries of “journalism” and the limits on who might be a participant in that sort of activity. (Obvious disclosure: Hey, I won a KNC grant a couple years back, so I’m extra-interested.)
  • Speaking of research, if you’ve written anything academic about online journalism in the last five years or so, you probably cited Pablo Boczkowski’s work. Lucky for you, he has a new book out, called News at Work. Read it, cite it, rock it.
  • This fascinates me: TimeFlow, a visual reporting/analysis tool for reporters. Less about visualizing conventional “data,” more about visualizing what you know about a story. Better than a pile of notepads? Surely. (via Mark Schaver)
  • USA Today’s Josh Hatch talks about that great Hurricane Katrina project they launched for the fifth anniversary of the storm, released on the Web, but designed for the iPad. I complained pretty adamantly about a recent Washington Post package that was clearly designed for the iPad, to the detriment of readability on the Web. The USA Today package, on the other hand, is the heir to the “Flash package of videos-as-chapters story” multimedia presentation. There’s no Flash, of course, in either the video players, or cool-trick-of-the-moment “Then and Now” image gallery. The USA Today package wisely doesn’t attempt to squeeze a massive text story into a mobile-friendly format. I’d like to believe that this is the beginning of a trend: The cool interactive built with just enough attention to the mobile browser. The user experience carries over across platforms without any missing pieces.
  • And, filed under a mix of fun, music, and historical information visualized as a map, the Rap Map, which maps and explains locations mentioned in the lyrics of popular hip-hop compositions. Spotted this via Kottke, who highlights the Club New York entry, which includes the Shyne/Puffy/J-Lo incident that inadvertently led to me quitting the movie/tv/commercial business. Long story.

So what’s the common thread?

When I look at these links, what jumps out at me are the layers of systemization and optimization that we layer on top of the Web of information available to us as journalists (and to consumers of news.)

Make sense of your social media workflow, impose order on your notes on a story, gather, catalog, and cross-reference otherwise independent locations…

Maybe this is one of the important parts about the shift from existing as a newspaper to a news organization: The end product is no longer, naturally, ink-on-paper. The end product is the organization of information into something useful to the audience.

But that’s obvious, right?

(A few other sources of origin, from my point of view, for the above information presented as a bulleted list: @amandabee, @chanders, @niemanlab)