[Wocky] SIPB Jabber

[Michael Lieberman]

I believe we care mostly about instances as tags.

Reading RFC 3921, it seems like the <thread/> element is innappropriate to 
serve as an instance:

"The value of the <thread/> element MUST be treated
    as opaque by entities; no semantic meaning may be derived from it,
    and only exact comparisons may be made against it."

The <subject/> element should work, however it goes against Draft 
JEP-0045 (Jabber Enhancement Proposal) that treats <subject/> as a global 
variable of the room. It expects changing the subject to be done 
separately from sending a message. We could write a client that uses it as 
an "instance", but users of the current version of gaim would instead see 
each time the subject "changes".

-Mike

On Mon, 26 Jun 2006, Greg Hudson wrote:

> Hi, Timothy.  Here's what I know.
>
> On Sat, 2006-06-24 at 21:33 -0400, Timothy G. Abbott wrote:
>>  	- the lack of a useful "instance" feature
>
> Do you mean the ability to subscribe to all or a part of a discussion
> node, or the ability to tag messages with a topic field within a
> discussion node?
>
> The Jabber protocol includes <subject/> and <thread/> elements within
> messages, and I believe our server supports them just fine.  This is
> more an issue of client support; I think popular Jabber clients
> generally do nothing with those fields.
>