henrybridge

Like I said on Quora, we use the location field that you put into the album when you uploaded it. The album location isn't displayed in the caption for individual photos and isn't displayed that prominently on the album page, so you're probably just not seeing that you set it when it was uploaded in 2009.

Disclosure: I work on location products at Facebook.

I think that real world places are an important part of who you are. Where you're from, where you've lived, and where you've travelled to, for instance, all help tell a story about you as a person.

The way that's represented on Facebook today is the Map on your Timeline. These suggestions help you put more photos on your map so you can share experiences with friends. That trip you took to Disney World 5 years ago may be far down in timeline, but it's going to be easy for friends to find it on your Map.

Hope that helps explain the "why" a bit.

Because Chrome has a multiprocess rendering architecture, and OS 10.5 doesn't provide a good path for hardware-accelerated rendering across processes. This means Chrome on 10.5 has to render each frame on the GPU, read it back to main memory as an image and then repaint it to the screen elsewhere. The bigger the window, the bigger the image and the longer this readback/copy takes.

ah, glad to hear it!

That is odd, I'm not sure. I know you said Beta channel, but what version number are you running? It needs to be >9.0 for WebGL to be on by default.

If you could file a bug at http://code.google.com/p/chromium/issues/list with the contents of your about:gpu page, we'll do our best to figure it out.

Are you running 10.5 or 10.6? Performance will be slow for large windows on 10.5