News for hackers. Stuff that matters.
Re:Breaking the web with hash-bangs by sunchild on Wednesday February 09, 2011 @04:22AM (#2196908)
The author also completely misses the business case: putting a single gateway through which Google can index makes sense for huge content generators. Sites like Twitter actually have some leverage with Google, as the Twitter firehose is more "real time" than Google's index. Using the #! allows Twitter tight control over Google's access to content. As for Gawker, I suspect they overestimate their leverage with Google, and have no similar business case.
Re:Breaking the web with hash-bangs by Isofarro on Wednesday February 09, 2011 @04:42AM (#2196937)
"The author also completely misses the business case: putting a single gateway through which Google can index makes sense for huge content generators."

That's called a domain name. www.lifehacker.com is a single gateway to all of lifehacker's blog posts. Then you use the path part of the URL to specify which post or collection of posts you want.

Twitter hasn't leveraged anything. The tweet URLs without the hash-bangs were more accessible to Google.

You want tight-control as to which user-agents can see which set of tweets - that's what the Controller is for on the server.

Re:Breaking the web with hash-bangs by ceejayoz on Wednesday February 09, 2011 @10:36AM (#2197720)
sitemap.xml and robots.txt offer much, much more control over Google's crawling, and require essentially no dev work.
Re:Breaking the web with hash-bangs by sunchild on Friday February 11, 2011 @09:14AM (#2206353)
And can be ignored...
Re:Breaking the web with hash-bangs by ceejayoz on Friday February 11, 2011 @08:06PM (#2208902)
The hashbang technique could be easily worked around by a company with the resources of Google, and the PR ramifications of GoogleBot violating robots.txt would be pretty big.