1script - 5:39 pm on Aug 23, 2013 (gmt 0)
@FranticFish: the more I'm thinking about it, the more I am leaning towards a hybrid approach. I didn't want to call it infinite scrolling because I despise the actual truly infinite scrolling myself. Lazy loading 10-20 items of content may be fine, and even useful on mobile phones, but if it really never ends, it becomes very hard to navigate and you can never go back and find anything anymore. And don't even get me started on Flickr implementation of lazy loading huge pictures that simply crushes my browser!
So, I am thinking I will end up still using pagination to split content into larger but still manageable chunks but will lazy-load those to real users in 1/20th increments. This is a mobile-first type of site, I just want to be polite to people that pay for bandwidth.
So, I think good old cloaking per se may not be required but if the ?_escaped_fragment_= mechanism works reliably, I would use it to serve bots the entire page, already assembled server-side.
Now if I could only get a word back from Bing about whether they support it!