This is a linkdump

At the risk of doing what I’m best at — overstating the obvious — you might have noticed that I don’t use this blog much anymore.

Actually, I do use it, maybe once a year or so, to communicate the fact that I don’t write many blog posts these days, and you should just follow me on Twitter or somewhere else if you’re interested.

But that’s barely true. I don’t “talk” about “media” stuff much on Twitter, although I sort of do, depending on how you feel about reading between the lines, but sometimes a GIF is just a GIF.

That’s the end of the preamble.

This is a linkdump.

I’ve been using Pinboard (again) for a couple months now to “save” links to “read” later. (Is there an Emoji for air quotes? Wait, I’m going to tweet that, brb.)

The air quotes are because I haven’t really used these tools for anything other than reducing the amount of guilt I have over not reading the entire Internet.

Really, who reads everything they save to “read later?” Nobody. It just sits there, festering. I used to share first, read later, but in modern times, it often feels silly to re-share something everyone has already shared, so I’ll just “like” or “favorite” and let that be a passive form of sharing, rather than crafting a shiny new headline and point of view around some interesting article, where “interesting” equals “this caught my eye and it seems important.”

So, instead, I present this unscheduled, imperiodic link dump of a bunch of stuff I’ve saved. Maybe I’ve read it, maybe not. Maybe it’s useful, maybe not.

You be the judge. An ordered list in no particular order follows, although it might end up in chronological order, we’ll see.

  1. Matt Waite for Source on the hey-wasn’t-this-hotly-debated ethics of a mugshot news app.
  2. 10 years of NFL play-by-play data, in CSV form.
  3. A List Apart article on small-screen (iPhone, for example) navigation patterns.
  4. Software to help humans figure out if that pic was ‘shopped, marketed to insurance companies.
  5. “Don’t learn how to code; learn to make things.”
  6. A painfully basic lesson for product managers and entrepreneurs: Solve Existing Problems
  7. If you’re going to have meetings, Always Be Capturing, so you don’t have to have more meetings to review what you decided in the previous meeting.
  8. On the perils of including edge case legacy functionality in your application to satisfy power users: Checkboxes That Kill Your Product
  9. Hey guys, remember when Netflix was a useful social network?
  10. Solid notes on *how* to measure audience engagement in news apps, although I would argue that *what* to measure is critical.
  11. For the completely uninitiated, a perfect explanation of the (current) state of open graph tags and making content shareable.
  12. Lorem Ipsum for avatars.
  13. The accidental limerick detector.
  14. The year-old Zeldman-approved recommended replacement for the ol’ -9999px trick.
  15. “Could you make a list of cute animals that gets 5 million views?”

 

 

11 websites that should never, ever have a Facebook open graph read action that tells my friends what I am looking at on the Internet

  1. Gawker
  2. Deadspin
  3. Most other Gawker sites, really.
  4. Reddit
  5. TMZ
  6. Amazon
  7. Any website mentioning the name “Hunter Moore”
  8. Every alternative weekly ever.
  9. Yahoo News Slideshows
  10. YouTube
  11. Anything still hosted at a blogspot.com domain

 

Link: How to Use the “Network Density” Formula to Measure the Health of a Community

I’m a sucker for engagement formulas, especially when they help provide a means to quantitatively track something that sounds as fluffy and qualitative as “the health of a community.”

Great ideas here for community managers and related parties: How to Use the “Network Density” Formula to Measure the Health of a Community

 

FAQ on how the New York Times handles comments

New York Times Public Editor Margaregt Sullivan on their workflow and editorial collaboration on the question of comments: Questions and Answers on How The Times Handles Online Comments From Readers

Current obsessions

In no particular order…

  • Men In Blazers, a soccer podcast by Brits of some vintage, in New York City, mostly, for ESPN’s Grantland. Funny.
  • Roadrunner, by Jonathan Richman and the Modern Lovers.
  • Hay Day, an iPhone farm game. Or as we call it in my household (all members of the household, cats excluded) “the farm game” or even just “the farm.”
  • Trying to get sort of OK at, well, Rubik’s Cube.
  • Reddit.
  • Alt Latino, from NPR, because, seriously, where else are you going to hear interesting new (and old) Latin music?

A good quick read on Product Management

Some of the basics of product management, from A List Apart, for both of you wondering what I’ve been doing for the last couple years: Product Management for the Web.

Not everything applies, and there are a lot of assumptions in this about Agile and the size of the organization involved, but it’s a good overview.

Why Italy?

On Sunday, after bearing the brunt of an excited explanation of Italy’s glorious victory over England via penalties, including a stunning Panenka from Pirlo, my own wife turned around and asked me why I was rooting for the Azzurri.

This was weird, because it’s her fault.

(Hey, this is a blog post about soccer. If you’re not interested, feel free to stop reading here.)

2012 Civic Media Conference takeaways, open questions, reactions, notes

It’s been three years since I last made the trek to Cambridge for what we once called KNCMIT, and although the cast of characters has changed (with little-to-no representation of 2007-8-9 Knight News Challenge winners, different faces at the MIT Media Lab, and a rebooted Knight Foundation posse) the outcome was similar.

All unhappy airport terminals are alike, so the sense of deja vu carries over from the hotel to the cab to the fluorescent carpeted discomfort of Logan, and the foreboding sense of dread that comes with a United flight. (Prove me wrong, airline. Prove me wrong.)

On to the obligatory, but hopefully not exclusively duplicative and obvious notes:

  • Homicide Watch is excellent, and repeatable. Whether or not you use the code powering the DC site, the model of reporting on every homicide in a city — and not just reporting it, but reporting on it, while maintaining pages for every victim and suspect — this is something that doesn’t depend exclusively on technology, although the platform is perfectly tailored to the job. But it does depend on being obsessed with telling the stories that we often hide behind numbers, or a map. (Previously.) Also, it helps to be as driven and passionate about it as Laura, and to care about people.
  • Sometimes, there’s just no story in the data. Jonathan Stray hoisted this banner of editorial force, and Daniel X. O’Neill waved it high, the sort of basic news value that journalism school drills into us if we listen: Check the facts, check the data, then double-check it and account for the fragile chain of human actions that produced the data. Because a spreadsheet packed with invalid data and intervening variables is not a story. It’s a mess, and a risk, and it might be the start of the reporting process, not the end of it. (Session video here, worth watching.)
  • The contraction of the Knight News Challenge grant cycle into themed 90-day periods is a right and good thing, as is the new prototype fund. You should apply to one or both, right now. This minute.

Not pictured in this list: An improved opinion of the food and beverage options in Cambridge, Mass.

A future history of crowdsourced reporting

During the second or third or so year of my still-brief career in what we might as well call “the news business” for lack of a more encompassing and descriptive term, I found myself jumping up and down advocating for a tool to standardize the task of gathering data from the news audience.

Crowdsourcing as a term was new, and by definition “bigger” than just “sourcing” because it could happen at scale, where scale could be thousands, hundreds of thousands, millions of people with the right call to action and programming framework.

WNYC’s “beer, lettuce, milk” price data gathering project was a favorite, although it appears to have been powered by a comment thread, mostly.

That was always one that stuck out in my mind, due to the quantitative nature of it. This wasn’t about asking the news audience for opinions; it was a method of gathering facts about the city and its bodegas, data that wasn’t compiled anywhere, and that made sense to bring together in one place, given the chaotic system (system?) of New York City bodegas.

###

Matt McAlister has gathered a Big Important List of crowdsourced reporting projects, and he’s notably compiling a list that extends beyond traditional journalism and news organizations, as we all should.

It’s a fascinating list of projects, and a reminder that it’s not always “content” news organizations are looking to “generate” from “users,” but information, or perhaps better yet, analysis of documents or images or cities or rivers or the world surrounding them.

Again, my own interest, albeit usually from afar, in tools like DocumentCloud, is the chance to bring the audience into the reporting process by giving them an assignment. “Read a piece of this giant 1100 page budget, or campaign finance bill, or FEC disclosure, or Friday night data dump (see the classic Talking Points Memo instance here), and annotate it so we can find the important stuff quickly.”

###

The fun part, naturally, isn’t in examining the past of crowdsourced reporting, but imagining the future. What does a platform to quickly spin up an instance of a crowdsourcing machine when news breaks look like? More than a map, surely, as amazing and powerful as location can be. It has to be flexible and fast and able to parse submissions into something useful, digestible, sortable so the most important information surfaces as if it were weightless.

Or are we already looking at the platform, the system, in Twitter or Facebook or Google Search or the Web itself? I don’t think I believe that. There must be more, or there must be a federated system to harvest and groom information from all these sources — not for the purpose of curation into a story or list or gallery, but for analysis, understanding, quantification at scale.

Continuing to dream of that ideal crowdsourcing platform…

Channel switching

Not sure how much I have to say these days, as most of my media-thinking-and-writing happens in the office and not on this or any blog, but I’m going to make a run at switching back to WordPress from the Tumblr I’ve been barely touching.

We’ll see. No promises.