7 ms·
I've believed since newsdiffs.org (mentioned in the OP) was launched that an in-house diff-tracker/displayer for the New York Times would be both a win in trans
by danso 11y ago
I've believed since newsdiffs.org (mentioned in the OP) was launched that an in-house diff-tracker/displayer for the New York Times would be both a win in transparency, accuracy, and the company's bottom-line. The first two are mostly self-evident...in terms of improving the bottom-line...well, I often go to the NYT for breaking news. For a given event, they'll often have a main story which they update throughout the day. The obvious problem is that if I've read it once, I have to re-read the entire story throughout the day, and mentally parse out the updated bits.
So why not have, for _every_ story, a "History" link, or even a _feed_ of latest changes, so that readers who re-visit a story can quickly see the atomic updates? For my own reading habits, this would cement the NYT has a place to go to for developing stories...the transparency/accuracy bit are just icing on the cake.
This issue of having an in-house Newsdiffs was brought up by the public editor back when Jill Abramson was still editor:
http://www.nytimes.com/2011/06/26/opinion/sunday/26pubed.html http://www.nytimes.com/2011/06/26/opinion/sunday/26pubed.htm...
Here's what she said:
> Right now, tracking changes is not a priority at The Times. As Ms. Abramson told me, it’s unrealistic to preserve an “immutable, permanent record of everything we have done.”
I can't speak for her true motives or intentions...but part of the problem here is technical ignorance. Her perception seems to have been that tracking changes would have been too much of a burden -- and she is justified in thinking this if she has never worked with something that uses a diff-like program...and in my experience, this includes most news people...in a newsroom, editing and re-editing stories and supplying reasons (i.e. as in a correction) is a very manual process. If a newsroom is using WordPress, sure, they know of the concept of article versions...but they don't really grok the ability for machines to create timestamped diffs.
However, if Ms. Abramson was familiar with the kind of system that Github (or Wikipedia, for that matter) uses, she would see that keeping an immutable, permanent record is actually quite easy for machines to do. So to create a inhouse change-log-per-article would be quite easy, technically, and with some interface work, it'd be a very welcome feature to more than a few readers, IMO.
edit: In terms of "most news people" not knowing diff...I'm basing this on anecdotal experience with non-programming investigative journalists who, among all journalists, have the most to benefit from understanding the implications of an efficient document diff, but I haven't worked with any who demonstrated that grasp. A common scenario is having two versions of some important document and wanting to see every change made. A diff would not be perfect, but it doesn't have to be, it just needs to triage possible changes to further investigate.
- reagency 11y agoThis is basic journalistic ethics, to post a log of corrections made to an article.
- danso 11y agoRight...but the implementation details matter. And not everything that is worth tracking is not necessarily a correction. In terms of corrections, for non-trivial ones, it sometimes takes more than a day to get the true story...and this is sensible, as no one wants to correct the correction. This process is pretty manual. In terms of changes, as described by the OP, it's not always clear what kind of changes deserve a manually-written line-item description. Fixing grammar and punctuation? Adding a new quote (usually when a new quote is added, an "Update" note is prepended to the story, but for most WordPress using organizations, this is again a manual process)? Rearranging the lede to put a more important, newly discovered fact up higher? So instead of leaving it to humans to decide which changes are worth manually logging...just let the machine timestamp the changes and show the diffs, allowing the reader to see them in a transparent way. For changes that require no explanation (i.e. the addition of an Oxford comma), let them stand alone. For changes that require some context, such as a new quote, give the option of letting the reporter/editor describe the reason, e.g. "Mr. Smith responded to a reporter's calls at 3 p.m. today".
- Natsu 11y agoIn this case, the edits were so large, I think they would have been better served with an entirely new follow-up story rather than replacing the original like that.
- toufka 11y agoIt's interesting that the log would also reflect internal editorial struggles within the NYT. If you scroll through the future changes since the major change, you see Silicon Valley described "sexist" then "male-dominated" then "sexist" again [1]. Seeing the flip-flopping edits would surely affect how the article (and SV) is perceived beyond the words themselves. [1] http://newsdiffs.org/diff/934591/934616/www.nytimes.com/2015/07/11/technology/ellen-pao-reddit-chief-executive-resignation.html http://newsdiffs.org/diff/934591/934616/www.nytimes.com/2015...