News for hackers. Stuff that matters.
Re:Why node.js disappoints me by pilif on Monday September 27, 2010 @11:25AM (#1731974)
Google parses and executes JavaScript already.

http://code.google.com/web/ajaxcrawling/docs/getting-started...

that's where that exclamation mark in the hash of the URL in recent sites comes from (like new twitter)

Edit:

Look at this query:

http://www.google.com/search?sourceid=chrome&ie=UTF-8...

it finds the existence of that word on my privacy page that gets only loaded via AJAX. So it must be able execute the javascript (sammy, basically) that intercepts these links to load the correct page fragment.

Edit:

Explanation is wrong. It takes a little bit of server side magic to work. See comment below. I completely forgot about this after implementing it in April :-)

Re:Why node.js disappoints me by simonw on Monday September 27, 2010 @11:41AM (#1732045)
Their Ajax crawling stuff doesn't work by executing JavaScript within their crawler. If you read the docs you linked to, they specify that this URL:

http://tempalias.com/#!/privacy

Gets converted by their crawler in to this:

http://tempalias.com/?_escaped_fragment_=/privacy

It's up to you to implement your server-side code such that ?_escaped_fragment_ causes an indexable version of your content to be served up.

Re:Why node.js disappoints me by pilif on Monday September 27, 2010 @11:48AM (#1732065)
Of course you are right. It has been a while since I've done this. Sorry for the confusion. I totally forgot that :-)