<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Grasswire on Medium]]></title>
        <description><![CDATA[Stories by Grasswire on Medium]]></description>
        <link>https://medium.com/@grasswire?source=rss-362e24621007------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*kZ_DmkJMYJTJEZg2.jpeg</url>
            <title>Stories by Grasswire on Medium</title>
            <link>https://medium.com/@grasswire?source=rss-362e24621007------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 20:23:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@grasswire/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Grasswire Announces Re-Launch of Citizen Newsroom Platform]]></title>
            <link>https://medium.com/grasswire-blog/grasswire-announces-re-launch-of-citizen-newsroom-platform-d99676f3ae5b?source=rss-362e24621007------2</link>
            <guid isPermaLink="false">https://medium.com/p/d99676f3ae5b</guid>
            <category><![CDATA[news]]></category>
            <category><![CDATA[medium]]></category>
            <category><![CDATA[journalism]]></category>
            <dc:creator><![CDATA[Grasswire]]></dc:creator>
            <pubDate>Tue, 01 Sep 2015 21:57:52 GMT</pubDate>
            <atom:updated>2015-09-01T22:01:01.018Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XaO4oYqRclRKvsc6QcOlQg.png" /></figure><p>Before today, the honor of the world’s largest newsroom belonged to the BBC with nearly 8,000 reporters, editors and other staffers in the United Kingdom and in locations around the world.</p><p>Today, the honor of the world’s largest newsroom now belongs to <a href="https://grasswire.com/">Grasswire</a> with a staff of 2.92 billion citizen reporters around the world.</p><p><a href="https://grasswire.com/">Grasswire</a>, a service that initially sought to help fact-check content and statements published on social media, has re-launched as a powerful storytelling platform, enabling anyone with a computer and an Internet connection to participate in the world’s largest open newsroom, working alongside professional and citizen journalists alike to research, verify and publish the most-interesting and important world news stories of the day.</p><p>“Our goal is to democratize the editorial system,” said Austen Allred, <a href="https://grasswire.com/">Grasswire</a> founder and chief executive. “The more people that are involved in the journalism process, the better the news becomes.”</p><p>As part of our new initiative, <a href="https://grasswire.com/">Grasswire</a> has completely re-designed its website to provide a visually-rich storytelling experience powered entirely by Grasswire’s users. In addition to publication space, <a href="https://grasswire.com/">Grasswire</a> provides citizen reporters with a number of tools to help users examine elements of a story, including an open newsroom powered by Slack where anyone can talk with other users and two professional editors to verify elements of a story before they are published.</p><p><a href="https://grasswire.com/">Grasswire</a>’s brand-new website is supplemented by a responsive mobile website, also launching today, and a set of smartphone apps that will be unveiled in the future. The launch ends four weeks of beta testing during which <a href="https://grasswire.com/">Grasswire</a> logged more than a half-million global page views.</p><p>—</p><p><strong>For questions and general inquiries, contact Austen Allred, Chief Executive Officer and Editor-in-Chief, at austen@grasswire.com or (801) 369–2444.</strong></p><p>To discuss news and editorial partnerships, e-mail Joanne Stocker at joanne@grasswire.com or Matthew Keys at matthew@grasswire.com.</p><p>To download our press kit, visit <a href="https://app.box.com/grasswirepresskit">https://app.box.com/grasswirepresskit</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d99676f3ae5b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/grasswire-blog/grasswire-announces-re-launch-of-citizen-newsroom-platform-d99676f3ae5b">Grasswire Announces Re-Launch of Citizen Newsroom Platform</a> was originally published in <a href="https://medium.com/grasswire-blog">Grasswire Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On Judgment Calls]]></title>
            <link>https://medium.com/grasswire-blog/on-judgment-calls-1ca0a53fcfef?source=rss-362e24621007------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ca0a53fcfef</guid>
            <category><![CDATA[journalism]]></category>
            <category><![CDATA[medium]]></category>
            <dc:creator><![CDATA[Grasswire]]></dc:creator>
            <pubDate>Wed, 26 Aug 2015 21:31:36 GMT</pubDate>
            <atom:updated>2015-08-26T21:37:05.198Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*LcAqoEJuLh3pU-M5DQMKjw.jpeg" /><figcaption>WDBJ-TV reporter Alison Parker (left) and photojournalist Adam Ward. (Image: WDBJ-TV/Supplied)</figcaption></figure><p>Like many of our colleagues in newsrooms across America and around the world, the Grasswire team performed our job duties today with a sense of deep shock and profound sadness over the sudden and very public loss of <a href="http://www.wdbj7.com/news/local/law-enforcement-investigating-incident-at-bridgewater-plaza/34923086">two fellow journalists</a>.</p><p>None of us on staff personally knew WDBJ-TV reporter Alison Parker* or photojournalist Adam Ward, but the industrial thread that unites all journalists has made every staffer in every newsroom around the world feel the sting of today’s tragic event. As with so many in our institutional family, we send our thoughts to everyone affected by today’s shooting in Virginia.</p><p>Throughout the day, Grasswire has received feedback from our community and our audience about how we chose to cover today’s news, and we wanted to take a moment to share with you some thoughts on some of the judgment calls we made in the course of reporting this story.</p><p>When we first heard about the shooting earlier this morning, we began covering it as we would any other story: By searching for reports and eyewitness accounts, verifying and reviewing content, and then publishing the most-informative and interesting pieces of news and media that had been confirmed as fact.</p><h3>Grasswire on Twitter</h3><p>BREAKING: Journalist, news photographer fatally shot during live broadcast - @WDBJ7 pic.twitter.com/JGaE7LJHk7</p><p>Within minutes of the first emerging reports, Grasswire found and reviewed an amateur video of what appeared to be a digital recording from WDBJ-TV’s broadcast signal. That video showed approximately half a minute prior to the first initial shot and a few seconds after that shot was fired. The video was corroborated by a second, clearer video taken straight from a recording of WDBJ-TV’s live broadcast that showed the same event.</p><p>Grasswire chose not to re-distribute any recording of the live broadcast on our social media accounts. We did, however, choose on our beta site to embed a tweet from a television news journalist who uploaded a complete, clear copy of the recording. The mechanism of our beta platform does not “autoplay” videos embedded from social media sites, and does not re-publish or embed Twitter videos at all.</p><p>We feel the recording from WDBJ-TV’s signal was newsworthy in that it depicted a notable and significant event that had been broadcast live to tens of thousands, if not hundreds of thousands, of households in the Roanoke viewing area. While we could have embedded the footage from any number of YouTube uploads, we felt our decision to instead link to the WDBJ-TV footage carried through on our duties as journalists to report and make accessible newsworthy material while at the same time affording our audience the choice to view, or not view, the footage themselves.</p><p>Throughout the morning we continued to report verifiable details as they became available. When news agencies confirmed the identity of the alleged gunman as former WDBJ-TV employee Vester Flanagan (“Bryce Williams”), we reached out to law enforcement and other sources to confirm his identity and certain elements of stories that were being reported by news agencies and on social media.</p><p>As part of our research into Flanagan, we and a handful of other journalists found two social media accounts that were purportedly connected to Flanagan. While we could not definitively confirm the accounts were associated with Flanagan, there were strong indications that the social media profiles had been used by Flanagan prior to Wednesday morning’s shootings.</p><p>One of the accounts found by Grasswire was a Twitter account containing photos of Flanagan and posts that are believed to have been published by the suspected gunman prior to the shooting. While we monitored the account, someone strongly suspected to be Flanagan began publishing a series of posts about the day’s shooting. The posts ended with two separate videos that offer a first-person perspective of Wednesday’s fatal shooting involving the two WDBJ-TV journalists. The same video was also posted to a Facebook account believed to be associated with the alleged gunman.</p><p>Grasswire’s editors immediately downloaded and reviewed copies of the videos posted on Twitter and Facebook. Upon review, the decision was made that Grasswire would not link to or redistribute the footage on any platform because it did not meet our criteria of newsworthiness, importance and interest.</p><h3>Grasswire on Twitter</h3><p>Our thoughts are with @WDBJ7 and the family/friends of Alison Parker and Adam Ward. pic.twitter.com/1foXOJYEEP</p><p>Our decision not to re-distribute or provide access to the footage came without debate or discussion. Our editorial team reached the decision immediately and unanimously. We felt that the footage served no valuable news purpose and that it did not adequately provide new insight or information into what was already widely-reported news event.</p><p>We want to be very clear that our decision today is not a hard-lined policy. We have, and we will, publish sensitive material that some may consider to be graphic, violent and/or distressing if we feel we can justify our position in doing so.</p><p>Today, we felt we would not be able to justify our decision if we casted ourselves as a conduit to a film depicting a murder produced by the murder suspect himself.</p><p>As is the case during any developing news story, there will be critics from both within and outside the information industry who offer their guidance and suggestions on best practices in reporting sensitive information and material, especially when such reporting involves an event of tragedy. We respect the decisions of other journalists and newsrooms when it comes to their own method of reporting the news, even if it may differ from our own.</p><p>We know there will be those who applaud our decisions to publish at times and to withhold at other times, and we know there will be those who challenge those decisions. As we move forward <a href="http://beta.grasswire.com/">with a new version of our website</a>, our community will play a big role in those editorial decisions as well, and we welcome any feedback from our community and our audience.</p><p>— Austen, Joanne, Matthew and the Grasswire team</p><p>* <em>Disclosure: Parker’s fiancé is an acquaintance of a Grasswire editor</em></p><p><em>Originally published at </em><a href="https://medium.com/@grasswire/on-judgment-calls-243836d134ff"><em>medium.com</em></a><em> on August 26, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ca0a53fcfef" width="1" height="1" alt=""><hr><p><a href="https://medium.com/grasswire-blog/on-judgment-calls-1ca0a53fcfef">On Judgment Calls</a> was originally published in <a href="https://medium.com/grasswire-blog">Grasswire Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Grasswire’s Messaging Service]]></title>
            <link>https://medium.com/grasswire-engineering/grasswire-s-messaging-service-1cfa4c896a07?source=rss-362e24621007------2</link>
            <guid isPermaLink="false">https://medium.com/p/1cfa4c896a07</guid>
            <dc:creator><![CDATA[Grasswire]]></dc:creator>
            <pubDate>Sun, 26 Jul 2015 00:48:27 GMT</pubDate>
            <atom:updated>2015-07-26T00:48:27.179Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Nice post detailing your tech stack! I was wondering if you could share some thoughts on your choice of message broker. What system did you chose, for what reasons, and have you had any pain points with it? — <a href="http://blog.lukecycon.com/"><strong>lukecycon</strong></a></blockquote><p>Thanks Luke! We chose RabbitMQ. One of the most compelling features of RabbitMQ is the ability to set up complex routing to different consumers. This can be really important if things are divided into many smaller services. The other option is Kafka. Kafka has very particular message delivery guarantees that we don’t need. Kafka also seems to be optimized for 100s of thousands of messages per second which is also something we don’t need (at least not at the moment). All in all, we chose RabbitMQ because it is more mature, it has a lot of client support, and some very powerful features for routing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1cfa4c896a07" width="1" height="1" alt=""><hr><p><a href="https://medium.com/grasswire-engineering/grasswire-s-messaging-service-1cfa4c896a07">Grasswire’s Messaging Service</a> was originally published in <a href="https://medium.com/grasswire-engineering">Grasswire Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A URL Shortener Service in 45 lines of Scala]]></title>
            <link>https://medium.com/grasswire-engineering/a-url-shortener-service-in-45-lines-of-scala-f861d4b8e5e3?source=rss-362e24621007------2</link>
            <guid isPermaLink="false">https://medium.com/p/f861d4b8e5e3</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[scala]]></category>
            <dc:creator><![CDATA[Grasswire]]></dc:creator>
            <pubDate>Sun, 26 Jul 2015 00:46:03 GMT</pubDate>
            <atom:updated>2015-07-26T00:50:38.561Z</atom:updated>
            <content:encoded><![CDATA[<p>We’re thinking about creating a URL shortener service to make it easier to share Grasswire links across the web. Here’s a rough proof-of-concept that implements the basic functionality in 45 lines of code:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c611eabe4b36282f69e238a3f67d9a91/href">https://medium.com/media/c611eabe4b36282f69e238a3f67d9a91/href</a></iframe><p>To create a short link, we generate a random String and use Redis to store the original url with our random String as the key. When a GET request is issued to the shortened url, we retrieve the original url from Redis. If such a value exists, we redirect, otherwise we respond with a Not Found status.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f861d4b8e5e3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/grasswire-engineering/a-url-shortener-service-in-45-lines-of-scala-f861d4b8e5e3">A URL Shortener Service in 45 lines of Scala</a> was originally published in <a href="https://medium.com/grasswire-engineering">Grasswire Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Grasswire’s Technology Stack]]></title>
            <link>https://medium.com/grasswire-engineering/grasswire-s-technology-stack-df032fc3329f?source=rss-362e24621007------2</link>
            <guid isPermaLink="false">https://medium.com/p/df032fc3329f</guid>
            <dc:creator><![CDATA[Grasswire]]></dc:creator>
            <pubDate>Sun, 26 Jul 2015 00:43:35 GMT</pubDate>
            <atom:updated>2015-07-26T00:43:35.395Z</atom:updated>
            <content:encoded><![CDATA[<p>At Grasswire, we use a number of technologies and tools to power our real-time, crowd-sourced news engine.</p><p><strong>Backend</strong></p><p>There are three backend services at the core of Grasswire, all of which are written in <a href="http://www.scala-lang.org/">Scala</a>.</p><ol><li>A RESTful API</li><li>A service that processes all user actions (upvotes, fact-checks, etc)</li><li>A service that consumes/analyzes news content from Youtube, Twitter, etc in real-time</li></ol><p>The RESTful API is written using Spray, which describes itself as:</p><blockquote><em>an open-source toolkit for building REST/HTTP-based integration layers on top of Scala and Akka. Being asynchronous, actor-based, fast, lightweight, modular and testable it’s a great way to connect your Scala applications to the world. (</em><a href="http://spray.io/"><em>spray.io</em></a><em>)</em></blockquote><p>All user actions (upvotes, fact-checks) posted to the API are sent to a separate service for processing via a message broker. There are many benefits to using a message broker. Two important ones are:</p><ol><li>Messages can be durable; if a service (as a consumer) goes down and can no longer process those messages, they will stick around until the service is restored.</li><li>A message broker provides an easy way to load-balance message processing across machines.</li></ol><p>Grasswire uses <a href="http://redis.io/">Redis</a> for caching (and other things) pretty extensively. Redis is incredibly fast and offers some useful data structures, such as lists, hashes, sets and more.</p><p>We use Spray to write our http server, but we also use its http client functionality for consuming content from various APIs. Spray is actor-based so it’s very fast which is important since we have to consume and process lots of content very quickly.</p><p>We are increasingly making use of <a href="https://github.com/scalaz/scalaz">Scalaz</a> in order to do purely functional programming in Scala. Our limited use of it so far has already paid off in a big way. We hope to use Scalaz even more going forward. It will allow us to write code that is more “pure”, more composable, and generally easier to reason about.</p><p>All of Grasswire’s backend services are deployed on Amazon Web Services.</p><p><strong>Frontend</strong></p><p>Grasswire’s website is an <a href="https://angularjs.org/">AngularJS</a> app. Angular is a JavaScript framework for writing dynamic web applications. Angular has served us well — it is feature-rich, provides us with a lot of flexibility in how we structure our application, and it’s been an essential part of building a modern, real-time web experience on Grasswire.com.</p><p>The Grasswire website is a consumer of our RESTful API, just like our Android app; the website is “merely” a client. This makes deploying the site very easy — Grasswire.com is hosted on Amazon S3 as a static website. We make quick changes to the site all the time and pushing those changes to production is simply a matter of uploading a new build directly to S3.</p><p>Hopefully this post gives you a basic idea of some the components at work behind the scenes of Grasswire. If there’s anything you’d like us to explore in future posts, please don’t hesitate to ask!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=df032fc3329f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/grasswire-engineering/grasswire-s-technology-stack-df032fc3329f">Grasswire’s Technology Stack</a> was originally published in <a href="https://medium.com/grasswire-engineering">Grasswire Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Grasswire’s Next Steps]]></title>
            <link>https://medium.com/grasswire-blog/grasswire-s-next-steps-6d13bb647e48?source=rss-362e24621007------2</link>
            <guid isPermaLink="false">https://medium.com/p/6d13bb647e48</guid>
            <category><![CDATA[crowdsourcing]]></category>
            <category><![CDATA[news]]></category>
            <category><![CDATA[journalism]]></category>
            <dc:creator><![CDATA[Grasswire]]></dc:creator>
            <pubDate>Mon, 13 Jul 2015 23:54:23 GMT</pubDate>
            <atom:updated>2015-07-14T00:01:42.475Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7gOzw0yn3UsZNRrvgkr-4g.png" /></figure><p>When we first launched <a href="http://grasswire.com/">Grasswire</a> last year, we had a vision of what an open newsroom would look like: Stories contributed hourly by dozens, if not hundreds, of users, and fact-checked by a community of thousands coming from all corners of the Internet to contribute to a new kind of editorial process not before seen in the traditional journalism industry.</p><p>Thanks to our thousands of users — some of whom drop by occasionally, others who contribute regularly — we’ve learned a lot about the process. We have a better idea of what works, what doesn’t, what the community needs and what we can do to create a richer, more-robust open newsroom experience for all.</p><p>Today, I want to talk about two changes we’re making to Grasswire, both of which are going to vastly improve the user experience.</p><p>First, I’m excited to announce the hiring of two managing editors: <a href="https://twitter.com/joanne_stocker">Joanne Stocker</a>, a Grasswire power user and contributing journalist currently based in Israel, and <a href="http://twitter.com/matthewkeyslive">Matthew Keys</a>, a former Thomson Reuters journalist with nearly a decade of digital news experience.</p><p>When we started Grasswire last year, we did so without a professional editorial staff — we wanted our users to be at the heart of the process, and we structured everything we did around that idea. That overall mission hasn’t changed — our users still power the editorial process — but as Grasswire has grown we’ve begun to recognize that our community could benefit from the guidance professional and experienced editorial staffers might bring to the table.</p><p>So that’s what Joanne and Matthew will do. Think of them as “power users” who are on-call to help offer the Grasswire community guidance on best practices for newsgathering, sourcing and fact-checking. Using input from Grasswire’s community, Joanne and Matthew will be putting together resources and tools to help users become better researchers and fact-checkers, and will be able to assist users in both aspects.</p><p>Second, we’ve completely redesigned both the process and the interface of Grasswire from the ground up. One of the challenges of our current system is that modifying Grasswire is a bit difficult: It is based on rules and processes that prevent the community from making mistakes, but inadvertently made simple tasks difficult to perform.</p><p>The next iteration will be very simple. Editing Grasswire will be as easy as clicking “Edit,” changing some text in a field, and clicking “Publish.” We’re stripping the process down to the essentials, and trusting the community to govern itself. Instead of making it difficult for a user to make mistakes, the next version of Grasswire will make it easy for anyone to correct them.</p><p>Simply put, the next version of Grasswire is going to be our biggest, boldest and best yet. And we can’t wait to show it to you.</p><p>- Austen, Levi and the Grasswire team</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d13bb647e48" width="1" height="1" alt=""><hr><p><a href="https://medium.com/grasswire-blog/grasswire-s-next-steps-6d13bb647e48">Grasswire’s Next Steps</a> was originally published in <a href="https://medium.com/grasswire-blog">Grasswire Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>