‘F***. YOU. ALL. TO. HELL’: Google Lead Designer Implodes Over Kavanaugh — Ruthlessly Attacks Christians, Conservatives

There’s no doubt at this point that Silicon Valley doesn’t like conservatives. Facebook, Twitter, Google, they’ve all be thoroughly exposed for their consistent efforts to silence conservative points of view. Big tech wanted Hillary Clinton to win and they did everything they could to make that happen.

The Brett Kavanaugh situation provided us with yet another example of why we should be skeptical of powerful companies like Google.

Here’s how a high level employee at Google reacted.

From Conservative Tribune:

Does big tech have a political bias problem? Companies like Facebook and Google have sworn up and down that they’re apolitical … but a growing amount of evidence is raising hard questions about the corporate culture within these brands.

On Saturday, one of Google’s top people single-handedly brought those questions to the surface again. After Brett Kavanaugh was confirmed as the next Supreme Court justice, the tech company’s design lead went on a hateful rant on Twitter.

You really think a guy who is that unhinged is capable of going into work and not injecting politics into his job?

Unlikely.

Things have not been going well for Google. Just this week we found out they completely botched protecting the privacy of their users in a pretty embarrassing way.

From BBC:

Google is shutting down much of its social network, Google+, after user data was left exposed.

It said a bug in its software meant information that people believed was private had been accessible by third parties.

Google said up to 500,000 users had been affected.

According to a report in the Wall Street Journal, the company knew about the issue in March but did not disclose it.

The WSJ quoted an internal Google memo that said doing so would draw “immediate regulatory interest”.

In a statement, the firm said the issue was not serious enough to inform the public.

“Our Privacy and Data Protection Office reviewed this issue, looking at the type of data involved, whether we could accurately identify the users to inform, whether there was any evidence of misuse, and whether there were any actions a developer or user could take in response.

Not ideal.

LEAVE A REPLY

Please enter your comment!
Please enter your name here