There’s indisputable evidence that a grassroots Trump supporter is responsible for Google having to rewrite their code to correct anti-Trump bias, and there’s a decent chance that same Trump supporter is responsible for Google’s CEO sending a memo to the entire staff telling them not to let their anti-Trump bias affect their work.
And you’re currently at that grassroots Trump supporter’s website.
This will be a process article devoid of all the juicy details, so if you want to know the specifics, you’ll have to refer back to the pieces linked throughout. (Most notably, the final piece linked at the bottom in the “RELATED” section.)
February 22, 2018: I write a piece providing concrete evidence that Google’s anti-Trump bias does make its way into their products.
I share it with every conservative media heavy hitter I can think of.
September 12, 2018: A video is leaked that shows Google leadership basically crying over the results of the 2016 election. In response, Google releases a statement claiming emphatically that their employees’ political views do not affect their code or products.
Naturally, at that point, I’m compelled to re-up the evidence I found 7 months earlier that proved Google’s statement was a lie; that their anti-Trump bias does make its way into the code.
September 13, 2018: I write that piece. And Mollie Hemingway tweets it out, and the good people at WhatFinger place it prominently at the top of their center column. But other than that, the piece is largely ignored. I shared with every heavy hitter in conservative media I could think of, but all of them ignored it and never bothered to help shed some sunlight on the hard evidence of anti-Trump bias embedded in Google’s code.
Sometime between September 13 and September 21, 2018: After more than 20 months of letting the partisan code fester (since January 20, 2017), Google within days of my piece being published quietly rewrites the code to conceal that the bias was ever there. They make no public statement, or acknowledge in any way that the flagrantly anti-Trump bias was ever deliberately programmed into their products. Also at some point during this time, Google’s CEO releases a memo to all staff about not letting their [anti-Trump] bias affect Google’s products.
September 21, 2018: I realize what happened, and write another piece. In it I lament that we had Google on the ropes but, thanks to the inaction of elitist conservative media, we never did anything with it. And Google was able to quietly change the code without ever enduring the public scrutiny or forensic accountability the strong evidence merited.
September 22, 2018 (today): I learn about the internal memo Google’s CEO sent to staff. A memo that went out around the same time they were fixing the code that I exposed as having been guided by their employees’ anti-Trump bias. I put it all together, and lay out the timeline you see above.
THE FALLOUT (OR LACK THEREOF)
And it all feels like kind of a big deal to me. Like I exposed, contrary to Google’s claims, that their employees’ anti-Trump bias does make its way into their products. And that because of what I found and Mollie Hemingway and the people at WhatFinger helped expose, Google had to fix the code as quietly as possible while also sending a memo to all staff instructing them to cease any work that incorporates their hatred for the duly-elected, sitting US President.
But it’s still extremely unfortunate that it happened so quietly. Because this was a pretty big deal and it merited some sunlight. To repeat the analogy I used in yesterday’s piece: We were basically accusing Google of robbing banks. But they said, “No, no. Not us. We never steal anything.” Then I caught them shoplifting gum. And that matters. If you think someone is robbing banks, and they say they never steal anything, and you catch them stealing gum…that matters. And I asked the conservative media big dogs to help get the word out. And none of them could be bothered because they’re all too busy congratulating each other for — nobody really knows anymore. And now, because readers like you never got a chance to go test the evidence for yourselves, and that evidence is basically gone now, Google gets to say — sticking with the bank robber analogy — that the video I have of them stealing gum is just a case of mistaken identity. The opportunity for millions of Google users to all go do the simple test and see for themselves, is gone.
Still, the fact appears to remain: I, a nobody writer who doesn’t advertise and works a regular joe day job like most of you, just forced Google to rewrite their code, and lecture their employees about not letting their bias interfere with Google’s products.
And while that’s a big deal to me personally, it’s entirely invisible to the rest of the world. And the worst part, because it’s entirely invisible to the rest of the world, is that until/unless someone finds more concrete evidence of Google employees’ anti-Trump bias making its way into their code, Google remains bulletproof in their denials that it ever happens.
VIDEO ONE: Taken on September 12, 2018, this video shows that Google programmers ensured the “p” would be capitalized for every President except for President Trump.
VIDEO TWO: Taken just 9 days later on September 21, 2018, this video shows that Google programmers corrected the code to remove their personal hatred of President Trump. It came up “president Trump” for all 20 months of President Trump’s time in office, but within days of my piece they fixed it. And that’s great. But now they have a lot of questions to answer about how it happened, why we should believe it’s not happening elsewhere, and what steps they’re taking to prevent it.
Make sure to check out WhatFinger News for all the best right-minded media content from around the web.