Recently I discovered what many looks like many other before me have already
figured out. The code to give new users a default roster only works one
way. It doesn't add roster entries for those who are listed in the
roster.xml file like one would expect.
For example, this item appears in the roster.xml distribution file file:
<item name='Helpdesk' jid='[EMAIL PROTECTED]' subscription='both'>
<group>Support</group>
</item>
If I was to use that file, then new users get this [EMAIL PROTECTED] added
to their
roster, but [EMAIL PROTECTED] doesn't get a corresponding item for the new
user in
their roster.
That makes the roster.xml almost useless, because even though the new user
thinks they
are subscribed to Helpdesk, when Helpdesk's presence changes, the new user
never gets
updates because it appears that jabber2d looks at helpdesks roster entries
to determine who to
send presence to. Furthermore, when Helpdesk gets presence updates about
the new user, it
often doesn't know what to do with them, since the new user isn't in
helpdesks roster.
Perhaps someone can tell me why this functionality was left out? Maybe I'm
missing some information?
I've read that others have used scripts to get around the problem, but I've
looked at the mod_template_roster.c code and it doesn't look like it will be
too hard to fix the problem there.
If I fix the problem can I contribute the code to the project or something?
Thanks,
Robert Temple
