The badge artwork, and why it is not here

The second page of the old programme was a shop window. jabberpowered.org/logos.html offered the JabberPowered badge in a range of sizes, in GIF and in PNG, plus an EPS file for anyone who needed to set it in print. The archived captures show pixel heights running from twelve up to thirty six, with a recommended size for websites at the top of the page.

Why an eleven size range made sense in 2003

Bitmap badges did not scale. A logo drawn for twenty pixels was not the same drawing as one for thirty six: it was redrawn, with fewer details and heavier strokes, so that it stayed legible at the size it would actually be seen. Offering a ladder of sizes was the only way to keep a mark recognisable across a web made of tables and fixed layouts. It is also why the EPS mattered: vector artwork for the one case, print, where you could not predict the size at all.

Why the artwork is not republished here

The page next door made the position explicit. The badge was a trademark of Jabber, Inc., licensed through the Jabber Software Foundation, and its use was subject to conditions the licensee accepted. A licence granted to badge holders in 2003 is not a licence to a site that bought the domain in 2026. We hold no rights in that artwork, so the historical image addresses answer 410 rather than serving files, and this page describes the badge instead of handing it out.

What replaced it

The community that grew out of the programme now publishes its own current logo and its own terms for it. Those terms are published by the XMPP Standards Foundation, and they are the only place to check what is permitted. If you maintain a project that speaks the protocol, the safest route is to read the current guidelines yourself and, where you are unsure, write a sentence instead of placing a mark: saying that a service speaks XMPP and linking to the specification is accurate, free and unambiguous.

A note for anyone still hotlinking

Some pages from the early 2000s still carry an image tag pointing at this domain. Those requests now receive a 410 with a short explanation rather than a broken image or, worse, a picture chosen by whoever owns the domain. That is deliberate: an address that once served a trademark should not quietly start serving something else.

Elsewhere on this site

The conditions attached to the badge are set out on the guidelines page, the software it was pinned to is listed on the directory page, and the protocol underneath all of it starts with the three stanza types.

Source: Internet Archive captures of jabberpowered.org/logos.html and /guidelines.html, 2001 to 2004.