The East Coast woke up this morning to news that an earthquake had hit Los Angeles. In Los Angeles, folks woke up to…an actual earthquake. But who broke that story?
All hail Ken Schwencke (@schwanksta) – our robonewsman overlord! pic.twitter.com/ND7yYWsbmQ
— Benny Spiewak (@BennySp) January 3, 2014
Indeed, Ken Schwencke, programmer and journalist at the Los Angeles Times, has been using a bot for more than a year to auto-report and publish newswire-type stories about earthquakes in California.
I wonder if @schwanksta even woke up to see his pet robot scoop y'all. http://t.co/NmDJ4CzvgV
— Ben Welsh (@palewire) March 17, 2014
@palewire Yes, yes I did.
— Ken Schwencke (@schwanksta) March 17, 2014
@palewire Woke up to set it live and see if my last patches worked.
— Ken Schwencke (@schwanksta) March 17, 2014
Schwenke continues to pursue the possibilities for robot reporting at the Times, even considering the possibility of having one bot talk to another.
@jeremybowers @palewire @harrisj A "los angeles quake response" bot would be amazing. "Ugh, a 5.0? Wake me up when my house pancakes."
— Ken Schwencke (@schwanksta) March 17, 2014
| 1036 tweets | What happened after 7 news sites got rid of reader comments Recode, Reuters, Popular Science, The Week, Mic, The Verge, and USA Today’s FTW have all shut off reader comments in the past year. Here’s how they’re all using social media to encourage reader discussion. |
| 699 | Facebook woos journalists with Signal, a dashboard to gather news across Facebook and Instagram Signal helps journalists find, source, and embed content from Facebook and Instagram. |
| 587 | Get AMP’d: Here’s what publishers need to know about Google’s new plan to speed up your website The speed gains are very real. But do publishers want to trade in the open space of what we’ve known as the web for yet another platform they have little control over? |