By: Kyle James | 10-02-2017 | News
Photo credit: Leslie Banks | Dreamstime

Wrong Name Of Vegas Shooter Circulated By Google News Came From 4Chan

In an out of character move, Google News used the imageboard site 4chan as a news source early Monday morning. Google News used a post on 4chan as a source and reported the wrong name of the Las Vegas shooter. The wrong name was first appearing on 4chan's "pol" board which is known for inflammatory content.

<blockquote class="twitter-tweet" data-lang="en"><p lang="en" dir="ltr">This email from Google I just got is insane. They talk about 4Chan as if it is a news source. Third bullet point: <a href=""></a></p>&mdash; William Turton (@WilliamTurton) <a href="">October 2, 2017</a></blockquote>

<script async src="//" charset="utf-8"></script>

The name was initially dug up by 4chan users investigating people connected with names first released by Las Vegas investigators. One of those people mentioned by Las Vegas police was a sibling of a person of interest and later cleared of wrongdoing by Vegas police. Other left-leaning news sites quickly picked up on the wrong name of the shooter as well calling the person in question a "far-left loon."

Gateway Pundit has since removed the article after spreading the false name in an article of their own. In an email from a Google employee, Google explained how the misinformation made it's way into Google News. The statement says "When the fresh 4chan story broke, it triggered Top Stories, which unfortunately led to this inaccurate result. We use a number of signals to determine the ranking of results—this includes both the authoritativeness of a site as well as how fresh it is." The statement went on to say, "We're constantly working to improve the balance and, in this case, did not get it right."

<blockquote class="twitter-tweet" data-lang="en"><p lang="en" dir="ltr">Facebook spox to me on site&#39;s listing of a Gateway Pundit story earlier on Crisis Response page <a href=""></a></p>&mdash; Oliver Darcy (@oliverdarcy) <a href="">October 2, 2017</a></blockquote>

<script async src="//" charset="utf-8"></script>

Facebook also reported on the false name but quickly removed it once the error was caught. A representative from Facebook said "We are working to fix the issue that allowed this to happen."

<i>On Twitter:</i>

<a href="">@ErvinProduction</a>

Tips? Info? Send me a message!


Share this article
Thoughts on the above story? Comment below!
0 comment/s
What do you think about this article?
Comment *

Recent News

Popular Stories