Blogger Developer Group

1. We will continue to support the Blogger API 1.0. (Technically, we are supporting it for the first time—as in, taking off the disclaimers and making sure it is up and running more reliably.) In fact, we have written a new implementation of it, along with the new, more robust, Blogger codebase. However, that spec is frozen and will not be developed further.
2. We will not be implementing or supporting the Blogger API 2.0.We apologize for having that out there in a semi-final looking spec for so long. We know it was frustrating for developers. But please forget that ever happened.
3. We are moving away from XML-RPC. If you choose to take advantage of the capabilities of the new API, you will need to use SOAP instead of XML-RPC. This was a difficult decision (made collectively by the designers of Atom), because there is a lot of investment in XML-RPC in the blogging tool space, and it is great for getting things done quickly. But we felt the technical advantages offered by SOAP were worth the effort. (See SixApart link below for details.)
4. The syndication format and API format will be unified. This is one of the nice aspects of Atom that could not have been easily accomplished without starting from scratch. It generally simplifies getting data into and out of blogging apps.
5. Interoperability. This is a biggie. At least two other major blogging tool and service companies (SixApart and Live Journal) have pledged their support for this new initiative, and we're working with them (as well as others) to define the spec up-front. This means your tools will be usable by as many people as possible, with minimal effort. And since the API/format will be vendor-neutral, no one's needs can be more important than users and developers.

• Jason Goldman : http://www.goldtoe.net/atom.xml
• Steve Jenson : http://www.saladwithsteve.com/atom.xml
• Jason Shellen : http://www.shellen.com/atom.xml
• Evan Wiliams : http://www.evhead.com/atom.xml

• support for titles
• tighter integration with the
  syndication format and editing tools
• extensibility
• easy-to-use WSDL file to work with most SOAP toolkits
• higher security authentication using WSSE
• more robust Blogger endpoint
• support for SOAP and REST

"MarsEdit doesn’t yet support titles for Blogger."

"It will—but it requires implementing the Atom weblog editing API first. This is MarsEdit’s top priority."

"This is the technical document that explains how we use Atom to post multimedia content online. Use this document to figure out how to adapt your servers to use Lifeblog 1.5."

We're very happy to be launching code.google.com today. To begin, we're releasing some developer-oriented libraries and tools. Google developers use these every day to make their programs easier to debug, faster, and more reliable. A number of engineers have used their 20% time to ready these tools for release, and will also help build the communities we hope will form around them.

We're also featuring links to all current Google APIs. Come check them out and if you'd like more information, please join our group, subscribe to our feeds, or if you're shy, email us directly. And happy coding!

"We are very excited to offer this service and Blogger is the first blogging site which we are supporting directly using an API... We are anticipating for it to be well received due to it's uniqueness and simplicity."

"A while back I realized that I really wanted to use Radio to be able to post to some of my blogs that are hosted at Blogger.com and Blogspot.com..."

"So this is it ... the new and improved RadioAtomBridge Tool ... a derivative of the xManilaBloggerBridge Tool which was a derivative of the ManilaBloggerBridge Tool. I'm giving all of this code to Userland to incorporate this into a future version of Radio."

"AwAPI uses a straightforward web-based protocol to receive requests and return data. Known as REST, it allows anyone to request feed traffic data using URLs submitted via HTTP. The data is returned as plain text XML which can be repurposed, transformed, and displayed by applications that you build. Using XML as the output format means testing and exploring AwAPI is as simple as composing an AwAPI URL and then requesting it with a web browser."

• Save a Post as Draft
• Blogger Extensions

"The good news is that this PHP/PEAR implementation is open source and immediately available. Be careful, this is not very seriously tested."

You can get it from here:

• the class: blogmarks.net/files/Services_Blogger_03.zip


• a package with all dependencies: blogmarks.net/files/Services_Blogger_03-package.zip


• for documentation and feedback, i started a wiki page on the blogmarks.net wiki about it: dev.blogmarks.net/wiki/ServicesBloggerPhpClient

Tired of coming to FeedBurner to analyze your stats? Use the API. Tired of "logging in" via a "browser" to "edit" your feed "settings"? Use the API.

What can't you do with the API? Nothing, with one exception. The API has a built-in limit of 20 burned feeds per user id. We will ratchet this down even lower if it's abused, but that seems like a reasonable number to get started.

"Announcing atom-blogger.el atom-blogger.el found at atom-blogger.tar.bz2 is a light-weight Emacs client for posting and editting blogger.com entries. It uses curl to handle the HTTP side of the blogger ATOM API, and relies on Emacs' support for editting XML --- either via nxml-mode or Emacs' vanila xml-mode."

Paul McDonald just announced the new Blogger JavaScript client library over on the Google Data APIs Blog:

The Blogger GData JS Client library enables developers to read and write blog posts using calls to our JavaScript library. This is a full client library, with support for authenticated access to private data and read-write capabilities. Now you can create Blogger applications and mashups that can read and write data from your Blogger blogs. No server-side programming is required. Your application can run on any domain, too. No proxying is required.

We have a new developer guide for JavaScriptand some code samples to give you ideas and get you started.

• Issue 795: Blog metafeed did not contain rel="self" links in entries. This had the even more unfortunate side effect of breaking some of our sample code, which was using these links to derive blog IDs.
• Issue 798: Query parameters were being repeated in the rel="next" and rel="prev" links in feeds, leading to invalid duplicate parameters.
• Issue 803: Unable to fetch blog documents.

Blog authors around the world, Google would like to remind you that it's your blog, your data. Now that Blogger allows users the ability to export all contents of their blog, the Data Liberation team would like to announce the Google Blog Converters project. This new Open Source project provides the ability to easily move blog posts and comments from service to service. This initial release provides Python libraries and runnable scripts that convert between the export formats of Blogger, LiveJournal, MovableType, and WordPress.

• Drafts intermittently not appearing in the authenticated ATOM feed
• Blogger v2 feeds do not contain gd:etag elements