All times are UTC.
00:33:55 <-- unghost has quit (A TLS packet with unexpected length was received.) 02:13:00 <instant-buildbot> build #3243 of macosx-nightly-default is complete: Failure [4failed compile] Build details are at http://buildbot.instantbird.org/builders/macosx-nightly-default/builds/3243 02:46:40 <-- clokep_work has quit (Ping timeout: 121 seconds) 02:51:18 <-- bgmCoder has quit (Connection closed) 04:01:03 <instant-buildbot> build #770 of linux64-nightly-default is complete: Failure [4failed compile] Build details are at http://buildbot.instantbird.org/builders/linux64-nightly-default/builds/770 04:24:18 <-- Suiseiseki has quit (Connection closed) 04:59:00 --> DGMurdockIII has joined #instantbird 06:34:16 --> Suiseiseki has joined #instantbird 06:54:12 --> abdelrhman has joined #instantbird 06:56:10 <-- abdelrhman has quit (Quit: Instantbird 1.6a1pre -- http://www.instantbird.com) 06:58:22 --> abdelrhman has joined #instantbird 07:41:29 --> Bollebib has joined #instantbird 08:11:25 <-- abdelrhman has quit (Ping timeout: 121 seconds) 08:13:35 <-- DGMurdockIII has quit (Quit: Leaving) 08:26:50 --> abdelrhman has joined #instantbird 08:30:52 <-- abdelrhman has quit (Ping timeout: 121 seconds) 10:19:22 <-- Tonnes has quit (Ping timeout: 121 seconds) 10:27:01 --> Tonnes has joined #instantbird 10:30:59 <-- Tonnes has quit (Quit: ChatZilla 0.9.92 [Firefox 47.0.1/20160623154057]) 11:02:23 --> gerard-majax has joined #instantbird 11:03:38 --> abdelrhman has joined #instantbird 11:08:42 <-- gerard-majax has quit (Ping timeout: 121 seconds) 11:09:40 <-- abdelrhman has quit (Ping timeout: 121 seconds) 11:10:11 --> abdelrhman has joined #instantbird 11:33:36 <-- abdelrhman has quit (Quit: Instantbird 1.6a1pre -- http://www.instantbird.com) 11:47:02 --> unghost has joined #instantbird 12:02:18 <-- BWMerlin has quit (Ping timeout: 121 seconds) 12:03:03 --> Tonnes has joined #instantbird 12:04:50 --> gerard-majax has joined #instantbird 12:06:37 --> abdelrhman has joined #instantbird 12:09:56 <-- abdelrhman has quit (Connection closed) 12:10:18 --> abdelrhman has joined #instantbird 12:19:00 --> clokep_work has joined #instantbird 12:19:00 * ChanServ sets mode +o clokep_work 12:19:48 <-- abdelrhman has quit (Ping timeout: 121 seconds) 12:40:31 --> abdelrhman has joined #instantbird 12:44:15 <clokep_work> So for oscar we seem to be hitting a different ifdef than we used to? I wonder if config.h isn't being processed properly now? 12:44:20 <clokep_work> / included. 12:48:49 <clokep_work> Any thoughts? 13:05:47 <-- abdelrhman has quit (Ping timeout: 121 seconds) 13:15:42 --> abdelrhman has joined #instantbird 13:27:43 <-- abdelrhman has quit (Connection closed) 13:27:50 --> abdelrhman has joined #instantbird 13:51:10 * clokep_work is now known as clokep 13:58:06 <-- abdelrhman has quit (Ping timeout: 121 seconds) 13:59:04 --> abdelrhman has joined #instantbird 14:05:46 <-- abdelrhman has quit (Connection closed) 14:06:08 --> abdelrhman has joined #instantbird 14:16:40 <-- abdelrhman has quit (Connection closed) 14:17:45 --> abdelrhman has joined #instantbird 14:21:46 <-- abdelrhman has quit (Ping timeout: 121 seconds) 14:26:08 --> abdelrhman has joined #instantbird 15:03:07 <-- unghost has quit (A TLS packet with unexpected length was received.) 15:12:24 <-- gerard-majax has quit (Ping timeout: 121 seconds) 16:25:03 <-- abdelrhman has quit (Connection closed) 16:36:10 --> abdelrhman has joined #instantbird 16:40:11 <-- abdelrhman has quit (Ping timeout: 121 seconds) 17:06:15 --> abdelrhman has joined #instantbird 17:24:12 <-- abdelrhman has quit (Connection closed) 17:24:34 --> abdelrhman has joined #instantbird 17:42:51 <-- abdelrhman has quit (Connection closed) 17:44:02 --> abdelrhman has joined #instantbird 18:01:07 <-- abdelrhman has quit (Connection closed) 18:01:20 --> abdelrhman has joined #instantbird 18:18:35 <-- abdelrhman has quit (Ping timeout: 121 seconds) 18:32:16 --> abdelrhman has joined #instantbird 18:38:18 <-- abdelrhman has quit (Ping timeout: 121 seconds) 18:39:17 --> abdelrhman has joined #instantbird 18:46:58 <abdelrhman> Do we have something special for delayed delivery of messages? 18:46:59 <abdelrhman> I mean in the UI 18:48:16 <abdelrhman> IIRC we can't reorder messages in UI after showing it 18:50:33 <-- abdelrhman has quit (Connection closed) 18:50:54 --> abdelrhman has joined #instantbird 18:51:05 <abdelrhman> (e.g. sorting by date) 19:00:10 <freaktechnik> for irc echoing clokep was suggesting just showing it once you know it arrived at the server, for example. 19:00:33 <-- abdelrhman has quit (Ping timeout: 121 seconds) 19:01:06 <clokep> abdelrhman: What do you mean by "delayed delivery"? Yes, we can't reorder (that's a really confusing UX anyway...) 19:06:14 --> abdelrhman has joined #instantbird 19:07:21 <abdelrhman> clokep: delayed delivery is an XEP allows us to display a received message that has been send while offline or in case of receiving cached messages from a conference room 19:07:42 <clokep> abdelrhman: OK...so what's the problem with just displaying them? 19:07:51 <freaktechnik> but the cached thing already happens 19:07:53 <clokep> I'm not sure if you're asking about user experience or about what's technically capable. 19:08:16 <abdelrhman> We need to notify the user that those messages are sent earlier 19:08:55 <freaktechnik> if the user was not connected inbetween those messages will not be below any newer messages.And you can set the correct timestamp 19:09:41 <clokep> abdelrhman: I would just set the right date on them for now. 19:11:12 <abdelrhman> I'm not sure about the context when the user reads them, if he/she does not notice that some of shown messages are not in the oreder 19:15:14 <-- abdelrhman has quit (Ping timeout: 121 seconds) 19:16:54 --> abdelrhman has joined #instantbird 19:22:16 --> gerard-majax has joined #instantbird 19:22:58 <-- abdelrhman has quit (Ping timeout: 121 seconds) 19:27:30 <-- EionRobb has quit (Quit: Leaving.) 19:27:34 --> abdelrhman has joined #instantbird 19:29:07 <-- gerard-majax has quit (Ping timeout: 121 seconds) 19:32:55 <-- abdelrhman has quit (Connection closed) 19:36:33 <clokep> abdelrhman: Why would they not be in order? :-S 19:38:30 <freaktechnik> hmm, maybe if the two XMPP servers disconnected, so both could still send messages to their servers? I have no idea how that delayed message thing works 19:43:36 --> abdelrhman has joined #instantbird 19:43:44 <-- Bollebib has quit (Ping timeout: 121 seconds) 19:46:05 <abdelrhman> http://xmpp.org/extensions/xep-0203.html#protocol 19:46:13 --> gerard-majax has joined #instantbird 19:46:38 <freaktechnik> but then they should never be out of orders with those examples 19:46:48 <freaktechnik> as they are always sent before the user would've sent anything on their side. 19:47:07 <freaktechnik> but again, I think that relay is already a thing in js-xmpp 19:47:12 <freaktechnik> at least I get that in thunderbird. 19:47:32 <clokep> abdelrhman: Did you see my comment? 19:47:48 <clokep> That XEP isn't very helpful to me. 19:48:06 <clokep> How would things be out of order? 19:49:04 <abdelrhman> I thought that the delayed messages can be delivered while user is talking to his/her partner or in the room 19:49:46 <abdelrhman> and when user tries to re read messages the context will not be correct. 19:50:14 <abdelrhman> But it seems this cannot happen 19:50:55 <abdelrhman> freaktechnik: I think it's not implemented. I'll check that now 19:51:31 <freaktechnik> I do get correctly timestamped replays on tatoeba.org 19:51:41 <clokep> I get them on pidgin, yeah. 19:52:13 <freaktechnik> I get them in thunderbird, which should be js-xmpp afaik 19:52:26 <freaktechnik> (I don't have the libpurple plugin) 19:52:57 <abdelrhman> Yes, you are right. it's implemented only for message stanzas 19:54:15 <abdelrhman> we need to implement it also for presence ones 19:58:32 <clokep> Can it be abstracted? :) 20:03:12 <-- abdelrhman has quit (Connection closed) 20:04:14 --> abdelrhman has joined #instantbird 20:06:27 <abdelrhman> I'll try 20:26:03 <-- abdelrhman has quit (Ping timeout: 121 seconds) 20:29:51 --> EionRobb has joined #instantbird 20:34:49 --> abdelrhman has joined #instantbird 20:44:10 <-- abdelrhman has quit (Connection closed) 20:47:41 --> abdelrhman has joined #instantbird 20:50:20 <-- abdelrhman has quit (Connection closed) 20:53:24 --> abdelrhman has joined #instantbird 20:59:38 <-- abdelrhman has quit (Ping timeout: 121 seconds) 21:00:28 --> abdelrhman has joined #instantbird 21:24:46 <abdelrhman> I think the modification will touch idleSince if it 21:24:54 <abdelrhman> it has delay element' 21:32:53 <-- abdelrhman has quit (Connection closed) 21:33:15 --> abdelrhman has joined #instantbird 21:37:16 <-- abdelrhman has quit (Ping timeout: 121 seconds) 21:41:49 --> abdelrhman has joined #instantbird 21:52:43 <-- gerard-majax has quit (Ping timeout: 121 seconds) 22:02:04 --> Bollebib has joined #instantbird 22:05:45 <-- abdelrhman has quit (Connection closed) 22:09:44 --> abdelrhman has joined #instantbird 22:33:30 --> aleth has joined #instantbird 22:33:30 * ChanServ sets mode +o aleth 22:39:50 <-- abdelrhman has quit (Connection closed) 22:39:55 --> abdelrhman has joined #instantbird 22:55:17 <abdelrhman> aleth: ^^ 22:57:31 <aleth> It looks like you know more about this than me ;)_ 22:57:58 <aleth> Sounds reasonable. 22:58:04 <aleth> Also maybe take a look at XEP-0160 22:58:23 <aleth> (to check we are following it) 22:59:30 <aleth> For messages in the end the only thing that matters is that the correct time/date is set, because that's what's displayed to the user. 23:00:10 <aleth> There is also a 'delayed' flag you can set on the message object if you know a message was delayed 23:02:03 <aleth> I think the XMPP code already does this somewhere, but you can check 23:03:58 <abdelrhman> Yes, it does 23:05:35 <abdelrhman> https://dxr.mozilla.org/comm-central/source/chat/protocols/xmpp/xmpp.jsm#408 23:06:01 <aleth> ah, and there is also https://dxr.mozilla.org/comm-central/source/chat/protocols/xmpp/xmpp.jsm#1920 23:07:03 <abdelrhman> yeah, I'll abstract this to be used also with presence stanzas 23:07:43 <aleth> Good, also add a comment with the XEP number for future reference 23:08:06 <abdelrhman> OK 23:08:17 <aleth> but you do that anyway ;) 23:08:36 <abdelrhman> :D 23:08:44 <abdelrhman> The example 2 in http://xmpp.org/extensions/xep-0203.html#examples 23:09:14 <abdelrhman> I think the modification will touch idleSince, right? 23:09:38 <aleth> seems likely, as the only extra info is when that status was set 23:21:40 <-- aleth has quit (Quit: Instantbird 50) 23:26:24 <-- Bollebib has quit (Ping timeout: 121 seconds) 23:57:36 <-- abdelrhman has quit (Connection closed) 23:59:05 --> abdelrhman has joined #instantbird