GoogleGuy MIA

Posted on March 23rd, 2005
by Site Admin in SEO



It seems all the fiasco over the 302 hijacking caught the attention of GoogleGuy who posted over at slashdot. Many of us have noticed a decidedly different change in GoogleGuys tone recently and Nick at threadwatch lays it all on the table:

This is not the IP we normally associate with the usually friendly and courtious GoogleGuy.

Im a little fed up with this. If Google wish to talk to TW then please use a real name or one nickname per person like everyone else.

I’ve been wondering at the change of style and attitude and have received many, many complaints about it - that now comes to an end.

The person who posts under that nickname usually is welcome here, as are any Google employee - but now i think we need to know who you are, no more silly games and jeckel and hyde personalities.

Im talking to the Google employee who normally posts under the GG nickname now, and trying to come to some terms on this.

We’ll see how that goes, then decide how to deal with it.

Thanks.

and follows up with this:

Whoever is posting under GoogleGuy here, has had posting rights turned off. We dont play those kind of games period.

Im talking to the normal GG and really hope to work something out with them about how Google can continue to communicate with TW and other places without the “multiple personality” promblem.

It’s a bit sad to have to do, but then unlike some other places, i value this place and it’s members far too highly to have anyone, even a google rep(s) cause trouble - on purpose or unintentionally.

Multiple personalities under the same nick, of a mega-corp we all have an interest in causes more trouble than it’s worth (and i might add that that trouble is reflected directly on Google more than it is here…) so untill we sort this out dont expect a GG answer to questions..

I suspect somebody’s gonna catch a beating at the Googleplex today …

technorati tag:

Popularity: 1% [?]

Sphere: Related Content

Text Link Ads


Comments are closed.

ss_blog_claim=11d9e7755a5f0384ef8a8ef01b9a7c1f