Spoonful



Howlin' Wolf

I'd Have to be Crazy



Willie!!

Deacon Blues




Steely Dan - Deacon Blues

I'll learn to work the saxophone
I'll play just what I feel
Drink Scotch whisky all night long
And die behind the wheel
They got a name for the winners in the world
I want a name when I lose
They call Alabama the Crimson Tide
Call me Deacon Blues


Eeyore really is cute

Well, this kinda catched the eye. From knownissues.blogspot.com

Some blogs are seeing a new post that says "eeyore is cute!"

We are identifying the cause of the problem and are working on a fix.



Heh.

Just poking around at blogs that seem to have the eeyore post a couple of things I spot in common. 1) All the ones I see are published via FTP and 2) Ones with the eeyore post also have many links that should be going to blogger.com going to urls like http://0.blogger_loadtest.server.blogger.gg.borg.google.com:9815. For things like openid server, email this post images, service post urls, etc. A url like that is an internal url for google corporate only. But the name of the particular server could be a clue.

So here's my guess. Either A)Group of Winnie the Pooh obsessed hackers are trying to bring down google or B) An internal load testing at Blogger somehow got some wires crossed that let their test post get published on some blogs.

I'll go with option B for now, but option A would be fun. Unknown option C or D might be fun too. We'll see what they say.

Eeyore is pretty cute too. But that goes without saying.

UPDATED

Aha. It was option B.

Update: During routine testing, a bug caused a small number of FTP blogs to publish a test post. No systems or accounts were hacked. We have corrected the original bug, and are working to remove the test data from the blogs.



Winnie the pooh hackers would have been fun.

Blogger, Robots.txt, Canonical URLs, Feeds - Let's get some Synergy

A little rant where I ask Blogger to make a slight change. The story begins...

Several months back, Blogger changed the way they did comments somewhat. Short version is they broke up post pages that receive many comments (200+). This is fine. In doing so, they also had to add some query parameters to comment permalinks so they could work with the new pagination. Again, nothing wrong with that.

But sometimes googlebot gets confused with a page having multiple urls. These are canonical issues. ( Admission - I have trouble both spelling and saying canonical, but I digress). This hit our favorite blog phydeaux3 when I noticed suddenly last December hits from Google had dropped off, to almost nothing. What I found when I started looking into it was it seemed Google was now suddenly grabbing tons of these comment permalink urls and giving them prominence over what should be the real url. Example.

Instead of having this url in the Google index
phydeaux3.blogspot.com/2006/09/code-for-beta-blogger-label-cloud.html
Which is the proper url, which has hundreds of links pointing at it, Google was indexing urls like this instead
phydeaux3.blogspot.com/2006/09/code-for-beta-blogger-label-
cloud.html?showComment=1221076440000

Which is just a link to a particular comment. But since that url doesn't having any links to it (as it shouldn't) it doesn't rise to the top of any searches like the real url would.

In a perfect world, Google usually knows which is the better url, and probably most of the time it does things correctly. But for whatever reason Google was mucking it up the same way on many of my posts that used to get search hits.

I should say here that ultimately I don't give a shit. Hell it took me a month to even notice as I'm not doing a lot of posting. I don't really care too much whether I get hits or not and I figure it will eventually work itself out. But it's a problem with such an easy solution.

Now my good pal, Notorious I.M.P, pointed out to me this recent post from Google Webmaster Central talking about a new feature that allows you to fix (supposedly) canonical issues like this by adding a "hint" to google with a <link> tag. Well that's fine. If'n it works.

If you wanted to try it for Blogger you would add something like this to the head of your template.

<b:if cond='data:blog.pageType == "item"'>
<link expr:href='data:blog.url' rel='canonical'/>
</b:if>


I've just tried that so I don't know if it actually works or not, but it outputs things the way the Webmasters Tools blog says to.

But for Blogger, we are really fighting a battle that could have a better solution. Only we users can't do it. It would have to be done at Blogger. A better solutions would be to add a few lines to the robots.txt file to take into account these canonical urls that the comment pagination changed caused. Blogger already blocks urls with "search" in the path which correctly blocks redundant label/search pages. But a few tweaks would help out also. Something along the lines of adding these two lines to the robots.txt

Disallow: /feeds/comments
Disallow: /*?showComment*


Now if I have that right (which I may not) that would 1) Block comments feeds from being indexed. That's where I believe the comment pagination links are being picked up from mainly, and besides comments feeds really don't need to be indexed do they? 2). Would block any urls with ?showComment in them which would block any of the comment permalinks if they got picked up somewhere else.

Or maybe there is a better way of doing it. Or they could do nothing. I'm just ranting.