Hey I know that there are some talent UI folks in this forum..so heres a nice chance for all yo peeps!! :)-

"...we're looking to hire some UI experts (both visual and interaction designers, as well as software engineers) to join the Blogger Team here at Google, and help us plan and build Blogger's next generation features. If you're interested, send an email to jobsblogger.com with your resumé, and which of the following job descriptions you're interested in:
# Visual Designer
# Interaction Designer
# User Interface Software Engineer"

http://www.google.com/support/jobs/bin/answer.py?answer=23885
http://www.google.com/support/jobs/bin/answer.py?answer=23690
http://www.google.com/support/jobs/bin/answer.py?answer=23744

..best of luck to all applicants!

A good chance.

New "Feature" (?):
http://help.blogger.com/bin/answer.py?answer=42442

stefan2904: That's not the new feature. (It's a little confusing though because the title is "What is a site feed?" but the content is for the "Recover post" feature.)

This is the new (albeit similar) feature:
http://buzz.blogger.com/2007/05/auto-savory-blogger-posting.html

And they've finally changed Ctrl+S so that it *saves* rather than *publishes*!

Ahm, my links has nearly the same content then yours. (except mine is help and yours is buzz).

help:
Blogger Help : How Blogger Autosaves Your Posts

buzz:
Blogger Buzz: Auto-savory Blogger Posting

(there was a js-popup in my blogger interface)

And they've finally changed Ctrl+S so that it *saves* rather than *publishes*!
> YOUHOUUUUUUUUUUUUUUuuuuuuu :-D

<< Ahm, my links has nearly the same content then yours. (except mine is help and yours is buzz). >>

Weird. That support article was totally different when I viewed it earlier! As I said, its title was "What is a site feed?" I guess they were in the middle of replacing their old "Recover Post" support article with the new one but I was hitting a different, out-of-date server...

Tony, you bring about a good point on how hard it is for Google to manage change propagation. (i.e "different, out-of-date server...")

E.g. , When Mission Critical information needs to be spawned across the network, Google biggest hurdle will be to ensure that all servers are in sync. I think the lesson here is that no matter how big you are , information dissemination across the network is always an issue, even if one controls the network!!