Logs for jdev@conference.jabber.org

[00:07:57] * left the chat.
[00:59:30] * joined the chat.
[01:00:17] * left the chat.
[01:56:32] * left the chat.
[01:57:10] * joined the chat.
[01:57:39] * left the chat.
[02:06:59] * joined the chat.
[02:11:19] * left the chat.
[02:31:43] * left the chat.
[02:55:10] * joined the chat.
[03:00:44] * left the chat.
[03:24:02] * joined the chat.
[03:25:28] * joined the chat.
[03:25:28] * left the chat.
[03:34:43] * left the chat.
[04:52:52] * joined the chat.
[04:53:39] * joined the chat.
[05:01:09] * joined the chat.
[05:23:51] * left the chat.
[05:43:46] * left the chat.
[05:49:48] * left the chat.
[05:52:21] * left the chat.
[05:53:17] * joined the chat.
[06:04:38] * joined the chat.
[06:04:59] * joined the chat.
[06:07:05] * left the chat.
[06:17:03] * joined the chat.
[06:28:42] * joined the chat.
[06:43:33] * joined the chat.
[06:55:41] * joined the chat.
[07:11:42] * joined the chat.
[07:16:03] * joined the chat.
[07:38:30] * left the chat.
[07:46:31] * joined the chat.
[07:54:17] * joined the chat.
[07:59:50] * left the chat.
[08:14:58] * left the chat.
[08:16:41] * joined the chat.
[08:19:43] * left the chat.
[09:37:15] * left the chat.
[09:40:07] * joined the chat.
[09:40:46] * left the chat.
[09:40:47] * joined the chat.
[09:41:53] * left the chat.
[09:41:53] * joined the chat.
[09:46:02] * joined the chat.
[10:01:17] * left the chat.
[10:13:21] * joined the chat.
[10:41:08] * joined the chat.
[10:54:09] * joined the chat.
[11:09:07] * left the chat.
[11:18:11] * left the chat.
[11:18:20] * joined the chat.
[11:33:39] * joined the chat.
[11:40:16] * joined the chat.
[12:07:38] * left the chat.
[12:07:38] * joined the chat.
[12:33:22] * joined the chat.
[12:44:10] * left the chat.
[12:59:51] * left the chat.
[13:00:29] * joined the chat.
[13:00:32] * joined the chat.
[13:17:39] * left the chat.
[13:18:09] * joined the chat.
[13:23:29] * left the chat.
[13:29:41] * joined the chat.
[13:30:03] * left the chat.
[13:40:06] * left the chat.
[14:05:05] * joined the chat.
[14:11:20] * left the chat.
[14:25:34] * joined the chat.
[14:38:50] * left the chat.
[14:46:03] * joined the chat.
[14:51:06] * left the chat.
[15:05:38] * left the chat.
[15:07:39] * joined the chat.
[15:13:27] * joined the chat.
[15:14:21] * left the chat.
[15:45:20] * joined the chat.
[15:50:21] * left the chat.
[15:54:15] * joined the chat.
[15:56:57] * left the chat.
[15:58:27] * left the chat.
[15:58:55] * joined the chat.
[15:59:26] * left the chat.
[16:11:28] * left the chat.
[16:11:49] * joined the chat.
[16:14:05] * left the chat.
[16:19:19] * joined the chat.
[16:22:07] * left the chat.
[16:32:52] * joined the chat.
[16:34:08] * joined the chat.
[16:34:22] * joined the chat.
[16:35:25] * left the chat.
[16:48:29] * joined the chat.
[16:54:11] * left the chat.
[16:55:26] * joined the chat.
[17:00:57] * left the chat.
[17:13:21] * left the chat.
[17:15:16] * left the chat.
[17:15:18] * joined the chat.
[17:16:37] * left the chat.
[17:23:22] * joined the chat.
[17:27:44] * joined the chat.
[17:33:34] * joined the chat.
[17:46:15] * joined the chat.
[18:08:14] * joined the chat.
[18:18:45] * joined the chat.
[18:18:49] * left the chat.
[18:20:13] <> I am looking for a specification if the client has to send presences to the users transports or if it's the job of the server to relay the presences to the transports. Can someone give me a pointer? Background: My transports don't go online when I connect my account
[18:32:37] <> Flow: you send your presence to your server, and it relays it to all the users subscribed to your presence
[18:33:40] <> naw: Thanks, but I am not talking about users, but transports (components). Not sure if the same rules apply there
[18:33:41] <> If I remember correctly, transports work emulating a server, so there are users like "user%hotmail@transport.somejabberserver.com"
[18:34:16] <> naw: No, not the transport contacts, the transport itself is in question here
[18:34:17] <> those users are subscribed to your presence, so your server will send updates to them
[18:38:33] <> hmmm I see that psi has an option for "log On" and "log out" and what it does is to send presences to the transport address
[18:39:42] <> but years ago, wen I used transports, they got the online presence as soon I log in on my jabber account
[18:40:34] * joined the chat.
[18:41:48] <> yep, and it seems that I would need this option in gajim
[18:42:08] <> would be great if I could find something in the specs about the expected behavior
[18:42:18] <> but maybe Asterix can shed some light into this
[18:46:59] <> as transports are registered on the roster (at least it shoud;) it will get the online presence when logging in
[18:51:44] * left the chat.
[18:51:51] * joined the chat.
[18:52:05] <> Asterix: my transports stay grey when I connect with gajim
[18:52:30] <> do you have subscription = both in transport information window?
[18:53:07] <> hmm, no only "to"
[18:54:06] <> I am looking currently into the cause for http://community.igniterealtime.org/docs/DOC-2601#Gajim_0154
[18:54:50] <> I am not sure why gajim would need a workaround at all.
[18:55:41] <> if you request subscription, what happens?
[18:56:28] <> Asterix: the manage transport option does not show the "subscription" option as it does with "manage contacts"
[18:56:39] <> so I don't have a way to request subscription
[18:56:53] <> indeed ...
[18:57:07] <> you'll have toi try in XML console ;)
[18:57:30] <> that should have happened when adding the transport ...
[18:57:46] * left the chat.
[18:58:46] <> maybe, but since this seems like documented behavior with gajim and gojara, I don't think that this can be the solution
[18:58:56] * left the chat.
[18:59:14] <> it's maybe a problem in the plugin if it doesn't accept the subscription request ...
[18:59:41] * left the chat.
[19:00:12] <> what makes the situation complicated, is the fact that gojara isn't actually the transport but a remote roster implementation for openfire, the transport is actually spectrum2
[19:00:16] * joined the chat.
[19:00:34] * joined the chat.
[19:01:06] <> so spectrum should accept the subscription then, no?
[19:02:29] <> maybe, but I would bet that the behavior won't appear with a spectrum2 only setup. I belive gojara messes something up
[19:03:18] <> no idea what gojara is and how all that behaves ... but the reason your server don't send presence to the transport is this missing subscription ...
[19:03:58] <> that doesn't help finding where the issue is ...
[19:04:18] <> so the server does actually relay the presence stanza to the registered components/transports? I am looking for the specification on this
[19:04:53] <> that's right, but you gave me enough information that I can confront the gojara devs with
[19:05:08] <> yes, the transport is a contact like others, so server relay presence to it, if it request subscription.
[19:08:50] * left the chat.
[19:11:37] * joined the chat.
[19:21:46] * joined the chat.
[19:41:07] * joined the chat.
[19:46:17] * joined the chat.
[20:15:28] * left the chat.
[20:18:28] * joined the chat.
[20:18:47] <> Hi
[20:21:18] <> I would like to get the yaxim name (all lowercase) and url (http://yaxim.org/) updated on http://xmpp.org/xmpp-software/clients/ - thanks :D
[20:22:32] * left the chat.
[20:51:01] * joined the chat.
[21:00:21] * left the chat.
[21:03:06] * left the chat.
[21:04:41] * joined the chat.
[21:04:53] * left the chat.
[21:07:09] * left the chat.
[21:37:13] * joined the chat.
[21:37:44] * joined the chat.
[21:52:48] * joined the chat.
[22:07:10] * left the chat.
[22:09:57] * left the chat.
[22:59:32] * joined the chat.
[23:01:58] * joined the chat.
[23:10:44] * joined the chat.
[23:13:28] * left the chat.
[23:17:18] * joined the chat.
[23:21:20] * joined the chat.
[23:27:39] * joined the chat.
[23:28:49] * joined the chat.
[23:39:32] * joined the chat.
[23:46:25] * joined the chat.
[23:46:34] * left the chat.
[23:47:19] * joined the chat.
[23:51:48] * joined the chat.