michael at aurora.gen.nz
Fri Nov 1 14:11:04 UTC 2002
> For what it's worth, I was working on a Jabber presence display program in
> perl. I'll post the source code in a seperate message.
> The script is a little different from yours because it's designed for
> environments where the user uploads it. Thus, it needs a configuration
> file that specifies both a username and password to connect to the Jabber
> server. It caches results (well, not yet) to prevent repeated calls to
> the server, and it gives the user the ability to specify their own files
> to display images for certain statuses.
> It also has a text mode, which is useful if you want to use server-side
> includes to call it and return the text inline with your document.
Cool. Thanks for the code.
One of the issues I have with this type of implementation is that for every
website that contains my presence, a Jabber "user" must be created and
logged in to collect my presence. This might be fine for your homepage, but
I would like this to be a little more widespread than that. 10,000 web
pages, 10,000 more users signed into your server..? Also, it is not as easy
to configure as whacking in a single line of HTML into a webpage...
> A couple of points.
> 1. What is to be gained by revealing resource and priority from the
To be honest, I'm not sure. Maybe nothing. Maybe someone can think of a
reason. Maybe we can drop it...
> 2. Why limit images to 16x16 or 32x32? Seems kind of small, and a square
> shape limits the kind of data that can be returned by the server. Can a
> status line really fit in that?
16x16 images for pages where space is limited - a good example of this is
next to a users name in a forum system. For an example of this see the ICQ
flower icons in the ARS Technica forums. (You have to actually click though
to read some messages to see them):
I'm open to suggestions of other graphic sizes that could be served (and the
actual graphics themselves)
> On Fri, 1 Nov 2002, Michael Brown wrote:
> > I have put up a draft JEP for WebPresence on Yabber.org.
> > http://www.yabber.org/jep/webpresence/webpresence.xml
> > The aim is to define a standard way for Jabber status information to be
> > represented on web pages etc.
> > I am not much of a webmaster or CGI guru myself so I am looking for some
> > peer-review of this document. If anyone wants to offer to rewrite it or
> > offer an alternative proposal please speak up. I would also be
> > in anyone who was willing to write a reference implementation (it
> > be that hard). I think there is a large demand for this to be
> > so I would like to get it formalized as soon as we can.
> > Michael.
More information about the Standards