The Nieman Lab has an awesome and invaluable “Reading Page”

Usually I’m reading their content via a feed reader, but last night I visited their actual site and I noticed that the Nieman Lab has a reading page!

Since they’re unlikely to report on the mechanics of some of their own website and journalistic output, I’ll take a moment to highlight it on their behalf.

Reading pages or Linkblogs

Traditionally known as linkblogs back in the old blogosphere days, this sort of web pattern is probably better and more specifically called a “reading page” now. (Even Nieman titles the page “What We’re Reading” and uses /reading/ in the URL path to the page itself.) Many people still maintain linkblogs or bookmark pages (often on social silos like Pinboard, Pinterest, Twitter, Pocket, Instapaper, et al.), but generally the semantic name there implies articles or pages that were found to be of general interest or that one wanted to keep to read or consume later. On today’s more advanced web, there’s actually more value in naming it a reading page as it indicates a more proactive interest in the bookmarked content–namely having spent the time, effort, and energy to have actually read the thing being bookmarked. This additional indication of having more skin in the game provides a lot of additional value of a read post over a simpler bookmark post in my mind. It’s also part of the reason my website sends and receives read-specific webmentions.

This pattern of providing links of read material is pretty cool for a variety of reasons.

Discovery

First, if you’re following and reading the Nieman Lab, you’re very likely going to be interested in many of the things that they’re reading, researching, and covering. By providing a reading page they’re giving their readers a trove of useful data to discover articles and material in similar and tangential spaces that the lab may not be able to actively cover or engage in at the time. 

Context

By knowing what the Lab is reading, you’re provided with a broader perspective of the things they’re actively interested in. By reading those things yourself, you’ll have increased context into what they’re doing, what those areas look like, and what they are adding to the conversation in their research and work.

Added value to their site

Linkblogging has long been a thing, and, in part, is what a large number of Twitter users are typically doing. In Nieman Lab’s case, they’re just doing it on their own website, which adds tremendous value to it. By smartly hosting it on their own site they’re also guarding against the built value of their read archive disappearing if they were hosted on a social silo (remember Delicious? CiteULike?). Also by keeping it on their site, it has more long-tail value than if it were to all disappear into the new-content-wins attention machine that Twitter has become.

Of course I’d personally find it a lot more beneficial if they provided or advertised a linkblog feed for their reading page. Sadly they don’t. However, if you’re as interested as I am, you’ll dig under the hood a bit to discover that Nieman Lab’s site is built on WordPress and they’re using that page likely with a category, tag, or other taxonomy. So with a short bit of intuitive guessing about how WordPress is structured, we happily discover there is a feed of their reads at https://www.niemanlab.org/reading/feed/. (I suspect this feed exists as a design choice by WordPress than by the design or will of the Nieman Lab.) If you prefer a faster, one button subscribe option:

If Nieman would like their own universal follow button like this, take a peek at what SubToMe has to offer on this front.

Value to research

By accumulating a trove of links and summaries, which they’re hopefully keeping, they’re creating a huge relevant database for future research on the topics in which they have interest. The small pieces that may not make sense today may potentially be woven into future narratives and pieces of research later, but this sort of thing is vastly harder to do without reading and making note of it. In a sense, they’re creating a corporate or research lab-based commonplace book for their own use.

Other Examples

While I’ve seen many people (generally individuals and not magazines, companies, or other bigger outlets) regularly publish newsletters or weekly posts on what they’ve found on the web that is interesting, I haven’t seen as many who publish specific pages or archives of what they’re reading. Even fewer provide RSS or other feeds of this content.

The IndieWeb wiki read page has some useful and interesting examples of this behavior, but they’re almost all individuals. 

One other example I can think of in the journalism space, mostly because it’s getting to that end-of-the-year recap time is Bloomberg’s Jealousy List, which this year incidentally has some fun little drolleries that move as you scroll the page. This subset of reading lists is interesting as a group of articles Bloomberg wished they’d written and published themselves. This may indicate that they’re keeping a reading list internally, but just not publishing it regularly like Nieman is.

I can’t help thinking if Nieman Lab’s OpenFuego bot is a part of their workflow in creating their reading page as well?

And finally, since I also have a similar behavior, I’ll mention that you can find my reads on my reading page (sometimes with commentary) or follow it all via RSS if you like.

Are you aware of other people or organizations publishing lists of what they’re actively reading online? Do they provide feeds? How can we make this feature more prevalent on the open web?

I’ve noticed that Bloomberg Businessweek’s Jealousy List for 2020 has quirky little animated drolleries racing around on it as you scroll up and down the page.

This makes me wonder what web designers and developers would put on their own personal jealousy lists for 2020. What types of features and functionality have you seen this year that you’d love to have on your own website or in your own projects?

Read As it settles into Vox, Recode is starting a new project to help people feel power over algorithms (Nieman Lab)
"It's about cutting through the apathy that a lot of people have about tech because it feels mysterious, letting people know there are decisions and changes you can make to your behavior that will feel empowering to people."
Listened to Body of Law: Beyond Roe from On the Media | WNYC Studios

Justice Ginsburg says she wishes it had been another case, not Roe v. Wade, that SCOTUS heard as the first reproductive rights case. On the Media and The Guardian take a closer look.

A majority of Americans polled by CSPAN last year couldn't name a Supreme Court case. Of those who could, Roe v. Wade was by far the most familiar, with 40 percent able to name it. (Only five percent could name Brown v. Board of Education.) And since it was decided in 1973, a majority — roughly 70 percent — have consistently said they want Roe upheld, albeit with some restrictions on legal abortion.

But what do we really know about Roe? Justice Ruth Bader Ginsburg has often said she wishes it had been another case that the Supreme Court heard as the first reproductive freedom case instead. It was Susan Struck v. Secretary of Defense, and it came to the high court during the same term as Roe

The year was 1970, and the Air Force (like the other branches of the military) had a regulation banning female service members from having a family. If a servicewoman got pregnant, she would get discharged. Captain Susan Struck was a nurse serving in Vietnam, and she challenged the decision in court with Ginsburg as her lawyer. However, the court never heard the case because the Air Force changed their policy first. For this week's show, we partnered with The Guardian (read their story here) to learn more about Susan Struck’s fight and its bigger lessons for reproductive freedom and for women in the workplace. 

Our producer Alana Casanova-Burgess and The Guardian's health reporter Jessica Glenza spoke to Struck about the difficult decision she made to give her baby up for adoption in order to fight the regulation. Plus, we hear why legal scholars think this case "deserves to be honored by collective memory," and how Ginsburg's arguments to the Supreme Court differed from what the justices decided in Roe

Then:

- Slate's Dahlia Lithwick explains the threats to reproductive rights in the court right now;

Neil Siegel of Duke Law School puts the Struck case in context and discusses what better questions we could be asking about women's equality;

- activist and scholar Loretta Ross explains the tenets of reproductive justice and how they expand the frame beyond Roe and abortion;

- and Reva Siegel of Yale Law School tells the story of how abortion was discussed before 1973, including during the Women's Strike of 1970. And she describes the framework of ProChoiceLife, which expands the idea of what pro-life policy is. She is also the co-editor of Reproductive Rights and Justice Stories

Read The Guardian’s print version here, and share your story with Jessica Glenza if you were a woman serving in the military before 1976.

Music by Nicola Cruz, Kronos Quartet, and Mark Henry Phillips

Bookmarked Trump Impeached for Abuse of Power and Obstruction of Congress (nytimes.com)
Voting nearly along party lines, the House approved two articles of impeachment against President Trump, making him the third president in history to face removal by the Senate.
A historic day, except that it doesn’t feel as validating because there is every chance that the Senate is going to pretend that the underlying abuses never existed.
Listened to From Upspeak To Vocal Fry: Are We 'Policing' Young Women's Voices? from Fresh Air | NPR

Journalist Jessica Grose, linguistics professor Penny Eckert and speech pathologist Susan Sankin discuss upspeak, vocal fry and why women's voices are changing — and whether or not that's a problem.

Journalist Jessica Grose is no stranger to criticism of her voice. When she was co-hosting the Slate podcast, the DoubleX Gabfest, she would receive emails complaining about her "upspeak" — a tendency to raise her voice at the end of sentences.

Once an older man she was interviewing for an article in Businessweek told her that she sounded like his granddaughter. "That was the first moment I felt [my voice] was hurting my career beyond just irritating a couple listeners," Grose tells Fresh Air's Terry Gross.

–Originally bookmarked on December 18, 2019 at 09:53AM
Listened to Jim Luke by Terry Greene from Gettin' Air The Open Pedagogy Podcast | voicEd

Jim Luke (@econproph) is an economics professor at Lansing Community College and pioneer of their Open Learn Lab. Jim is Running errands for ideas at the intersections of economics, org theory, higher ed, and open pedagogy. His economist’s take on Open Education, higher education and how we can use The Commons for the good of learners is truly fascinating.

Cover art for Gettin' Air

I like the idea of “Running errands for ideas”.

They took a reasonable stab at defining the commons, but never quite got it concretely for those who’ve not come across it before.

I also appreciated Jim’s idea about the commons being needed to be applied to smaller groups around the size of the Dunbar number. Larger groups definitely seem to have issues as things scale up, not the least of which is the potential for free-riding. Colin Woodard’s book could be looked at from an economics perspective particularly as different nations within America have different approaches to the commons and who pays for what and how much trust those groups have with each other.

Listened to Mia Zamora by Terry Greene from Gettin' Air The Open Pedagogy Podcast | voicEd

Mia Zamora (@MiaZamoraPhD) is Associate Professor of English and Director of the MA in Writing Studies at Kean University in New Jersey (@KUWSP). She studies the dual layer of electronic literature, words born in an electronic environment, among other things. In this episode Mia describes innovative and open projects and courses that she has worked in like the #NETNARR Networked Narratives course at Kean.

Cover art for Gettin' Air