Here is New York, Part 2

Another shot from an afternoon photo walk around the office neighborhood. Fujifilm X-T1, 23mm f/1.4.

Here is New York

Construction on Spring Street, West Soho in Manhattan. Fujifilm X-T1, 23mm f/1.4.

Twitter API Changes Likely to Hobble Third-party Apps

Several third-party app makers have banded together to protest the shutdown of Twitter’s streaming APIs, along with a required switch to a new “Account Activity API.”

The removal of streaming services is likely to alter these apps in fundamental ways, breaking them in some cases. As of early Friday none of the developers noted had access to an existing beta that would let them test how the switch might affect their apps at scale.

If this sounds familiar it’s because Twitter has been making clumsy, developer-hostile moves for years. Ever since 2012, when they posted a confounding advisory warning developers not to create apps that “mimic or reproduce the mainstream Twitter consumer client experience,” Twitter has stoked an air of uncertainty around their third-party ecosystem.

One can venture a guess as to their motivation. Twitter has shifted away from its origins as a “platform” to a more traditional ad-supported play, one that requires large audiences and constant growth to thrive. If that’s your business model, a free-wheeling API isn’t in your best interest because it makes it difficult to guarantee the consistent delivery of ads to every user. But that’s still a guess, because as a company Twitter is just plain terrible about broadcasting its intent.

Ironically, Twitter owes its initial success to third-party developers more than most products. Twitter launched during the pre-iPhone, pre-app Internet, and was nominally based on SMS. But the way enthusiastic early members interacted with it most was through desktop apps built by third parties. For years Twitter had none of its own.

Twitter was born during an era when having an API was seen as a virtue, and enabling third-party developers was a key to growth. They reaped the benefits of that—they even co-opted their brand from a desktop Mac application—becoming immensely popular along the way.

Fast-forward to the present day and things have changed. Twitter is a company driven by growth on mobile, specifically its native iOS and Android apps. Desktop is a comparatively small share of their overall audience, and certainly not where the action is. And their revenue comes from ads, increasing the importance of controlling the user experience.

That’s fine. It’s just that Twitter doesn’t say so.

In many ways, I would respect Twitter more if they just came out and said it or announced in clear and unequivocal terms that they’re shutting down outside developers and why. This tweet from Dieter Bohn nails it (the rest of Dieter’s thread is worth checking out too):

Maybe this is part of a great product refocusing at Twitter. I should hope so, since they’ve been making puzzling moves lately, like abandoning native apps on major platforms. Maybe they’ve got a Big Plan. Who knows? And it’s that “Who knows?” that kills. The end result is Twitter comes off looking like a company that doesn’t know what it’s doing, generating uncertainty for its developers, and by extension, its users.

Fittingly, I switched over to using Twitter’s native app on my iOS devices last year because I thought it was a near certainty they would eventually screw over third-party developers. I wanted to start getting used to what that future might feel like if I wanted to stay connected to my friends and colleagues on their network. Not because they said that was what was going to happen, but because it felt like that was what was going to happen. (Perhaps more damning, I was also using it to break myself of an obsessive Twitter-checking habit. I found their native app interrupted the scroll so much it discouraged the kind of regular, diligent scanning I would do with Tweetbot. And it worked. I check in far less now than I did before.)

Update

Twitter has announced they are delaying the rollout of the Account Activity API, and have committed to giving developers 90 days before they deprecate the existing Site Streams and User Streams APIs. The thread announcing the change links to a migration guide and encourages developers to sign up for beta access, but many questions still remain.

Holland Tunnel

A few shots from some afternoon walks around the office neighborhood, not far from the Manhattan side of the Holland Tunnel.

There’s something about the tunnel that feels very Old New York to me. It hails from an age of great public works and industrial ambitions, now strained by the city that keeps rising around it. Still, it remains stitched into the fabric of daily life in the city—subsumed into the bones of New York, nearly overrun but not outgrown.

Meet Column Setter

ProPublica Design & Production team member Rob Weychert has created a handy tool for building responsive, grid-based layouts in Sass. We’re calling it Column Setter.

There are a couple things that set Column Setter apart. First, you can use any grid proportions you want. Unlike some other tools, it doesn’t rely on a set of predefined grids you have to cram your content into. You get to pick what works best for your design. Even better, it’s not a framework, so you don’t have to junk up your page with lots of krufty markup. Lastly, layouts built with Column Setter work in older browsers. While the future of advanced layout on the web is clearly CSS Grid, Column Setter’s got you covered if you need to support the broadest possible audience without resorting to lots of hacks or workarounds.

We’ve been using Column Setter on the new ProPublica.org for several months. It’s internal code name was “Josef” (as in Josef Müller-Brockmann, naturally). If you’ve browsed our site or read one of our feature stories recently, you’ve already seen Column Setter layouts in action.

Dig into the code on GitHub, and check out Rob’s writeup over on the ProPublica Nerd Blog.

Facebook’s News Feed Update Relies on Unreliable Signals

Like pretty much everyone else in journalism I’ve been thinking a lot about Facebook’s big News Feed announcement.

In case you missed it, content posted by publishers and institutional players will now be downplayed in the News Feed in favor of stuff your friends and family share and comment on. The result will be fewer articles from newsrooms and (shudder) brands, and more stuff from actual people like your Aunt Susie. Fair enough. It’s named after a face book for a reason, right?

Facebook says they’re doing this to address the “well-being” of their users. Mark Zuckerberg uses the word multiple times in his post about the announcement. What they don’t say is “fake news” or address how these changes might stop bad guys from manipulating their network like they did during the U.S. Presidential election and Brexit (and likely elsewhere, too). Which is odd because those are clearly the precipitating events that led to these changes. And there’s good reason for concern, because this update may do little to stop it all from happening again.

Under this new arrangement “engagement” becomes the key factor in determining what users see. Publishers will still be able to post their stories, but it will take comments, shares, and “likes” from friends and family on those posts for them to rise to the top. In Facebook’s own words, “Posts that inspire back-and-forth discussion in the comments and posts that you might want to share and react to.” That means Facebook will be basing their revamped feed on a process that responds to emotional reactions.

That’s a setup that talks straight to the lizard brain. Moreover, it has a weak correlation with value. I’m talking about the good-for-people-and-society kind of value, not good-for-Facebook’s-bottom-line value. Josh Benton nails it in his post on NiemanLab:

[A]t a more practical level, it seems to encourage precisely the sort of news (and “news”) that drives an emotional response in its readers — the same path to audience that hyperpartisan Facebook pages have used for the past couple of years to distribute misinformation. Those pages will no doubt take a hit with this new Facebook policy, but their methods are getting a boost.

Content that “starts conversation” isn’t automatically good content. Just because live videos “get six times as many interactions as regular videos” doesn’t mean they’re any better for us. It just means we’re reacting to them more. Facebook needs to know why we’re reacting, and incorporate more objective elements into their algorithms instead of relying on subjective emotional ones. Otherwise they’re leaving the door wide open to still more social poison.

Building those sorts of objective filters is precisely where Facebook has struggled in the past. Efforts to halt “engagement bait” have focused on cursory signals that have proved ineffective against more calculated efforts from troll farms and the like.

And then there are the unintended consequences. For that I’ll cite a very recent personal example.

Last week a member of my wife’s extended family passed away. She had been active on Facebook, and when she died someone updated her page to let us know what happened and when and where the funeral services would be. Because this post keeps getting “reactions” and comments it keeps appearing at the top of my feed, helpfully reminding me of her death over and over again, days after the fact.

Keep in mind this is a company that knows how often I log in, if I’ve seen this post and—yes—if I’ve “engaged” with it. Even with that information they aren’t getting it right. Why? Because engagement alone is too brittle a determining factor, and responds too easily to the wrong signals.

As for publishers, they’ll still be right in the thick of it, hunting for new ways to make their content popular under this latest set of conditions. It’s naive to think they’ll simply walk away. Even a reduced slice of billions of users is too rich a prize for them to ignore.

Institutional content will still get shared on Facebook. Virtuous publishers and ne’er-do-wells alike will still fight like hell for it to be their content that gets shared. Facebook has to get better at telling the good from the bad and incorporate tools that know the difference in order for this to work.

The Road to Zion

Shot from the side of the road about 15 minutes outside Springdale, Utah, on the way to Zion National Park. We spent a couple days hiking there this past summer. Zion is a gem, and a reminder of what a treasure the national parks system is. Seemed only fitting to post after last week’s news cycle.

We’re Not Shutting Up

I get a lot of questions about my gig. Of those, the third most frequently asked is about swag: Have we got any? (No, really. I keep track. We’ll save Numbers One and Two for another time.)

Well, we’ve finally got something to answer that question with, and it’s pretty great:

The back story: Last week, a certain White House official was widely quoted saying the media should “keep its mouth shut.” My boss, editor-in-chief Steve Engelberg, told him (via the New York Times) the diplomatic equivalent of “NOPE.” I was away at a conference when I pulled out my laptop, saw all this, and thought, “Hey, I’ve got an idea…”

Several hours later, with the help of our crack social team, biz dev director Celeste LeCompte, and the fine folks at Cotton Bureau, we had ourselves a damn fine shirt. Roughly $10 from each sale goes towards funding ProPublica’s work, the rest lets Cotton Bureau cover their bills.

If you’re into it, go grab one (or several). And if you’re really into it, give us a shoutout or two on Facebook or Twitter and help spread the word, won’t you?

Morning Commute

Morning commute, West Soho/Hudson Square, New York City. iPhone 7, black and white conversion via Darkroom.

Photojournalists Call on Camera Manufacturers to Add Encryption

The Freedom of the Press Foundation has published an open letter signed by over 150 photojournalists and documentary filmmakers asking manufacturers to build encryption into their cameras.

This is important. Consider what can be easily revealed about a confidential source when a government or hostile party seizes a journalist’s camera, and you begin to understand what’s at stake.

Android, iOS, and macOS all offer system-level encryption for their devices, but there’s nothing to stop someone from pulling the data card out of most any camera, plugging it into a reader, and freely reviewing its contents—and “inspecting” cameras is a favorite tactic of many a government, police force, or criminal antagonist. The Committee to Protect Journalists notes such incidents are so common they can’t “realistically track” all of them.

There are too many places in the world where a single photo can put a source or photographer in lethal danger, and that makes the current lack of hardware-level protection unacceptable. As someone who collaborates with and directs photojournalists’ efforts on a daily basis, I endorse the Foundation’s call.