zlacker

>>benhur+(OP)
Is there really no way for a user to get in touch with a human agent? I read that Google automates the flagging and disabling of accounts but given how many people have their livelihood linked to these accounts, Google must have done something. It makes me scared how deep I have dived into the Google ecosystem. Time and time again I think about transitioning to someplace else but don’t know how to. It seems too daunting.

>>rochak+W1
Google only takes calls for ad sales and gsuite support as far as I know. Beyond that shaming them on social media is the only way to get their attention. I used to work for a top five web site and even we couldn’t get ahold of anyone - one day Google decided to start crawling us at a rate of 120k rps and it was killing the site by pulling ancient content that was 100% cache miss. No way for us to get in touch with Google officially, our billionaire CEO hadn’t traded numbers with their billionaire CEO so no help there, one of the developers had a college buddy that landed at Google and that guy was able to use some sort of internal mailing list to get them to drop the crawl rate down to 20k rps.

(Microsoft is just as bad - their sales people can’t be bothered to talk to anyone who isn’t a partner, but that worked out great for me, I wasn’t really feeling azure and it made a great excuse to not consider them. One of their sales people did leave me a VM three or four months later but we had already chosen another vendor by then).

>>zxcvbn+N5
I think returning http status code 429 (=too many requests) or 5xx should work. Google claims to respect it. And it's not like they have choice really: the server is refusing to provide the content. Additionally, serving such an error should be as cheap or cheaper than a cache hit.