If you're interested in Blogger template hacking-via-javascript, be sure to check out Google's AJAX Search API. While its home on Code contains a bunch of interesting sample apps for learning and tinkering, Google Engineer Mark Lucovsky recently published an ajaxy, bloggy playground on BlogSpot: http://ajaxsearch.blogspot.com/

Notable stuff:

• the sidebar's "Google Search" field searches multiple indexes (Web and BlogSearch), as well as individual sites (in this case the AJAX Search API blog, the Google blog and www.blogger.com) - you can customize all of these things
  
• the sidebar's "Video Search" field displays (and plays!) results inline
• links in the main blog section can dynamically link directly into the sidebar's embedded Map and Video boxes (try clicking the 'Sakana' and 'Jimi Hendrix' links)

Mark's post on the API's blog has further details about the tweaks and integrations.

If you whip up something nifty on your Blogger blog using the AJAX Search API, post about it and link to this post, so we can see it in the Backlinks. Thanks!

Update:

• Hoctro's Place has applied the above to Blogger beta - nice work!
• Hoctro also has a Blogger Beta Playground, so be sure to check out some of his neat hacks.
  
• Zizukabi has an AJAX Search Widget in his sidebar, though I don't read Korean so I'm not 100% sure about what he's saying. :)
• Mark Lucovsky posted a beta blog with the same functionality.
  

Update #2:

• Mark posted another AJAX Search API example, the Video Bar.
  

Do you remember the Blogger Mobile jingle? I am happy to report that we have added “the rest” to the new version of Blogger in beta.

If you have a mobile blog already, we’ll now let you switch over to the beta (if you meet the other criteria, that is). Then just keep sending your pictures and messages to go@blogger.com, and we’ll post them for you.

Already using the new Blogger? You can create a new mobile blog simply by sending an e-mail or MMS from your phone to go@alpha.blogger.com. The “alpha” tells us to create the blog on the new version of Blogger.

In this same release we’ve fixed some feed related things as well: comment feeds are now showing the latest comments, and pagination works, which solves this known issue. Also, feed URLs on the beta are now also served up from your blog’s domain in addition to from beta.blogger.com.

(just linking to a few notable blogs that crossed my path in the past few days)

1. The Boing Boing crew just launched a new blog on Blogger beta - the Boing Boing Digital Emporium:

"The four of us at Boing Boing love music, comics, videos, and books. We especially love them in digital format so we can store them on capacious hard drives, instead of cramming more things into our already overstuffed bookcases. And we super-extra especially love them to be DRM-free so we can read, watch, and listen to them on our MP3 players, on our handheld devices, on our computers, and in our cars."

"That's why we created the Boing Boing Digital Emporium, launching today. We'll be selling our favorite DRM-free digital goods and giving the the majority of the proceeds (minus the transaction charges imposed by Paypal and Payloadz) to the creators of those goods."

2. Blogger-powered news from Thailand is available from Bangkok Pundit and 19sep.

Ahoy sailors. The infamous pirate Edward Teach once wrote in his ship’s log (or “p’slog” in 18th century slang):

Such a day found one with a great deal of liquor on board, so kept the company hot, damned hot; then all things went well again [cite]

Yar. Now, had Teach written this on a blog, his crew may have wanted to comment on it (“Pass me th’ bottle,” “when can we go back to Port Royal?,” “why’s the rum gone?,” &c.). Until today, they may have had a great deal of trouble, above and beyond the significant scarcity of reliable Internet access in 1718 colonial America. A pair of issues have plagued Blogger and the Blogger beta: Blogger users unable to comment on beta blogs, and beta users unable to comment on Blogger blogs.

For the benefit of time traveling pirates with hypothetical weblogs everywhere, these issues have been well and truly keelhauled. Get thee to commenting, w’ abandon!

I’m very pleased to announce that Flickr has added support for the new version of Blogger in beta! Now you can blog and post photos directly from Flickr to your beta blog. This is something that a ton of you have been requesting, and many thanks go to the Flickr folks for upgrading their site to work with the new version of Blogger. (The relevant known issue has been updated, if you’re keeping track.)

Flickr is using a secure authentication method made possible by the new Blogger’s use of Google Accounts. When you want to add a Blogger beta blog to Flickr, Flickr will redirect you to google.com to enter your username and password. Read more about granting access to websites.


Flickr (and other websites that support this technology) will never see your username or password; all of that information is kept securely on Google’s servers. In addition, these websites will only be authorized to post to your Blogger blog. They will not be allowed to access your seach history (if you save it, that is), your Gmail, your Google Checkout data, or any other part of your Google Account. If you ever want to deauthorize a website and disallow it from posting, you can revoke its access from your “My Account” page.

Remember, never enter your Google Account login information on a website not owned by Google!

In the past month we’ve made a number of changes to image uploading to detect and solve the problems that some folks have been having. The number of problem reports concerning image uploading have decreased substantially, so we know that we’re moving in the right direction. There are still some problems out there, however, and we’re committed to tracking them down and solving them.

To that end, we’ve just released an additional change on the Blogger beta site to show you thumbnails of your photos after you upload them:

We hope that this thumbnail feature will help us diagnose the remaining issues, in particular those where no error message pops up. If you still have image upload problems on the beta please report them to us so we can get them solved. Don’t forget to mention in your description whether or not you see the thumbnails!

One more thing: to get all the latest fixes make sure that you clear your browser cache.

I know it may sound cheesy for some frustrated bloggers but, happy photoblogging!

Some of our users have expressed concerns about the lack of up-to-date information on issues and bugs they’re seeing in the new version of Blogger in beta. What are the engineers aware of? What’s being worked on? And when have bugs been fixed? We’re addressing these questions with today’s launch of Known Issues for Blogger in Beta, a new blog that will contain fresh information about the status of issues and bugs that affect you.

While I am on the subject of communication, let me clarify the purpose of the various other communication channels that exist between the users and the Blogger Team:

• Support form: Users can report problems with the application here to the Blogger support team. Depending on the issue the support team will answer with either some pointers to self-help information, ask for more information, or — in case of a new issue — report it to engineers for resolution. Issues that affect a large group of users will be resolved promptly (meaning that an engineer will start to work on it right away) whereas problems that just apply a single blog or account may take a little longer to fix.
  
• Blogger Status: This venue is used by the Blogger Team to report production outages, such as database problems. This is not a place where we report known application issues.
• Blogger Buzz: This blog contains information about new product features on Blogger as well as posts about cool and interesting things that go on the blogosphere.
• Blogger Help Group: Here Blogger users help each other with gotchas, tricks, hacks, etc. The Blogger support and engineering teams monitor this forum and occasionaly post on issues of general interest, but it is not the goal of the Help Group to become an alternative to the Support form.

I hope this note helps to clarify at which site/blog to seek help in various situations. And many thanks to the good folks on the Blogger Help Group for their feedback, which helps us provide a better service for all users.

Many of us in the USA are celebrating Labor Day today, which marks the end of the summer and is generally a good opportunity to have a backyard barbecue. The Blogger team decided to celebrate Labor Day by doing some actual labor and fixed a couple of issues with the beta:

• users seeing error pages instead of their beta blogs will not see these errors anymore
• old-style archive links for migrated blogs work again, in addition to the new-style links
  

Thanks for helping us continue to improve the Blogger beta!

In his landmark book The Design of Everyday Things, Donald Norman writes:

The human mind is exquisitely tailored to make sense of the world. Give it the slightest clue and off it goes, providing explanation, rationalization, understanding. … Well-designed objects are easy to interpret and understand. They contain visible clues to their operation. Poorly designed objects can be difficult or frustrating to use. They provide no clues–or sometimes false clues. They trap the user and thwart the normal process of interpretation and understanding.

With that, we say good-bye to the combined Blogger / Google Accounts sign-in box on our homepage. Functional? Quite (though not everyone believes me). Well-designed? Not a chance. We’ve listened to the problems with our combined login box, and we have a solution.

The new login choice on the homepage should relieve any Google Accounts–related login trouble you may have. And if you’re like me and still haven’t been able to switch to the beta, you’ll be happy to find that your password manager will stop trying to fill in your Google Account login information on Blogger.

Sincere apologies to everyone who was a victim of our bad design and had trouble or even couldn’t log in. We goofed on this one, and we’re sorry.