Slashdot Mirror
Where Do You Go When Google Locks You Out?
Lobais sends in the cautionary tale of a man who was locked out of Google Groups for three years — losing the ability to administer his own open source project in the process. "After about a year of using Google Groups for the PyChess project, I started [noticing] a problem. When I wrote mails to the list, no one would answer. And when I answered other peoples' post[s], they seamed to ignore them and press for new answers. As I tried to check the online group to see what was happening, I got a 403 Forbidden error. After a short while I realized that this error was given for any page on the groups.google.com subdomain. The lockout meant that I was unable to manage the PyChess mailing list. I was unable to fight increasing spam level, and more importantly I couldn't reply to anybody in my community. I wasn't even able to visit the Google help forums, which are all on groups.google.com. As the services are free of charge, I never really expected any support options. ... How can we know how often this kind of thing happens? If any admin can lock you out by a sloppy click, and give you no option to defend yourself, then it is bound to happen once in a while."
Several years back I had built up quite a large following on a Yahoo group. At one point the group had over 600 members, not bad. I did some posts on other groups on related subjects. Maybe one of them complained. Anyway, one fine day Yahoo refused to let me login. All attempts to contact the company were fruitless. I found that not only my account but also the entire group was nuked. Fortunately I had a backup of the registration emails. I shelled out some bucks for a server, emailed all my group members with the new group address, and never looked back.
om namo bhagavate vasudevaya
A few months ago I needed to contact Google UK over an unpaid fee for their use of a photograph. Even though they have an office with staff, they have made every effort to be invisible and uncontactable. If you do get hold of the office number, and call it, you are given a myriad of options. If you work your way through each option, they _all_ ultimately tell you to go to the Google web site and send an e-mail. There is no possible way to get put through to a human in any department. Google do not like talking to people.
ps. To add to your comment about poor support for Android: There are several critical errors in Google's sample code provided to Android developers. The errors have been pointed out, and fixes supplied, by kind-hearted developers who wanted to help others. Yet it is apparently too much effort for Google to update the sample code, meaning that every new developer coming to Android must struggle with the same problems.
How's charging a reasonably low price for a phone call or two to resolve the issue with a support person who is knowledgeable as well as able to effect change? Say, charge someone's card $10 and then initiate the support call, and if they are found out to have been an erroneous ban, refund the $10. Keeps the spammers from appealing in a massive manner, while allowing the one-off mistakes relief.
What you're saying is very interesting, but in contradiction to my experience with GoogleBot's behavoiur.
I've seen GoogleBot-images do a normal crawl of the images on the site, respecting robots.txt and all, and then, start a crawl over the images it was explicitly forbidden from indexing, from the same IP (*definitely* a Google IP, not an impostor), just with the User-Agent header changed to an empty string. Nice, eh? It was way too fast and way too cordinated to be triggered by human action. And if there was actually a human involved in telling the bot to return to the site, *ahem*, "incognito" a few seconds later, I'd be more than happy to tell them to bugger off properly when they're told to.
This is Slashdot. Common sense is futile. You will be modded down.