Jon Rafman has a fascinating web project that puts a real eyeball on Google’s mapping of our private lives in the public streets by providing, as a subset of his collection — what appear to be hookers — working from curbs around the world. The overall project is called — “Google Street Views” — and I was particularly fascinated by the amount of possible “hookers” recorded by Google in Jon’s folio. Let’s take a look at some of the street captures and see what you think.
There’s nothing quite as harrowing as having anything Google go toes up — because there is no clear path to getting a hassle-free technical support experience even if you pay your way as a Google Apps Premier Customer and even if you write the first Google Apps Administrator Guide book to market. I have a long history of writing technical books and providing online technical support and, without question, Google are the absolute worst problem solvers when it comes to the individual incident and fixing the outlier and resolving the uncommon anomaly. We won’t get into how generally awful Blogger tech support is today — we’ll just stay focused on Google Apps Premier for now.
Continue reading → Poor Google Apps Premier Support and Missing Google Search Returns
I have a lot of amps and I am always curious to see which amp heads and which combo amps will come with a cover or padded case included with the purchase. I always wonder if an amp comes with the cover if that means the amp is more prone to breaking or is it just a scheme to makes us feel better about paying a higher price?
UPDATE #2: September 6, 2010
At noontime Eastern, I heard from Naoko again and she confirmed robots.txt has been upgraded site-wide on WordPress.com!
I had to change the privacy settings on all my blogs — and then back again to “public” — to force the new robots.txt file to update. The plan worked.
All 13 public blogs are now set and updated and ready for Google and the rest of the indexed search world to remove our proprietary Movable Type search results.
Here’s a screenshot of the new robots.txt file disallowing the “/cgi-bin/” directory. I highlighted the new addition:
Yay, WordPress.com!
THANK YOU from prying us from the rock!
UPDATE:
The moment I published this article today at 12:24pm Easter time, I followed up with WordPress.com support and gave them the link to this article in an attempt to better explain — with screenshots — the problem I was trying to solve.
At 2:12pm — less than two hours after I wrote to WordPress.com — Naoko replied:
Hi there,
I was waiting for this to actually go live, but a change has been made in our code.
User-agent: *
Disallow: /cgi-bin/Will be added to robots.txt (not visible yet, I need to check back with the developer).
Fantastic news! That solves my proprietary Movable type search results problem across all 13 of my public WordPress.com blogs! Here is my reply:
Hi Naoko!
Oh, that’s great news! Is this change on a per-blog basis, or is it site wide?
If it’s side wide, are there plans to include robots.txt proprietary search disallows for the other blogging services?
I will update my article to reflect the information you provide.
Thanks!
Best,
db
I will keep you updated!
I don’t see the “/cgi-bin/” disallow yet on any of my blogs in robots.txt, but the moment it goes live, I will go back to Webmaster Tools and specifically ask that the “/cgi-bin/” directory be removed now and forever from all my blogs.
As well, because of this robots.txt disallow addition, I will now be able to effectively venture into Yahoo! and Bing to see if I can get the same directory deleted in those services for all my blogs.
Thank you WordPress.com Gods!
ORIGINAL ARTICLE:
I recently discovered a terrible Movable Type artifact that still remains festering and alive within me — via Google Search Returns — six months after I became a Six Apart refugee and gave up my expensive, self-hosted, standalone, blog hosting and returned to my first blogging home: WordPress.com. You can see an example of the problem below in the third search return in the screenshot. That “Memeingful: Search Results” link takes you to a proprietary Movable Type search return that has been dead for six months. Click on that link, and you’ll be taken to a “Not Found” error page on WordPress.com.
Continue reading → Dead Search Returns: Caught Between a WordPress.com Rock and a Google Hard Place
We are too well aware that much of Twitter’s content is comprised of Blogging the Bodily Fluids Stream — and we know how useless it can be. Twitter also can be useful when used properly. I am here to tell you that Kickbee is here and is number one in uselessness. When I tried to visit the Kickbee website, I was met with this warning from Google:
Google bleated its own horn last week concerning a new “YouTube Ready” captioning initiative. Our sad question is: “What took you so long?”
A while ago, I did a Google search for “ass burger” — and while I can’t remember the why or wherefore, I do remember grabbing this screenshot of the event so we could discuss this later — meaning now. I wonder how “Asperger” feels being included in a Google search return for “ass burger?” Is this search return an example of “searching by sound” and not by rational context? I can’t imagine “ass burger” is a common misspelling for “Asperger.”
Continue reading → Reverse Contextual Aural Discrimination: Did You Mean Ass Burger or Asperger?
You must be logged in to post a comment.