Tulsi Gabbard Sues Google

Today Tulsi Gabbard’s campaign sued Google for $50 million. Why? Because during the night of the first debate Google disabled her “advertising account” (I’m assuming she means adwords) preventing her from being able to purchase ads to direct searchers to her website. There’s also a paragraph in there that they’re “disproportionally putting her email into the spam folder.”

Image of a courthouse with scales of justice.

I read the complaint in the Gabbard suit (available from the NY Times). It’s kinda hard to read in a few places. The lawyers make statements that are clearly not factual (the First Amendment applies to Google advertising accounts) and others that are irrelevant (she’s a skilled surfer)

What I get from it is that Gabbard’s campaign was buying up lots of ads on Google the night of the first debate. Then their account was suspended. Google responses to the campaign as quoted in the complaint don’t look that suspicious to me. In fact, they tell me that Google saw some activity on their adwords account that was out of line with their history and so the account was suspended until someone could investigate. Google’s algorithms hate change and this isn’t surprising. Google had bland, meaningless boilerplates like most companies and the campaign didn’t like that.

The thing is, no where in this does she assert that Google delisted her website or did anything to change her organic search results. All she asserts is that they suspended her ability to buy advertising. If folks really were searching for Gabbard, surely they’d find her website, and her wikipedia article. They might not see any paid ads for her site, but I’m not sure why “not being able to buy advertising” is a first amendment issue.

She’s also asserting her email is being treated unfairly because it’s being filtered to the spam folder “more than other Democratic candidates.” What if the reason for that is she’s spamming more than other Democratic candidates? In any case, multiple laws protect the companies doing the filtering. As long as the filtering is being done in good faith, the companies are statutorily protected from legal liability. In fact, there are 2 decades of case and statutory law saying that mailbox providers have every right to filter or block mail as they see fit. I’ve detailed at least half a dozen cases here on the blog over the last few years – even going to courtrooms and watching the proceedings.

I am certainly not Google’s biggest fan, and find a lot of what they do problematic and intrusive. But in this case, I really can’t see what they’ve done wrong. Gabbard’s complaint boils down to Google inhibited her freedom of speech by prohibiting her from buying advertising on their during a specific 24 hour period (a lot of folks are saying her account was suspended for 6 hours, but I don’t know where that figure came from). I don’t really think the First Amendment grants us the right to buy advertising on a private ad network at a specific time.

Are there bigger issues with large social media companies and how they impact speech and our ability to communicate? Yes. Absolutely. There are significant issues with how they manage speech and what they allow. I’m not sure that Google is a social media company, though. Google is a data collection and advertising platform. The one bit of the company that might be a platform for speech (Google+) was shut down a while ago. Requiring Google to carry your ads is like insisting that the local newspaper publish your letter to the editor.

I don’t see this going very far. I’ve watched Google’s lawyers in action against someone expecting Google to change their filtering. I expect we’ll see a motion to dismiss on the basis of no valid claim. Google isn’t a public forum, nor a state actor; the internet is not public property. The judge may give the campaign an opportunity to rewrite the complaint, but unless they get better lawyers it’s going no where.

Related Posts

Google makes connections

One of the client projects I’m working on includes doing a lot of research on MXs, including some classification work. Part of the work involves identifying the company running the MX. Many of the times this is obvious; mail.protection.outlook.com is office365, for instance.

There are other cases where the connection between the MX and the host company is not as obvious. That’s where google comes into play. Take the domain canit.ca, it’s a MX for quite a few domains in this data set. Step one is to visit the website, but there’s no website there. Step 2 is drop the domain into google, who tells me it’s Roaring Penguin software.
In some cases, though, the domain wasn’t as obvious as the Roaring Penguin link. In those cases, Google would present me with seemingly irrelevant hosting pages. It didn’t make sense until I started digging through hosting documentation. Inevitably, whenever Google gave me results that didn’t make sense, they were right. The links were often buried in knowledge base pages telling users how to configure their setup and mentioning the domain I was searching for.
The interesting piece was that often it was the top level domain, not the support pages, that Google presented to me. I had to go find the actual pages. Based on that bit of research, it appears that Google has a comprehensive map of what domains are related to each other.
This is something we see in their handling of email as well. Gmail regularly makes connections between domains that senders don’t expect. I’ve been speaking for a while about how Gmail does this, based on observation of filtering behavior. Working through multiple searches looking at domain names was the first time I saw evidence of the connections I suspected. Gmail is able to connect seemingly disparate hostnames and relate them to one another.
For senders, it means that using different domains in an attempt to isolate different mainstreams doesn’t work. Gmail understands that domainA in acquisition mail is also the same as domainB in opt-in mail is the same as domainC in transactional mail. Companies can develop a reputation at Google which affects all email, not just a particular mail stream. This makes it harder for senders to compartmentalize their sends and requires compliance throughout the organization.
Acquisition programs do hurt all mail programs, at least at Gmail.
 

Read More

Tell us about how you use Gmail Postmaster Tools

One of the things I hear frequently is that folks really want access to Google Postmaster Tools through an API. I’ve also heard some suggestions that we should start a petition. I thought a better idea was to put together a survey showing how people are using GPT and how high the demand is for an API.
They’re a data company, let’s give them data.

I’ve put together a survey looking at how people are using GPT. It’s 4 pages and average time to take the survey is around 7 minutes. Please give us your feedback on GPT usage.
I’m planning on leaving the survey open through the first week in November. Then I’ll pull data together and share here and with Google.

Read More

Google Postmaster Tools

Earlier this month Google announced a new set of tools for senders at their Postmaster Tools site. To get into the site you need to login to Google, but they also have a handy support page that doesn’t require a login for folks who want to see what the page is about.
We did register, but don’t send enough mail to get any data back from Google. However, the nice folks at SendGrid were kind enough to share their experiences with me and show me what the site looked like with real data, when I spoke at their recent customer meeting.
Who can register?
Anyone can register for Google Postmaster tools. All you need is the domain authenticated by DKIM (the d= value) or by SPF (the Return Path value).
Who can see data?
Google is only sharing data with trusted domains and only if a minimum volume is sent from those domains. They don’t describe what a trusted domain is, but I expect the criteria include a domain with some history (no brand new domains) and a reasonable track record (some or all of the mail is good).
For ESPs who want to monitor all the mail they send, every mail needs to be signed with a common d= domain. Individual customers that want their own d= can do so. These customers can register for their own access to just their mail.
ESPs that want to do this need to sign with the common key first, and then with the customer’s more selective key.
How does it work?
Google collects data from DKIM and/or SPF authenticated mail, aggregates it and presents it to a Google user that has authenticated the domain.
How do I authenticate?

Read More