All times are UTC.
00:16:10 --> mconley has joined #instantbird 00:49:37 <-- GeekShadow has quit (Ping timeout) 00:49:40 --> GeekShadow has joined #instantbird 01:35:32 <-- mconley has quit (Input/output error) 01:48:06 <-- mali has quit (Ping timeout) 01:49:02 --> mconley has joined #instantbird 02:26:55 <instantbot> email@example.com set the Resolution field on bug 2190 to FIXED. 02:26:58 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=2190 tri, --, 1.5, clokep, RESO FIXED, Update the credits for Instantbird 1.5 02:33:04 <instantbot> Check-in: http://hg.instantbird.org/instantbird/rev/e9b42c71279a - Patrick Cloke - Bug 2190 - Update the credits for Instantbird 1.5, r=fqueze. 02:38:07 <instant-buildbot> build #483 of macosx-onCommit is complete: Success [build successful] Build details are at http://buildbot.instantbird.org/builders/macosx-onCommit/builds/483 03:17:35 <instant-buildbot> build #996 of linux-nightly-default is complete: Success [build successful] Build details are at http://buildbot.instantbird.org/builders/linux-nightly-default/builds/996 03:29:15 <-- wnayes has quit (Quit: wnayes) 03:30:51 --> FireFly_TB has joined #instantbird 03:47:34 <instant-buildbot> build #481 of linux-onCommit is complete: Success [build successful] Build details are at http://buildbot.instantbird.org/builders/linux-onCommit/builds/481 03:59:21 <-- skeledrew has quit (Ping timeout) 03:59:37 --> skeledrew has joined #instantbird 04:11:12 <-- FireFly_TB has quit (Quit: FireFly_TB) 04:15:15 --> FireFly_TB has joined #instantbird 04:15:23 <-- FireFly_TB has quit (Quit: FireFly_TB) 04:32:38 <instant-buildbot> build #1028 of macosx-nightly-default is complete: Success [build successful] Build details are at http://buildbot.instantbird.org/builders/macosx-nightly-default/builds/1028 04:35:45 --> Mook has joined #instantbird 04:50:01 <-- mconley has quit (Input/output error) 05:05:53 <-- EionRobb1 has quit (Quit: Leaving.) 05:50:30 --> mconley has joined #instantbird 05:55:51 <-- mconley has quit (Ping timeout) 06:19:39 --> EionRobb has joined #instantbird 06:24:56 --> FireFly_TB has joined #instantbird 06:30:13 <-- FireFly_TB has quit (Input/output error) 06:30:55 <-- gerard-majax_ has quit (Ping timeout) 06:34:37 --> jb has joined #instantbird 06:35:28 <-- jb has quit (Connection reset by peer) 06:35:33 --> jb has joined #instantbird 06:37:22 <-- jb has quit (Ping timeout) 07:01:01 <-- Mook has quit (Ping timeout) 07:05:13 --> Mook has joined #instantbird 07:09:19 <instant-buildbot> build #1116 of win32-nightly-default is complete: Success [build successful] Build details are at http://buildbot.instantbird.org/builders/win32-nightly-default/builds/1116 07:11:06 <instant-buildbot> build #475 of win32-onCommit is complete: Failure [failed compile] Build details are at http://buildbot.instantbird.org/builders/win32-onCommit/builds/475 blamelist: Patrick Cloke <firstname.lastname@example.org> 07:11:27 --> gerard-majax_ has joined #instantbird 07:16:31 --> jb has joined #instantbird 07:28:54 --> Mic has joined #instantbird 07:28:54 * ChanServ sets mode +h Mic 07:30:58 --> nhnt11 has joined #instantbird 07:32:33 <Mic> Not supported yet as it seems: https://bugzilla.mozilla.org/show_bug.cgi?id=235605 :( 07:42:09 <Mic> nhnt11: do all the bugs you filed for regressions or follow-ups block the bug that relates to them? 07:43:23 <Mic> That would hopefully leave only a few block-lists to go through to compile a list of issues that can be triaged. 07:43:58 <nhnt11> They should be blocking, yes 07:45:19 <Mic> The quicksearch can't do this but the full search in Bugzilla allows to search for "Blocks" "any string of" "bugnumber bugnumber ..." by the way 07:45:23 <flo-retina> Mic: you can make all the awesomebugs like ranking, auto-LIST, etc... block the initial awesomebug, to have a single dependency tree ;). 07:45:51 <-- flo-retina has quit (Quit: Instantbird 1.5a1pre -- http://www.instantbird.com) 07:45:54 --> flo-retina has joined #instantbird 07:45:54 * ChanServ sets mode +qo flo-retina flo-retina 07:46:01 <Mic> nhnt11: ^ 07:46:55 <-- Mook has quit (Quit: Mook) 07:50:37 <flo-retina> ah, http://www.mozilla.org/en-US/about/powered-by/ has been redesigned 07:53:01 <-- nhnt11 has quit (Quit: Instantbird 1.5a1pre -- http://www.instantbird.com) 07:53:05 --> nhnt11 has joined #instantbird 08:01:24 <-- jb has quit (Ping timeout) 08:26:38 <-- nhnt11 has quit (Ping timeout) 08:29:21 --> nhnt11 has joined #instantbird 08:32:05 --> jb has joined #instantbird 08:33:14 --> chrisccoulson has joined #instantbird 08:37:07 <Mic> Ah, that's done already. :) 08:37:09 <Mic> https://bugzilla.instantbird.org/showdependencygraph.cgi?id=1583 08:44:26 --> qlum has joined #instantbird 08:52:43 <-- jb has quit (Ping timeout) 08:54:32 --> BWMerlin has joined #instantbird 08:54:39 <-- EionRobb has quit (Quit: Leaving.) 08:59:54 --> aleth has joined #instantbird 08:59:54 * ChanServ sets mode +h aleth 09:02:17 <-- flo-retina has quit (Quit: Instantbird 1.5a1pre -- http://www.instantbird.com) 09:15:27 <instantbot> email@example.com set the Resolution field on bug 2155 to WONTFIX. 09:15:31 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=2155 nor, --, ---, nobody, RESO WONTFIX, Existing conversations should be ranked to the top 09:40:35 --> flo-retina has joined #instantbird 09:40:35 * ChanServ sets mode +qo flo-retina flo-retina 09:42:06 <-- aleth has quit (Quit: Ciao) 09:42:11 --> aleth has joined #instantbird 09:42:11 * ChanServ sets mode +h aleth 09:45:17 <-- aleth has quit (Quit: Ciao) 09:45:23 --> aleth has joined #instantbird 09:45:23 * ChanServ sets mode +h aleth 09:46:39 <aleth> The profiler is working :) 09:47:43 <flo-retina> ah, you got it from the email I sent to nhnt11 a while ago? :) 09:47:58 <aleth> Yes :) 09:48:04 * flo-retina was surprised for a few seconds, as the pull request to make it be compatible with ib hasn't been sent yet ;) 09:48:26 <flo-retina> aleth: happy profiling! \o/ 09:50:50 <aleth> The read/write points indicate reading/writing what? 09:52:11 <aleth> (above the profile spike diagram) 09:53:05 <flo-retina> maybe sync disk I/O? 09:53:35 <aleth> Maybe... if you click on them you get a list of "markers" indicating read/write was on the main thread 09:54:33 --> nhnt11_phone has joined #instantbird 09:58:29 <-- nhnt11_phone has quit (Quit: AndroIRC - Android IRC Client ( http://www.androirc.com )) 09:58:58 <aleth> flo-retina: Did you ask in the pull request whether we could host it on AIO as well? Might be useful to have it there too 09:59:55 <flo-retina> No pull request yet! 10:00:03 <flo-retina> my code is full of dumps and other debugging stuff... 10:00:08 <flo-retina> I need to clean it up and send a pull request 10:22:18 <aleth> I saw the dumps, I assumed that was just the profiler ;) 10:45:35 <-- Mic has quit (Quit: Instantbird -- http://www.instantbird.com) 10:47:18 * nhnt11 is back 11:14:24 <-- dew has quit (Ping timeout) 11:14:48 --> dew has joined #instantbird 11:58:09 --> Huvik has joined #instantbird 12:09:12 --> qheaden has joined #instantbird 12:10:49 <-- qheaden has left #instantbird () 12:11:22 --> qheaden has joined #instantbird 12:23:11 <-- BWMerlin has quit (Quit: BWMerlin) 12:29:39 <clokep_work> qheaden: Review ping. 12:37:17 <instantbot> firstname.lastname@example.org requested review from florian@instantbird .org for attachment 2932 on bug 1980. 12:37:20 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=1980 nor, --, 1.5, clokep, RESO FIXED, In IRC account properties, Auto-Joined Channels doesn't support non-ASCII symbols 12:37:54 <-- nhnt11 has quit (Ping timeout) 12:44:23 <instantbot> email@example.com granted review for attachment 2932 on bug 1980. 12:44:26 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=1980 nor, --, 1.5, clokep, RESO FIXED, In IRC account properties, Auto-Joined Channels doesn't support non-ASCII symbols 12:47:00 --> mconley has joined #instantbird 12:58:55 --> nhnt11 has joined #instantbird 13:03:39 <instantbot> Check-in: http://hg.instantbird.org/instantbird/rev/c7587a9e2f68 - Patrick Cloke - Bug 1980 - In Join Chat, Auto-Joined Channels doesn't support non-ASCII symbols, r=fqueze. 13:06:55 --> jb has joined #instantbird 13:07:22 --> mali has joined #instantbird 13:17:55 <-- mconley has quit (Input/output error) 13:27:55 <-- jb has quit (Ping timeout) 13:28:55 --> jb has joined #instantbird 13:36:46 * aleth wonders if codes like zone(0xf2b4c800) in about:memory could easily be turned into something readable 13:37:53 <aleth> Maybe they're irrelevant as dynamically allocated 13:40:50 --> jb1 has joined #instantbird 13:41:01 <-- jb has quit (Connection reset by peer) 13:45:15 <aleth> nhnt11: Could we get the tooltips to work in the about:memory tab? ;) 13:56:42 <nhnt11> aleth: Where exactly? 13:56:57 <aleth> Scroll right to the bottom and read ;) 13:57:17 <nhnt11> Ah 13:57:35 * nhnt11 doesn't really know how to fix that 13:57:38 <-- Huvik has quit (Ping timeout) 13:57:40 <nhnt11> Sorry I've been a bit unavailable btw 13:57:55 <aleth> Real life happens ;) 13:58:27 --> Huvik has joined #instantbird 14:12:44 <aleth> nhnt11: You probably have to set the tooltip attribute on the browser 14:14:50 --> mconley has joined #instantbird 14:15:38 <aleth> If you are lucky tooltip="aHTMLTooltip" is enough. 14:22:15 <-- mconley has quit (Input/output error) 14:27:11 --> mconley has joined #instantbird 14:27:38 <-- mconley has quit (Input/output error) 14:28:31 --> mconley has joined #instantbird 14:39:38 <-- nhnt11 has quit (Quit: Instantbird 1.5a1pre -- http://www.instantbird.com) 14:48:06 <instant-buildbot> build #476 of win32-onCommit is complete: Failure [failed compile] Build details are at http://buildbot.instantbird.org/builders/win32-onCommit/builds/476 blamelist: Patrick Cloke <firstname.lastname@example.org> 14:50:05 --> wnayes has joined #instantbird 14:58:22 --> nhnt11 has joined #instantbird 15:16:12 <nhnt11> aleth: Tooltips aren't that simple I'm afraid 15:16:23 <nhnt11> I need to use FillInHTMLTooltip somehow... 15:16:35 <nhnt11> I have to go now though. I may be back later tonight 15:16:36 <-- nhnt11 has quit (Quit: Instantbird 1.5a1pre -- http://www.instantbird.com) 15:17:18 <aleth> nhnt11: Right, you might have to add your own tooltip XUL element and point at that and then copy in parts of the FX browser.xml version of that function, if the existing one in convbrowser doesn't work for this 15:20:05 <aleth> Hmm, it's surprisingly short 15:20:05 <aleth> Possibly the comment here applies http://dxr.mozilla.org/mozilla-central/source/browser/base/content/browser.js#l2708 15:21:47 <-- mali has quit (Quit: Instantbird http://www.instantbird.com) 15:23:15 <aleth> ah, it's only short because they moved the code :P http://dxr.mozilla.org/mozilla-central/source/toolkit/content/widgets/popup.xml#l498 15:24:31 <clokep_work> I like seeing things in toolkit. :) 15:25:09 <aleth> Yes :) 15:25:35 <aleth> Must be a recent change though as the page attribute appears to be undocumented 15:26:13 <flo-retina> aleth: I tried porting that patch a while ago (I have a WIP around) but didn't get it to work :-S 15:26:28 <flo-retina> I wanted to file a bug so that we don't forget to cleanup, but never got to it 15:26:50 <flo-retina> I think we've already factored most of this tooltip code in convbrowser.xml, which isn't the best place if we want to also benefit from it in about:memory ;) 15:28:59 <clokep_work> aleth: Sooooo any chance we could convince you to refactor the tab complete stuff and write some tests? :-) I know it isn't fun. 15:29:12 <aleth> clokep_work: Have you got plans for it? 15:29:17 * aleth agrees he should do it... 15:29:21 <flo-retina> is it the most pressing refactoring these days? 15:29:49 * flo-retina isn't sure how easy it is to write tests without a build machine 15:30:10 <flo-retina> I think at some point soon we really need to discuss our goals for the next few months 15:30:24 <flo-retina> are we pushing 1.5 out asap? 15:30:37 <flo-retina> what's planned for just after that? 15:31:40 <aleth> When "asap" is kind of determined by what we decide is blocking 15:31:50 <clokep_work> I didn't say ASAP! 15:32:12 * aleth asked nhnt11 for a bug list to be able to get a clearer idea of what was still needed 15:32:45 <aleth> We should definitely pref on yahoo first and move chatdev to it for a while first 15:34:55 <flo-retina> I think what makes it hard for me on this 1.5 planning thing is that I really don't have any idea of how much time I'll be able to spend on Ib in the next few months 15:36:00 <aleth> Wasn't there some l10n issue that needed resolving too? 15:36:06 <flo-retina> yes 15:37:00 <-- mconley has quit (Connection reset by peer) 15:37:41 --> mconley has joined #instantbird 15:46:58 * clokep_work sent an email... 15:47:17 <clokep_work> flo-retina: I think we want to release pretty soon... 15:49:55 <clokep_work> I guess...do we think the awesometab is ready? 15:50:13 <flo-retina> right now no. 15:50:24 <flo-retina> Do we think it can be ready within a week... maybe? :) 15:50:51 <clokep_work> aleth: ^ 15:50:58 <clokep_work> I haven't used it THAT much. 15:52:30 <aleth> I doubt it unless nhnt11 has a fair bit of time in the next week. 15:52:50 <aleth> Plus we should have a week of js-yahoo #chatdev imho (idk what bugs remain there) 15:53:00 <flo-retina> aleth: I meant "within a week [of work]" 15:53:12 <flo-retina> not 7 days from now 15:54:30 <aleth> It will be easier to predict once ranking looks closer to what we expect (hard to know how many tweaks are needed - hopefully not many) 15:55:26 <flo-retina> right 15:55:51 <flo-retina> so do we know what nhnt11 is waiting to get the ranking fixed? ;) 15:55:52 <aleth> There may be more bugs like the XMPP issue I discovered yesterday 15:56:22 <flo-retina> also, I just opened the awesome tab to see how ranking looked, and that just made the whole UI very unresponsive, to the point that typing "so do we know what nhnt11 is waiting to get the ranking fixed? ;)" was quite difficult 15:56:38 <aleth> I've not experienced any unresponsiveness myself 15:56:50 <aleth> Would be interesting to figure out why ;) 15:56:54 <flo-retina> I guess I need to get the profiler installed in this profile 15:57:00 <clokep_work> XMPP bug? 15:57:15 <flo-retina> clokep_work: the stats service ranking separately each resource 15:57:26 <aleth> (and then ignoring most of them) 15:57:29 <flo-retina> (yet another normalized name issues; aleth's favorites ;)) 15:57:38 * aleth runs, hides 15:57:58 <clokep_work> :( 15:58:14 <clokep_work> aleth: Honestly, I'd love JS-Yahoo to be in this release...but if it's not...oh well. 15:58:20 <clokep_work> We aren't missing functionality or breaking UI. 15:58:50 <aleth> clokep_work: My guess would be JS-Yahoo is right now closer to being release ready than the awesometab 15:59:03 <aleth> (in terms of work remaining) 15:59:28 <aleth> But maybe it's just not been used enough :P 16:01:45 <flo-retina> I suspect neither is *currently* in a releasable state. 16:01:58 <flo-retina> I hope both could be within in a relatively short amount of time 16:02:37 <aleth> Yeah, there are no huge patches remaining for either, but it depends on how much time nhnt11 and qheaden have 16:04:59 <-- Huvik has quit (Ping timeout) 16:22:41 <clokep_work> So I have two questions: when do we want to release 1.5? Would we hold 1.5 for either of these features? 16:32:09 <instant-buildbot> build #484 of macosx-onCommit is complete: Success [build successful] Build details are at http://buildbot.instantbird.org/builders/macosx-onCommit/builds/484 16:33:39 <aleth> I had the impression the timetable was driven by wanting to do it on moz24 16:34:28 <clokep_work> OK, so then we want to release by....Oct. 29. 16:37:06 <aleth> 1.5 fixes without awesometab and yahoo https://bugzilla.instantbird.org/buglist.cgi?query_format=advanced&emailassigned_to1=1&emailtype2=notequals&list_id=5651&bug_status=RESOLVED&email2=nhnt11%40gmail.com&email1=qheaden%40phaseshiftsoftware.com&emailassigned_to2=1&target_milestone=1.5&emailtype1=notequals 16:38:28 <aleth> The problem is there is no standout feature without the gsoc stuff 16:38:45 <clokep_work> When has that stopped us before? ;) 16:38:50 <clokep_work> What's the standout feature of 1.4? 16:39:06 <aleth> I'm sure there was something to put in the blogpost ;) 16:39:40 <clokep_work> It has self-signed cert stuff and the Twitter character counter. 16:39:43 <clokep_work> Not very exciting IMO. 16:42:38 <aleth> Oct 29 minus the string freeze leaves about 5 days for deciding/landing strings... 16:45:17 <clokep_work> :) I agree. 16:45:39 <clokep_work> I started looking at OSCAR again on the plane yesterday. ;) 16:47:04 <flo-retina> so how come we managed to land so many patches without anything user visible? :-S 16:47:37 <flo-retina> I cleaned up the error console! 16:47:48 <flo-retina> (but there's now even more noise in it than before...) 16:48:26 <clokep_work> There are user visible changes. 16:48:30 <clokep_work> Participants have tooltips. 16:48:35 <clokep_work> And a few other things, I think. 16:48:38 <clokep_work> But nothing dramatic. 16:48:53 <flo-retina> this is what I currently get in there: http://i4.minus.com/i2qOuXZ4c06t5.png 16:49:31 <aleth> ().buddy is null looks like worth filing ;) 16:49:37 <clokep_work> The GTalk typing bug is pretty good fix. 16:50:28 <flo-retina> have we agreed for a fix for the this._account one? 16:50:45 <flo-retina> I would also like to get the -moz-inital one fixed 16:50:55 <aleth> Is that the one awaiting review? 16:51:08 <flo-retina> it's mac-only so I guess I'll either need to convince nhnt11 to poke at it, or fix it myself ;) 16:51:19 <flo-retina> hmm, or I think it's mac only 16:51:24 <flo-retina> I'm not sure actually :) 16:51:45 * aleth suspects nhnt11 is going to be busy enough ;) 16:52:09 <flo-retina> yeah 16:52:11 --> Mook_as has joined #instantbird 16:52:26 <flo-retina> which bug should that .buddy thing block? :) 16:53:19 <-- gerard-majax_ has quit (Ping timeout) 16:53:30 * flo-retina decides 1583 16:53:46 <instantbot> New Instantbird (UI) bug 2209 filed by email@example.com. 16:53:49 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=2209 nor, --, ---, nobody, NEW, Error: (intermediate value).buddy is null at ibConvStatsService.js:479 17:02:20 <-- flo-retina has quit (Quit: Instantbird 1.5a1pre -- http://www.instantbird.com) 17:11:12 --> Huvik has joined #instantbird 17:32:20 <-- jb1 has quit (Ping timeout) 17:32:42 --> flo-retina has joined #instantbird 17:32:42 * ChanServ sets mode +qo flo-retina flo-retina 17:33:33 <flo-retina> "potentially "bargain" to have just TB go back in." I think if we managed to be in c-c before the merge, we should push as hard as possible to avoid that. 17:34:12 <clokep_work> I agree. :) 17:34:15 <flo-retina> (as in that situation we would end up having to maintain c-c with the SeaMonkey people, who aren't very active these days; instead of relying on Tb people to do it) 17:35:18 <clokep_work> If that happened I'd say we should just pull back out and use our own repo. ;) 17:35:44 <clokep_work> (Although in that case we'd then have chat/ in m-c which would be a PITA to maintain / edit code) 17:37:27 <aleth> Since I don't know anything much about the build system and don't do the gecko updates I'll leave this decision to those who will do the work ;) 17:37:43 <aleth> I guess the question is "will this make life easier afterwards"... 17:40:20 <flo-retina> clokep_work: we may just stop supporting Tb. 17:41:32 <clokep_work> Haha. 17:42:22 <clokep_work> aleth: Right. :) Well I'd still like your opinions in the email thread. 17:42:32 <clokep_work> flo-retina: We could do that, yes. 17:51:25 --> gerard-majax_ has joined #instantbird 17:55:51 --> rosonline has joined #instantbird 17:58:56 --> jb has joined #instantbird 18:01:32 <-- jb has quit (Ping timeout) 18:06:11 <-- Huvik has quit (Ping timeout) 18:07:26 <-- gerard-majax_ has quit (Ping timeout) 18:07:56 --> Mnyromyr has joined #instantbird 18:29:41 <-- qlum has quit (Ping timeout) 18:53:32 --> StrangeCharm has joined #instantbird 19:01:25 <StrangeCharm> Hello Instantbird cadre. My name is Tom Lowenthal, and I'm the project coordinator at Tor. 19:01:41 --> unghost has joined #instantbird 19:02:03 <StrangeCharm> We have a project to produce a Tor instant messaging bundle, rather like Torbrowser. 19:02:19 <clokep_work> StrangeCharm: Hello, 19:02:38 <StrangeCharm> We think that Instantbird is probably our best place to start from. 19:03:07 <StrangeCharm> We have Opinions, and also, importantly, questions. Could I pepper y'all with some queries? 19:03:15 <clokep_work> Yes. 19:03:25 <clokep_work> I think someone peppered us already a bit, but feel free to pepper us more. ;) 19:03:37 <-- dew has quit (Ping timeout) 19:04:04 <StrangeCharm> clokep_work: Do you know who the original pepperer might have been? 19:04:25 <clokep_work> I don't even remember if it was over email or what... flo-retina aleth ^? 19:05:24 --> dew has joined #instantbird 19:05:41 <StrangeCharm> My understanding is that Instantbird currently uses libpurple as the IM component, but that you're switching to a JS IM implementation which is currently available in on of your early test builds, if you know the right about:config incantation? 19:05:44 <clokep_work> arlolra maybe? 19:05:54 <StrangeCharm> Oh excellent. 19:05:55 <clokep_work> StrangeCharm: That's not entirely true. 19:06:18 <aleth> clokep_work: I can't remember, I suspect it was here 19:06:50 <clokep_work> StrangeCharm: For IRC, GTalk, Facebook and Twitter we already use our own JS implementations. 19:07:13 <clokep_work> You can also enable JS implementations of XMPP and Yahoo/Yahoo JAPAN on our nightly builds. 19:07:26 <clokep_work> We use libpurple for any protocol not mentioned above. 19:07:33 <StrangeCharm> We're only really intrerested in XMPP. 19:07:57 <clokep_work> OK. 19:08:11 <StrangeCharm> I mean, other stuff is fine, whatever, no problem. But XMPP is our goal. 19:08:18 <clokep_work> Understood. :) 19:08:37 <StrangeCharm> We'd probably start out turning all that other stuff off. 19:08:50 <StrangeCharm> Maybe add IRC back if we're feeling bold. 19:09:20 <StrangeCharm> Okay, what's the status of that JS implementation. Is that where you're going long-term? Is it basically working right now? 19:09:25 <aleth> JS-XMPP is not the default for us because of the current lack of DNS SRV. Iirc it needs some improvements to MUC support too 19:10:07 <aleth> It's the default on TB and for the specific case of gtalk and fb (which are basically just wrappers for JS-XMPP with the servers etc predefined) 19:10:13 <clokep_work> Yes, pretty much what aleth said. MUCs mostly work, but need a bit of work. 19:10:55 <StrangeCharm> MUC is not a target for us because we don't have a good crypto solution for it. 19:11:08 <StrangeCharm> We know how to do two-party OTR right now. 19:11:09 <aleth> The fact it's not the default means it's seen less improvements than the other JS protos, but it works. 19:11:10 <clokep_work> That was kind of my assumption. 19:11:35 <clokep_work> StrangeCharm: So have you read through https://bugzilla.mozilla.org/show_bug.cgi?id=779052 btw? 19:12:07 <StrangeCharm> clokep_work: I'll look at that in a moment. 19:12:37 <flo-retina> StrangeCharm: I think the original person asking us Tor related questions was m ikeperry 19:12:40 <StrangeCharm> What's the current status with getting SRV records? Is that something Necko can do in theory? 19:13:12 <StrangeCharm> flo-retina, clokep_work: It's possible that both mikeperry and arlolra both asked things. 19:13:38 <clokep_work> Ah, yes it was Mike. :) 19:13:56 <clokep_work> StrangeCharm: Necko doesn't support them yet, I talked to the Necko guy this weekend about it and he hopes to do it soon but no "real" timeline. 19:14:24 <StrangeCharm> Well shucks. Is there a cheap hack for getting SRVs? 19:14:26 <clokep_work> Also other OTR info is in https://bugzilla.instantbird.org/show_bug.cgi?id=877 (it's annoying the bug is split...) 19:14:30 <instantbot> Bug 877 enh, --, ---, nobody, NEW, Add support for OTR and encrypted chats. 19:14:39 <clokep_work> You can apply the patch in https://bugzilla.mozilla.org/show_bug.cgi?id=14328 ? 19:14:45 <aleth> StrangeCharm: You can read up the bugzilla bug if you want to see the status quo 19:14:51 <StrangeCharm> Apart from just pinning jabber.ccc.de and riseup by their hidden servcies. Â¬_Â¬ 19:16:05 <StrangeCharm> Okay, moving on with my questions. I heard rumors of modifocations to NSS to have NSS support the OTR crypto primitives. Is that real? 19:16:07 <flo-retina> StrangeCharm: we could get DNS SRV records by doing the lookup through jsctypes. 19:16:29 <flo-retina> StrangeCharm: But I think Mike said you would want to turn SRV resolution off as it wasn't secure; or something like that. 19:16:32 <clokep_work> StrangeCharm: That's a twisting of what's happening. 19:16:47 <clokep_work> StrangeCharm: We could use NSS to implement many of the pieces of OTR. 19:17:10 <StrangeCharm> Tell me what you're thinking of. 19:17:34 <clokep_work> I don't understand the question. 19:18:28 <clokep_work> "what you're thinking of"? In what sense? 19:18:49 <StrangeCharm> What's your plan for getting OTR? What are you planning to do with NSS? 19:20:24 <clokep_work> One of the guys in #maildev has been looking at implementing it. 19:20:41 <clokep_work> We should have all the crypto stuff in NSS. 19:20:45 <clokep_work> It's just a matter of piecing them together. 19:20:54 <clokep_work> Maybe slightly modifying the chat code to handle OTR. 19:20:58 <clokep_work> And then we should be "all set". 19:21:12 <clokep_work> If that doesn't answer your question, please ask more specific ones. :) 19:22:50 --> Mic has joined #instantbird 19:22:50 * ChanServ sets mode +h Mic 19:23:08 <Mic> Hi 19:23:15 --> qlum has joined #instantbird 19:23:22 --> nhnt11 has joined #instantbird 19:23:26 <StrangeCharm> I think that's probably what I want right now. 19:23:30 <StrangeCharm> I think. 19:23:37 * StrangeCharm is also perusing these bugs. 19:23:55 <clokep_work> OK. :) 19:24:00 <clokep_work> Please let us know if you have other questions. 19:24:14 <Mic> The buglist excluding nhnt11 and qheaden is missing some bugs that weren't GSoC related but fixed by one of them anyways by the way.. 19:24:35 <Mic> Oops, sorry for pinging you, guys. 19:24:54 <StrangeCharm> Someone is going to put together an implementation plan for us. They'll probably be back with more questions. 19:25:13 <StrangeCharm> Or not. 19:25:33 <StrangeCharm> Thanks for working on Instantbird. 19:25:49 <clokep_work> StrangeCharm: OK. What other sorts of changes were you looking to make btw? Is it really just the lack of OTR support? 19:26:19 <flo-retina> StrangeCharm: OTR isn't a priority for any of the currently active developers (otherwise it would already be implemented ;)), but we are very willing to mentor new developers interested in it. 19:27:13 <clokep_work> There is someone kind of working on it now, I have no idea of how quickly he will make progress, of course. 19:27:38 <flo-retina> clokep_work: that someone needs mentoring, doesn't he? 19:28:41 <StrangeCharm> We are looking to make a usable (widely, in many languages), secure (against remote exploits), cross-platform (Windows, OSX, Linux), privacy-preserving (all traffic over Tor, like Torbroswer), encrypted (all conversations, by default) IM app. 19:29:24 <StrangeCharm> OTR is one major thing. 19:29:35 <StrangeCharm> We also want not to be readily exploitable. 19:30:10 <StrangeCharm> We need to have a GUI which we can ealiy translate into many languages, and we have translators for our key ones. 19:30:23 <clokep_work> OK, would you be contributing those translations back? 19:31:04 <StrangeCharm> Probably. Right now, I don't know how forky we need to be, and I'm not really on top of our translation infra. 19:31:13 <flo-retina> will you be in Paris next summer? 19:31:14 <StrangeCharm> I don't know how many string changes we'd need. 19:31:30 <StrangeCharm> flo-retina: Was that question for me? 19:31:39 <flo-retina> yes, I think you are planning a work week there. 19:32:08 <StrangeCharm> Oh. If there's a Tor dev meeting, I'll definitely be there. 19:32:18 <StrangeCharm> I didn't know that next summer's was in Paris and already planned. 19:32:38 <flo-retina> well, I don't think it's "already planned" 19:33:07 <flo-retina> I just saw some emails mentioning it. 19:33:10 <nhnt11> Mic, flo-retina, aleth: Er, I'm a little embarrassed to ask this, but is there any particular bug that I should look at first? I'm guessing the XMPP resource one and/or bug 2200? 19:33:14 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=2200 nor, --, ---, nobody, NEW, Use a conversation's statusType for ranking 19:33:20 <clokep_work> Well I greatly dislike forking so forkign as little as possible would be desirable for me. :) 19:33:33 <clokep_work> nhnt11: XMPP resource one IMO. 19:33:35 <nhnt11> (I'm really tired and can't really think about which one to take a crack at now) 19:34:00 <aleth> nhnt11: xmpp and/or tweaking the ranking ;) 19:34:11 <aleth> Maybe you need that etherpad to decide what to do first ;) 19:34:18 <nhnt11> Yeah 19:34:22 * clokep_work plans to force nhnt11 to fix our normalized names. :P 19:34:25 <clokep_work> (I'm kidding.) 19:34:45 <StrangeCharm> Okay, that's all from me for now. 19:34:54 <StrangeCharm> Thanks for being so responsive! 19:35:17 <qheaden> Hello. 19:35:28 <flo-retina> nhnt11: I would say whatever is likely to give us soon realistic results when opening the tab ;) 19:35:39 <flo-retina> so something that wouldn't cause most of the first results to be channels would help 19:35:47 <qheaden> clokep_work: I'm going to work on JS-Yahoo a bit today. I finally have some time. :) 19:35:55 <nhnt11> aleth: What surprises me about the xmpp resources is that these can't be from log crawling (unless there's a serious bug in the log crawling code) 19:36:11 <nhnt11> I don't think the resource is included in the log header.. or is it 19:36:13 <flo-retina> nhnt11: well, you need to at least find where they are coming from 19:36:15 <aleth> nhnt11: can you reproduce? 19:36:28 <nhnt11> I never noticed anything like that from all the times I inspected the json file 19:36:31 <nhnt11> let me check again though 19:36:32 <flo-retina> nhnt11: I suspect the usernames inside each logged XMPP message contains the resource 19:36:46 <flo-retina> nhnt11: so you may be using the message usernames instead of the username in the conversation header 19:36:47 <nhnt11> flo-retina: But the log crawling code doesn't obtain the account from the messages 19:36:51 <flo-retina> that would be strange though :-S 19:36:53 <aleth> You could compare your add-on with the current code as the results are significantly different 19:37:05 <flo-retina> oh, it's the account that has resources? I thought it was the contacts 19:37:16 <nhnt11> Uh 19:37:19 <nhnt11> Wait 19:37:30 <nhnt11> Er, whichever it is 19:37:33 <nhnt11> I'm mixing up the names a bit 19:37:39 <nhnt11> (bah) 19:38:04 <nhnt11> the thing is, the account, protocol and name are all obtained from the header 19:38:06 <nhnt11> of the log file 19:38:39 <aleth> http://lxr.instantbird.org/instantbird/source/instantbird/components/ibConvStatsService.js#470 19:39:21 <nhnt11> aleth: That's what made me suspect the account 19:39:28 <nhnt11> We're not using the normalizedName there 19:39:46 <clokep_work> qheaden: I'd appreciate if you could check out that review I tossed toward you. 19:39:48 <nhnt11> But a resource for an account doesn't really make sense 19:39:54 <qheaden> OKay. 19:39:56 <aleth> It's not the account in my JSON 19:40:41 <nhnt11> aleth: My json file looks fine :-/ 19:40:58 <nhnt11> The only XMPP accounts I have are gtalk and facebook though 19:42:04 <aleth> The most obvious case I have is a gmail contact which has lots of gmail.2FE86893 type resources 19:42:57 --> EionRobb has joined #instantbird 19:44:52 --> kkirill has joined #instantbird 19:44:59 <-- kkirill has quit (Quit: kkirill) 19:45:01 <aleth> You are getting that from the name in the header. It's no mystery. 19:45:02 --> kkirill has joined #instantbird 19:45:10 <flo-retina> nhnt11: well, account names could contain a resource. But then they would contain it all the time, so it shouldn't be a problem 19:45:20 <-- kkirill has quit (Quit: Instantbird 1.5a1pre -- http://www.instantbird.com) 19:45:20 <instantbot> firstname.lastname@example.org granted review for attachment 2926 on bug 2159. 19:45:22 --> kkirill has joined #instantbird 19:45:22 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=2159 nor, --, ---, clokep, ASSI, Port |Bug 884319 - Add http.jsm to toolkit for usage by Thunderbird FileLink, Lightning and Instantb 19:45:31 * qheaden feels weird giving an r+ to clokep_work 19:45:47 <aleth> qheaden: get used to it, you own the yahoo code ;) 19:45:47 <flo-retina> qheaden: you'll get used to it 19:45:53 <qheaden> :P 19:45:58 <flo-retina> qheaden: but you also should give him a few r- ;) 19:46:04 <qheaden> lol 19:46:20 <flo-retina> just to show us you are actually looking at the code ;) 19:47:03 <nhnt11> aleth, flo-retina: Ok, so I've decided I can't really wrap my head around the xmpp problem at the moment 19:47:31 <nhnt11> I'll upload a patch (or two) for bug 2200 though, and maybe we can see if results get better 19:47:34 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=2200 nor, --, ---, nobody, NEW, Use a conversation's statusType for ranking 19:48:00 <clokep_work> Thanks qheaden . :) 19:48:29 <qheaden> No prob. 19:48:47 * qheaden feels good to get back to Ib development again. I was missing it. 19:49:11 <qheaden> Been doing mostly system admin/networking projects at my job. But I love programming. :) 19:58:11 <-- aleth has quit (Quit: Ciao) 20:01:20 <-- dew has quit (Connection reset by peer) 20:03:02 --> dew has joined #instantbird 20:03:07 --> aleth has joined #instantbird 20:03:08 * ChanServ sets mode +h aleth 20:03:52 <aleth> flo-retina: did you file those bugs for yoric? 20:03:59 <flo-retina> no :( 20:04:11 <flo-retina> I haven't done any of the summit follow-up emails yet 20:06:29 <clokep_work> Which bugs are these? 20:07:53 <flo-retina> clokep_work: enhancements to the platform to let us do our long operations in chunks in a way that doesn't cause jank 20:08:30 <flo-retina> clokep_work: basically, a solution more reliable than just doing stuff for an arbitrary number of ms like we currently do. 20:14:15 <clokep_work> Ah, cool. :) What kind of change did Yoric think that would be? 20:14:27 <clokep_work> I'm surprised they didn't just say "use a worker" 20:18:41 <-- nhnt11 has quit (Quit: Instantbird 1.5a1pre -- http://www.instantbird.com) 20:18:50 --> nhnt11 has joined #instantbird 20:22:24 <-- nhnt11 has quit (Quit: Instantbird 1.5a1pre -- http://www.instantbird.com) 20:22:40 --> nhnt11 has joined #instantbird 20:25:25 <flo-retina> clokep_work: so we just said what we want, and he replied to file bugs so that he can investigate the best way to handle it 20:25:43 <flo-retina> clokep_work: worker can't access the DOM, so that doesn't solve the problem 20:25:52 <flo-retina> *workers 20:25:53 <clokep_work> Oooo, I see. 20:25:55 <clokep_work> Cool. :) 20:26:09 <-- nhnt11 has quit (Quit: Instantbird 1.5a1pre -- http://www.instantbird.com) 20:26:21 --> nhnt11 has joined #instantbird 20:26:25 <flo-retina> some of the stats service stuff should likely use a worker 20:27:39 <aleth> We could have used promises instead of callbacks for LIST too ;) 20:27:53 <aleth> Hmm... maybe not 20:28:14 <-- nhnt11 has left #instantbird () 20:28:15 <flo-retina> I thought that too 20:28:20 --> nhnt11 has joined #instantbird 20:28:42 <flo-retina> but then we need that platform support _again_ 20:28:51 <flo-retina> aleth: we could have used Task.js for the log crawling though 20:29:16 <flo-retina> and guess what, we need the same stuff again ;) 20:29:29 <aleth> Right, thought JSON.parse would be sync no matter when it was done 20:29:37 <aleth> s/thought/though 20:29:43 <flo-retina> how is that a problem? 20:29:54 <flo-retina> we could yield after each message 20:30:28 <aleth> Oh, I forgot he parsed individual messages. Then... sure! 20:31:17 <aleth> It's the stats json that is one big lump. 20:31:35 <flo-retina> is it really that big? 20:32:02 <aleth> well, mine is 24K 20:32:11 <flo-retina> that's small 20:32:12 <aleth> So not that much I guess. 20:32:17 <nhnt11> Mine is 18K 20:32:21 <flo-retina> I don't see how that could take 15+ms to parse ;) 20:32:31 <-- nhnt11 has quit (Quit: Instantbird 1.5a1pre -- http://www.instantbird.com) 20:32:35 --> nhnt11 has joined #instantbird 20:32:46 <aleth> It must be something else causing the 10K strings I see in about:memory ;) 20:33:02 <flo-retina> what do they start with? 20:33:10 <nhnt11> I'm about to upload a patch to bug 2200 20:33:14 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=2200 nor, --, ---, nobody, NEW, Use a conversation's statusType for ranking 20:33:18 <aleth> It's JSON, first item is start:... 20:33:20 <nhnt11> the code isn't very polished, but the results seem better to me. 20:35:19 <flo-retina> aleth: I don't have any JSON in the huge strings here 20:35:50 <aleth> If it showed the whole thing it would be easier to identify 20:36:21 <flo-retina> I wonder how much debug logs are responsible for our memory usage in JS prpls 20:36:33 <flo-retina> maybe we should make the memory pressure notification clear all the debug logs? 20:36:53 <instantbot> New Instantbird (UI) bug 2210 filed by email@example.com. 20:36:56 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=2210 nor, --, ---, nobody, NEW, XMPP buddies with changing resource don't get their stats counted correctly 20:37:16 <flo-retina> I've got 4 4k strings that are definitely raw XMPP exchanges 20:38:02 <aleth> Maybe we should discard the debug log entries over the maxnum on the fly, that would limit the size 20:39:19 <aleth> (if we don't already) 20:40:21 <flo-retina> what does that mean? 20:41:03 <flo-retina> see http://lxr.instantbird.org/instantbird/source/chat/components/src/imAccounts.js#301 20:41:21 <aleth> So we do do it already ;) 20:41:26 <flo-retina> I guess it doesn't help my memory usage that I've set that pref to 2000 ;) 20:45:40 <nhnt11> aleth, flo-retina: Do we want to give existing convs in general a negative bias or just existing chats? 20:45:50 <-- dew has quit (Ping timeout) 20:45:50 <-- Mic has quit (Quit: Instantbird -- http://www.instantbird.com) 20:45:59 --> dew has joined #instantbird 20:46:54 --> Mic has joined #instantbird 20:46:54 * ChanServ sets mode +h Mic 20:47:22 <flo-retina> nhnt11: or just chats? 20:47:28 <flo-retina> whether they exist or not? 20:48:07 <nhnt11> I'd say we keep just chats how they are, boost contacts a bit based on availability, and bring existing chats a bit down 20:48:19 <nhnt11> (or all existing convs) 20:48:28 <aleth> Contacts, offline contacts you can send to, chats based on stats, then other offline contacts? 20:48:45 <nhnt11> Do we want all contacts to come before chats? 20:48:49 <flo-retina> i'm also surprised by the ranking of chats. 2 out of the 6 first chats are private chats where I barely talked in the past, and that are dead now 20:48:55 <aleth> That's what I'm asking 20:49:16 <nhnt11> flo-retina, aleth: Do you have time to try out my patch now? 20:49:21 <flo-retina> nhnt11: not all contacts. But the contacts that have a high frecency score should be before chats, even if away/mobile 20:49:29 <nhnt11> yeah 20:49:51 <nhnt11> Let me upload that patch and you can see if you think my multipliers make sense 20:49:57 <Mic> I've got someone (a contact on Facebook) appearing five times in the list :S 20:50:04 <nhnt11> Mic: I thought I fixed that bug 20:50:12 <nhnt11> bug 2201 20:50:15 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=2201 nor, --, 1.5, nhnt11, RESO FIXED, Duplicate items in the new conversation tab 20:50:19 <aleth> I've also got some strange chat ranking, #maildev is way down despite being on my autojoin list so it should have a high score 20:50:44 <aleth> Mic: Possibly bug 2210 20:50:47 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=2210 nor, --, ---, nobody, NEW, XMPP buddies with changing resource don't get their stats counted correctly 20:51:06 <nhnt11> I would think that auto join implies you're less likely to want to open it using the awesometab? 20:51:27 <-- nhnt11 has quit (Quit: Instantbird 1.5a1pre -- http://www.instantbird.com) 20:51:35 --> nhnt11 has joined #instantbird 20:51:44 <aleth> nhnt11: Maybe, but you're not taking account of that yet, so it shouldnt be happening 20:51:58 <aleth> I also see a bunch of offline contacts followed by some online available ones, which is weird 20:52:11 <aleth> (if I understand your sort algorithm correctly) 20:53:18 <nhnt11> Those available ones should be ones without stats... 20:53:20 <nhnt11> :( 20:53:26 <-- nhnt11 has quit (Quit: Instantbird 1.5a1pre -- http://www.instantbird.com) 20:53:35 --> nhnt11 has joined #instantbird 20:54:13 <aleth> I doubt I have never talked to Mic :-/ 20:54:18 <aleth> Yeah, there are logs. 20:54:24 <aleth> So there should be stats. 20:54:38 * nhnt11 is puzzled 20:54:49 <nhnt11> I don't see such anomalies here... 20:55:12 <aleth> Maybe your algorithm (based on the addon) was good, but there is a bug that is messing things up, so I am seeing something else 20:55:44 <aleth> aha! 20:55:58 * nhnt11 waits intently 20:56:16 <aleth> I think I may know what it is. Let me check 20:57:37 <aleth> Right, the context menu on Mic doesn't find the logs either. 20:58:05 <aleth> So it's bug 2115 combined with bug 1454 20:58:12 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=2115 nor, --, ---, nobody, NEW, Provide a way to obtain the normalizedName of a nick 20:58:13 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=1454 nor, --, ---, clokep, ASSI, normalizedName for JS-IRC is wrong 20:58:48 <aleth> The log folder name is mic (lowercase) and the nick is uppercase. 20:58:53 <clokep_work> Doesn't surprise me. ;) 20:58:58 <clokep_work> Isn't bug 1454 mostly fixed? 20:59:00 <clokep_work> What's left? 20:59:05 <nhnt11> Yay 20:59:11 <nhnt11> So it's not (technically) an awesomebug 20:59:12 <nhnt11> :D 20:59:29 <aleth> nhnt11: Maybe... you may not be being consistent ;) see XMPP 20:59:49 <nhnt11> clokep_work, aleth: When we land those normalizedName changes, we likely want to up the stats cache version to force a resweep of the logs 21:00:02 <nhnt11> I'll add that as a comment on those bugs.. 21:00:04 <flo-retina> aleth: I think we should give you a normalized quota, saying that you aren't allowed to mention more than one normalized* bug per day ;). 21:00:45 <aleth> My ranking is not normalized correctly :P 21:01:29 <flo-retina> nhnt11: "I would think that auto join implies you're less likely to want to open it using the awesometab?" auto-join with a conv on hold implies that want to have context whenever I open that channel; so I think I'm actually way more likely to want to open it. 21:01:37 <instantbot> firstname.lastname@example.org requested review from email@example.com rg for attachment 2933 on bug 2200. 21:01:40 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=2200 nor, --, ---, nhnt11, ASSI, Use a conversation's statusType for ranking 21:01:45 <aleth> nhnt11: If you can work around those two bugs to fix this that would be helpful. 21:02:18 <flo-retina> and now we get normalized workarounds? :-o 21:02:28 * nhnt11 will look into it tomorrow 21:02:45 <aleth> No, I just mean that if it is possible to be consistent in the names he is using for id's there should not be a problem 21:04:08 * flo-retina was just kidding 21:05:43 <nhnt11> aleth: I'm using normalizedName everywhere 21:05:50 <nhnt11> (am I not?) 21:06:16 <aleth> nhnt11: It's like the XMPP bug. I doubt it even needs filing separately. Did you read my comment? 21:07:31 <aleth> Well, possibly a bit different. I suspect in this case the name from the logs is Mic and the normalizedName is mic 21:09:13 <nhnt11> aleth: The headers on my gtalk logs don't contain the resource in the name 21:09:22 <nhnt11> The individual messages do though, but I don't see how that matters 21:09:40 <aleth> nhnt11: Are you using JS-XMPP 21:10:01 <nhnt11> Yes 21:10:15 <nhnt11> (I created the account as "GTalk" which uses js-xmpp by default, no?) 21:10:22 <aleth> I'm not ;) Maybe that's it? 21:10:30 <nhnt11> Ah 21:10:36 <nhnt11> bah. 21:10:38 <flo-retina> aah! 21:10:38 <aleth> I have those contacts listed via xmpp federation 21:11:05 <nhnt11> aleth: But the log folder names are fine? 21:11:14 <aleth> nhnt11: Yes, just one log folder. 21:11:17 <nhnt11> (In that case, I can just use the log folder name for the account name) 21:11:23 <nhnt11> oh wait 21:11:28 <nhnt11> We're not talking about the account 21:11:32 <nhnt11> damn it 21:11:35 * nhnt11 is tired 21:11:41 <aleth> buddies have log folders too ;) 21:11:43 <aleth> It might work. 21:11:59 <aleth> That's what I meant about being consistent, you have to trace where those names come from in the code. 21:12:09 <nhnt11> wait that's what made me think of that in the first place, but then I was focused on an emtpy account folder which made me think we don't have buddy folders 21:12:17 <nhnt11> yeah 21:12:23 <aleth> It's not that you're tired, it's that normalizedMess makes you tired ;) 21:12:25 <nhnt11> Ok so at least we know what's going on now 21:12:46 <flo-retina> hmm, aren't the folder names mangled to avoid some special characters? 21:12:53 <clokep_work> Yes. 21:13:07 <clokep_work> The log code should handle that for you. 21:13:09 <aleth> Taht's where the lowercase is coming from. 21:13:36 <flo-retina> clokep_work: yeah, my point is that using the folder name as if it was the name normalized by the prpl may not work 21:13:48 <nhnt11> Bah :/ 21:14:06 <clokep_work> That shouldn't work at all...use a name that has % thrown in there. 21:14:42 <nhnt11> So maybe I should be trying to normalize a normalizedName? :P 21:15:24 <nhnt11> I'll look at how these names are set in the code tomorrow 21:15:26 <flo-retina> nhnt11: ssssh, aleth is reading ;) 21:15:43 <aleth> Yeah, better do it when you are refreshed and have coffee nearby ;) 21:15:53 <flo-retina> :) 21:16:12 <clokep_work> s/coffee/alcohol/ 21:16:15 <clokep_work> ;) 21:16:23 <Mic> Regarding the encoded file names: I think I insisted that the encoding is reversible. 21:16:28 <flo-retina> I was surprised nothing stronger than coffee had been suggested 21:16:33 <nhnt11> flo-retina, aleth, Mic: Any chance you'll have feedback on bug 2200 within the next ~10 minutes? 21:16:37 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=2200 nor, --, ---, nhnt11, ASSI, Use a conversation's statusType for ranking 21:16:40 <Mic> nhnt11: no 21:16:43 <flo-retina> Mic: but it's not applied for old logs ;) 21:17:03 <flo-retina> nhnt11: aleth may have :) 21:17:08 <flo-retina> I likely won't 21:17:12 <aleth> Mic: also bug 1983 21:17:16 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=1983 nor, --, ---, nobody, NEW, Default normalizedName normalization is too aggressive 21:17:46 * nhnt11 wonders if we can just hash names for normalization purposes 21:17:54 <flo-retina> nhnt11: I looked enough to dechide I don't understand that code, and will need to reread the surrounding code before having an opinion. 21:18:17 <flo-retina> nhnt11: no :) 21:18:43 <Mic> nhnt11: how would you make sure that you get the same hash all the time? 21:19:01 <flo-retina> Mic: by hashing the normalized name ;) 21:19:04 <Mic> By making sure the name is normalized properly before hashing it maybe ;) 21:19:07 <nhnt11> Why would a hash changed? 21:19:09 <nhnt11> change8 21:19:10 <nhnt11> * 21:19:25 <nhnt11> Oh, the resource 21:19:32 * nhnt11 sighs 21:19:46 <flo-retina> nhnt11: Mic and mic likely won't produce the same hash for most hash functions ;) 21:20:15 <nhnt11> flo-retina: I was mainly thinking about the problem of eliminating special chars 21:20:33 <nhnt11> But I guess I don't really understand the full scope of the normalization stuff so... 21:21:27 <aleth> nhnt11: why did you drop the continue;'s? 21:21:41 <nhnt11> aleth: To make existing convs get ranked separately 21:21:45 <flo-retina> ah, I knew aleth would have some feedback! \o/ 21:21:58 <nhnt11> (with the continue;'s, they just took the place of the PossibleConv) 21:22:33 <-- Mnyromyr has quit (Quit: ChatZilla 0.9.86 [SeaMonkey 1.1.19/2010030105]) 21:23:02 <nhnt11> (the splicing now only removes the conv without inserting the existingConv in its place) 21:23:11 <aleth> nhnt11: btw the normalized stuff is documented in this patch https://bugzilla.instantbird.org/attachment.cgi?id=2456&action=diff which hasn't landed yet 21:23:32 <aleth> (it adds comments) 21:23:52 <nhnt11> aleth: Thanks 21:23:54 --> Huvik has joined #instantbird 21:24:45 <aleth> I don't think I can finish reviewing this patch in the next 2 mins (which is all I have time for) 21:24:47 <aleth> sorry 21:24:55 <nhnt11> sure :) 21:25:13 <nhnt11> I think that patch is a bit too lenient with offline contacts 21:26:25 <-- aleth has quit (Quit: Ciao) 21:28:10 <nhnt11> Odd though, seeing as offline contacts are given a 0.5 multiplier 21:28:53 <nhnt11> Maybe it's just that I talk so often with people currently offline that they appear near the top anyway 21:30:24 <-- nhnt11 has quit (Quit: Instantbird 1.5a1pre -- http://www.instantbird.com) 21:30:30 --> nhnt11 has joined #instantbird 21:30:34 <nhnt11> Good night. 21:31:58 <-- kkirill has quit (Quit: Instantbird 1.5a1pre -- http://www.instantbird.com) 21:32:40 <mikeperry> are there prefs to disable all HTML in chat windows, if one wanted to reduce that vulnerability surface? 21:32:57 <mikeperry> for ex, similar to how Thunderbird can disable all html for mail display 21:33:55 <Mic> mikeperry: you're talking about filtering things from the messages most likely? 21:34:08 <mikeperry> well I saw the contentsink filter 21:34:33 <mikeperry> but I am wondering about disabling all ways to render html elements with or without said filter... for defense in depth 21:34:58 <mikeperry> or at least ways to disable things like JS, images, CSS, etc in the chat window 21:35:22 <Mic> The themes are HTML templates. 21:35:48 <Mic> Is something wrong with the filter? 21:36:35 <Mic> flo-retina: imContentSink is in /chat, did it get a security review maybe? 21:36:35 <mikeperry> nothing obvious... we're just discussing ways of reducing the vulnerability surface in #tor-dev 21:38:19 <flo-retina> Mic: I think it did. 21:39:00 <flo-retina> which irc network? 21:39:21 <mikeperry> irc.oftc.net (port 6697 is ssl) 21:40:13 <flo-retina> is the cert self signed? 21:40:54 <flo-retina> hmm, doesn't seem so 21:41:33 <mikeperry> might be cacert.. I forget 21:43:02 <flo-retina> the server doesn't seem to like me 21:45:38 <flo-retina> mikeperry: "disable things like JS, images, CSS, etc in the chat window" Did you mean incoming JS/images/CSS? 21:45:56 <clokep_work> You can disable incoming formatting. 21:45:58 <flo-retina> they are all disabled by default 21:46:36 <flo-retina> do we have a pref to disable _automatic_ /formatting/ of *plain* |text| messages? 21:46:58 <clokep_work> No. :) 21:47:10 <clokep_work> But if you disable all formatting it might go away. 21:47:13 <flo-retina> IIRC the mozilla security team frowned upon that specific piece of code, so if I wanted to reduce the attack surface, it's the first thing I would want to turn off. 21:47:33 <clokep_work> BenB's code?! 21:47:35 <flo-retina> clokep_work: no, I meant a way to not make the incoming data from the network go through that piece of code; 21:47:40 <flo-retina> clokep_work: exactly! 21:47:55 * clokep_work wonders why they were concerned about that. 21:48:21 <flo-retina> clokep_work: I can cc you on the relevant security bug if you want 21:48:38 <clokep_work> Sure. :) 21:49:58 <clokep_work> mikeperry: You could just sanitize all HTML out of messages though, but most of the theming is from IB, not from remote locations. 21:50:31 <flo-retina> clokep_work: done 21:50:49 <mikeperry> flo-retina: what is that bug #? 21:50:59 <flo-retina> mikeperry: are you in the mozilla security group? 21:51:10 <clokep_work> Thanks. 21:51:51 <mikeperry> flo-retina: yes 21:52:06 <mikeperry> I am on the list anyway 21:52:16 <mikeperry> not sure if they gave me magic bugzilla privs as part of that yet or not 21:52:21 <flo-retina> mikeperry: 727216 21:53:06 <mikeperry> looks like no magic bugzilla privs for me yet 21:54:16 <qheaden> clokep_work: In bug 2199, was the account trying to reconnect when you clicked "Disconnect"? 21:54:19 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=2199 nor, --, ---, nobody, NEW, Disconnect doesn't cancel connect 21:55:25 <clokep_work> flo-retina: Gross. Sounds like we should replace that code. 21:55:44 <clokep_work> qheaden: Yes. 21:56:15 <qheaden> clokep_work: I think that is a core issue. I remember something similar happening to me on my GTalk account./ 21:56:32 <flo-retina> clokep_work: we should replace it because it's crappy. 21:57:12 <flo-retina> clokep_work: but I don't think any of the stuff discovered by the security team was exploitable (if it was we wouldn't have shipped it in Tb :)) 21:57:58 <flo-retina> but still, if I wanted to make the security level go from "above average" to "paranoid", it's the first stuff I would poke at ;). 21:58:16 <clokep_work> qheaden: I was able to disconnect ALL my other accounts. 21:58:30 <clokep_work> flo-retina: We should replace it w/ the twitter stuff we have already, I think? 21:58:41 <qheaden> clokep_work: Hmm okay. I'll see if I can reproduce it. 21:59:01 <flo-retina> clokep_work: it won't cover _*|/ magic though ;) 21:59:18 <clokep_work> True. 21:59:20 <flo-retina> and the security people weren't thrilled with the idea of using regexps 22:00:43 <flo-retina> they said the regexp engined had been exploited a few times in the past, and isn't a great choice to sanitize untrusted data or something like that. 22:01:00 <flo-retina> *engine 22:01:40 <flo-retina> "had been exploited a few times in the past" hmm not sure actually. Maybe they just said it has a large attack surface. 22:03:02 <clokep_work> Weird. 22:06:59 <-- Huvik has quit (Ping timeout) 22:08:50 <-- Mic has quit (Quit: Instantbird -- http://www.instantbird.com) 22:12:34 <-- nhnt11 has quit (Ping timeout) 22:30:26 <-- chrisccoulson has quit (Quit: OSError: [Errno 130] Owner died) 22:39:36 <-- unghost has quit (Input/output error) 23:01:16 --> chrisccoulson has joined #instantbird 23:17:17 <-- qlum has quit (Quit: Getting the <censored> out.) 23:59:23 <instant-buildbot> build #482 of linux-onCommit is complete: Success [build successful] Build details are at http://buildbot.instantbird.org/builders/linux-onCommit/builds/482