Development

So you've just published a new article on your Geeklog site and now you're eagerly awaiting the world to take notice. But it takes so long ... Sure, your regular readers will be notified through the RSS feed within the hour. But GoogleBot and friends will only come visit at their own pace and it will take even longer for your post to show up in their search engines. Isn't there some way to get the word out faster?

And indeed there is: As of Geeklog 1.4, you can send a Ping to weblog directory services, i.e. websites that specialise in listing the newest posts of blogs around the world. So by sending a Ping, you tell them "Hey, look! My new article is up!!!" and the sites send their spiders to index them. And within minutes, your post can be found on those sites. Nifty, eh?

Trackback and Pingback both provide a convenient solution for the same problem: Making connections between posts on different sites. And since they are standardized, they can be sent to sites running other weblog / CMS software.

So let's say you've read about the release of Geeklog 1.4.0b1, proceeded to download it, tried it out, and then posted a review on your own site. How can you let people visiting geeklog.net know about your review? Sure, you could post a comment under the announcement, adding a link back to your site. But with Trackback and Pingback, you can do the same in a semi-automatic way without having to visit geeklog.net.

In other words: A Trackback comment is an automatically created comment, added to a post on some other site and pointing back to a post on your own site.

Technical details aside, the differences between Trackback and Pingback boil down to this: A Trackback contains, in addition to the link back to your post, the title of the post, the name of your site, and an excerpt of your post while Pingbacks contain only the link. Since they are much simpler Pingbacks can be sent mostly automatic while a Trackback comment requires some interaction, especially for the excerpt.

The comment plugin API for previous versions of Geeklog has been bothering me for a long time. There were some fundamental problems that prevented plugin authors from exercising full control over their comments. To correct these deficiencies and to hopefully make development of plugins using comments simpler, we've revamped the comment API making it more powerful and at the same time easier to use.

Below is a description of the new plugin comment engine and how to use it in the development of Geeklog plugins. Those unfamiliar with plugin development in Geeklog may first want to read Geeklog's Plugin Development Guide.