It’s been about a month since all 14 of our former network blogs, Urban Semiotic, Go Inside, Boles Blues, Panopticonic, Carceral Nation, Boles University Blog, 10txt, RelationShaping, United Stage, WordPunk, Memeingful, Scientific Aesthetic, Dramatic Medicine and Celebrity Semiotic became this Boles Blog. In that brief time, we’ve published over 80 new articles. That’s a World Publishing Record for any of our single blogs.
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
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 taught, early on in our lives, to be cautious and to watch our backs and to look out for each other. We obediently lock our doors. We psychologically brand our children. We learn to buckle up. We are a nation of Safety First. Are you as safe in securing your online life?
The Rev. Al Sharpton wants Don Imus fired for Racist remarks Imus made on-the-air last week about the Rutgers University women’s basketball team.
I agree with Al Sharpton even though I have written positively about Imus here in the past.
Sometimes there are things spoken that are so inconsiderate and so hurtful that no apology and no excuse can ever erase the psychological and physical damage done.
Imus, and his show Imus in the Morning, allegedly have a well-documented history of Racism and intolerance and he needs to immediately and permanently leave the airwaves:
Continue reading → Don Imus and the Rutgers Nappy Headed Hos
The problem with unrestricted community involvement in online research is the great risk to truth and accuracy in the reporting. If one community member cannot be trusted, then the entire veracity of the rest of the community — guilty or not — is also placed under the microscopic and burning Panopticonic eye of doubt and disingenuousness.
Continue reading → The Deadly Danger of Wikipedia and Corrupt Community Research
Are we are minds?
Or are we our bodies?
We cannot be both because our bodies are limited and our minds are endless.
How we deal with that mind/body disconnect is the biggest conflict of our existence but, sadly, many of us never realize that struggle or recognize our need to confront the mortal and the immortal within us.
You must be logged in to post a comment.