#instantbird log on 07 29 2013

All times are UTC.

00:22:16 <-- rosonline has quit (Quit: Instantbird 1.4 -- http://www.instantbird.com)
00:27:13 <-- wnayes has quit (Ping timeout)
00:31:09 --> EionRobb has joined #instantbird
00:31:14 --> wnayes has joined #instantbird
00:34:11 <-- EionRobb has quit (Connection reset by peer)
00:34:18 --> EionRobb has joined #instantbird
01:24:30 <-- mpmc has quit (Quit: Instantbird 1.5a1pre -- http://www.instantbird.com)
01:39:31 --> jb has joined #instantbird
01:52:45 --> clokep has joined #instantbird
01:52:45 * ChanServ sets mode +o clokep 
01:55:49 <-- jb has quit (Connection reset by peer)
01:56:27 --> jb has joined #instantbird
02:02:46 --> dew has joined #instantbird
02:27:00 <-- wnayes has quit (Ping timeout)
02:28:36 <-- clokep has quit (Quit: Instantbird 1.5a1pre -- http://www.instantbird.com)
02:30:40 --> wnayes has joined #instantbird
02:46:37 <-- jb has quit (Ping timeout)
03:04:18 <instant-buildbot> build #924 of linux-nightly-default is complete: Success [build successful]  Build details are at http://buildbot.instantbird.org/builders/linux-nightly-default/builds/924
03:09:52 <-- wnayes has quit (Quit: wnayes)
03:36:20 <instant-buildbot> build #924 of macosx-nightly-default is complete: Failure [failed shell_3]  Build details are at http://buildbot.instantbird.org/builders/macosx-nightly-default/builds/924
04:18:35 <-- EionRobb has quit (Quit: Leaving.)
05:04:52 <-- Mook has quit (Quit: Mook)
05:22:06 --> FireFly_TB has joined #instantbird
05:52:20 <instant-buildbot> build #1020 of win32-nightly-default is complete: Success [build successful]  Build details are at http://buildbot.instantbird.org/builders/win32-nightly-default/builds/1020
05:54:04 <-- FireFly_TB has quit (Ping timeout)
05:54:23 --> FireFly_TB has joined #instantbird
05:56:53 <-- FireFly_TB has quit (Ping timeout)
05:59:09 --> FireFly_TB has joined #instantbird
06:07:49 <-- FireFly_TB has quit (Ping timeout)
06:12:09 --> FireFly_TB has joined #instantbird
06:18:55 --> mpmc has joined #instantbird
06:45:49 <-- FireFly_TB has quit (Quit: FireFly_TB)
07:03:35 --> Tonnes has joined #instantbird
07:17:55 --> FireFly_TB has joined #instantbird
07:19:39 <-- FireFly_TB has quit (Ping timeout)
08:10:47 --> Mic has joined #instantbird
08:10:47 * ChanServ sets mode +h Mic 
08:11:12 <Mic> Good morning
08:22:18 <-- Mic has quit (Quit: Instantbird -- http://www.instantbird.com)
09:27:21 --> aleth has joined #instantbird
09:27:21 * ChanServ sets mode +h aleth 
09:56:54 --> Mic has joined #instantbird
09:56:54 * ChanServ sets mode +h Mic 
10:21:03 <-- Tonnes has quit (Ping timeout)
10:22:50 --> Tonnes has joined #instantbird
10:27:15 --> atuljangra has joined #instantbird
10:28:40 <atuljangra> aleth: Mic I wanted to know your opinions on the file transfer start/end ui. Do we like notification for some time interval in the conversation window? 
10:30:45 <aleth> atuljangra: I don't understand - can you explain in more detail?
10:32:39 <atuljangra> aleth: When a file transfer is started on the sender side, we want to inform the user about that somehow. So what should be the appropriate UI for that?
10:33:03 <aleth> atuljangra: How about a notification bar, a bit like https://support.mozillamessaging.com/media/uploads/gallery/images/2012-08-24-14-02-35-1c9f4c.png
10:33:53 <atuljangra> aleth: Seems cool. So it will be a notification bar, with no buttons?
10:34:02 <aleth> By the way, that particular notification bar might be exactly what you need for "This file transfer seems to be taking too long. It might be better to use Filelink instead." ;)
10:34:17 <aleth> atuljangra: Wouldn't you want an accept button and a reject button?
10:34:23 <atuljangra> aleth: Yess ++
10:34:34 <aleth> Oh sorry, is this for the sender or for the receiver?
10:34:46 <atuljangra> aleth: Yes, that's for receiver side. I need for sender
10:35:15 <aleth> When the sender starts a file transfer, I don't think we'll need extra notification. It will show up in the download/upload panel after all.
10:35:50 <atuljangra> Okay, and when the file tranfer finishes? (on sender and receiver side)
10:36:27 <aleth> How about just copying what FX does for downloads?
10:37:18 <atuljangra> You mean, some sort of highlighting of the array icon?
10:37:43 <aleth> Well, you haven't got the download panel added yet, so I guess what I'm saying is "leave it for later until you do" ;)
10:38:01 <aleth> Or add the panel now if you like :D
10:39:00 <atuljangra> aleth: yes. :D
10:39:02 <aleth> Also, for debugging purposes, the prpl file transfer code should log what it is doing (transfer started/incoming transfer accepted/...) in the usual way to the debug log. Ask if you don't know how to do that.
10:39:03 <Mic> Hi
10:39:23 <atuljangra> aleth: Okay I'll add that.
10:39:25 <atuljangra> Hi Mic  :)
10:39:30 <Mic> Unfortunately I need to go for the afternoon (just had lunch and missed your discussion).
10:39:44 <atuljangra> Mic: No pbm.
10:39:55 <Mic> I'll gladly provide feedback in the evening but I really need to go now.
10:40:03 <atuljangra> Mic:  BBye :-)
10:41:32 <aleth> atuljangra: Before you add the download panel, it might be a good idea to finish the Filelink UI
10:41:48 <aleth> (the preferences pane and the notification bars)
10:42:24 <atuljangra> aleth: Yes, I was thinking of landing the filelink first and then separately handling the progress bar and download panel.  
10:42:34 <atuljangra> I recall this from the Mopad.
10:42:37 <aleth> So that that part is done and can be reviewed and hopefully land soon when flo gets back
10:42:49 <aleth> Great :)
10:42:50 <atuljangra> aleth: Agreed.
10:42:55 <atuljangra> :)
10:43:00 <-- Mic has quit (Quit: Instantbird -- http://www.instantbird.com)
10:43:36 <atuljangra> Do I need to write daily progress mail now also? As we are tracking progress through the mopad.
10:43:45 <atuljangra> https://etherpad.mozilla.org/filelink
10:44:01 <aleth> atuljangra: it would be a very good idea to write daily logs on your blog or per email
10:44:12 <atuljangra> aleth: Okay. :)
10:45:11 <aleth> Nothing long, look at qheaden's for example.
10:45:20 <aleth> Short but explicit.
10:45:36 <atuljangra> aleth:  Okay. I'll stick with daily email. :)
10:57:51 <aleth> atuljangra: I have a question about your current code flow
11:05:17 <aleth> atuljangra: Are you still around?
11:06:05 <atuljangra> aleth: I've a class to attend. I'll be back in 2 hours.
11:06:07 <atuljangra> Sorry
11:06:20 <aleth> :-/
11:06:27 <atuljangra> :(
11:06:27 <aleth> OK...
11:06:37 <-- atuljangra has quit (Quit: http://www.mibbit.com ajax IRC Client)
11:36:50 <instantbot> New Core - Yahoo! Messenger bug 2079 filed by aleth@instantbird.org.
11:36:52 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=2079 nor, --, ---, nobody, NEW, JS-Yahoo has no protocol icon
11:50:57 <-- mpmc has quit (Connection reset by peer)
11:53:23 --> mpmc has joined #instantbird
12:07:30 --> jb has joined #instantbird
12:12:02 --> clokep_ has joined #instantbird
12:14:48 <-- jb has quit (Quit: jb)
12:31:18 --> jb has joined #instantbird
12:34:32 <-- clokep_ has quit (Quit: http://www.mibbit.com ajax IRC Client)
12:47:30 --> clokep_ has joined #instantbird
12:49:11 <clokep_> So everything is working OK again?
12:50:04 <aleth> In the nightlies? Yes.
12:50:30 <aleth> Apart from the filed bugs of course ;)
12:50:49 <clokep_> Good. :)
13:09:20 <-- jb has quit (Connection reset by peer)
13:09:27 --> jb has joined #instantbird
13:10:30 <clokep_> Could someone maybe go through the mailing list and approve/not approve all the stuff we've gotten the past four days or so? If not I'll try to do it tonight.
13:10:36 <clokep_> I think we also have a few unanswered support requests. :(
13:11:05 --> jb1 has joined #instantbird
13:11:32 <-- jb has quit (Connection reset by peer)
13:16:02 * qheaden_away is now known as qheaden
13:16:24 <qheaden> Hi all!
13:17:13 <-- jb1 has quit (Ping timeout)
13:17:26 <clokep_> Hello.
13:17:52 <aleth> clokep_: I've only come across spam the last few days.
13:18:41 <clokep_> aleth: Me too. :)
13:18:48 <clokep_> Last week we had a couple people post.
13:19:00 <clokep_> One guy from a corporation asking about security (The answer to all his question is "Yes, we do that.")
13:19:05 <clokep_> But I haven't had time to write a response.
13:19:28 <qheaden> aleth: So the Yahoo plug-in is working for you?
13:20:11 <aleth> qheaden: yes :)
13:21:06 <aleth> clokep_: Oh right, that one.
13:21:09 <qheaden> :)
13:21:31 <aleth> qheaden: looks like it's working well :)
13:23:28 <qheaden> clokep_: So this weekend, I was looking at how we could possibly implement buddy info.
13:23:50 <qheaden> We might have to use the new Yahoo contacts API.
13:24:09 --> jb has joined #instantbird
13:24:11 <-- jb has quit (Broken pipe)
13:24:26 <clokep_> qheaden: Why does the old way of doing it not work?
13:24:30 <clokep_> Isn't that what libpurple uses?
13:25:53 <qheaden> clokep_: After looking, and trying it in Pidgin and Ib, I don't think libpurple supports extra buddy info for Yahoo.
13:26:21 <clokep_> Umm....nothing extra shows up in the tooltip?
13:26:28 <clokep_> Maybe I don't understand what you mean by "extra buddy info".
13:26:57 <qheaden> It only tells the online state and availability. No address book stuff.
13:27:31 <aleth> qheaden: It doesn't display it in the tooltip because we discard that info currently for all protocols other than JS-IRC.
13:28:11 <qheaden> I can't even find the code that makes a request for it.
13:28:54 <clokep_> qheaden: http://lxr.instantbird.org/instantbird/source/purple/libpurple/protocols/yahoo/yahoo_profile.c
13:29:09 <qheaden> The only usage of the address book URL I found in libpurple is to list public chat rooms, which are now gone.
13:29:23 <aleth> qheaden: http://lxr.instantbird.org/instantbird/source/purple/libpurple/protocols/yahoo/yahoo_profile.c#1263 ?
13:29:33 <clokep_> aleth: We should stop doing that thing w/ IRC...
13:30:18 <aleth> clokep_: ...at least for JS-XMPP and JS-Yahoo! ;)
13:32:37 <clokep_> aleth: Yes, :)
13:32:52 <aleth> qheaden: FYI http://lxr.instantbird.org/instantbird/source/instantbird/content/buddytooltip.xml#251 you should change this :)
13:33:33 --> mconley has joined #instantbird
13:34:34 <-- mconley has quit (Connection reset by peer)
13:34:36 --> mconley_ has joined #instantbird
13:35:56 <clokep_> qheaden: For now, change that and see what is actually returned.
13:36:32 <qheaden> Wow, strange code. OK. :P
13:47:36 <-- clokep_ has quit (Quit: http://www.mibbit.com ajax IRC Client)
13:52:33 --> jb has joined #instantbird
13:52:37 <-- jb has quit (Broken pipe)
13:58:14 <qheaden> Hmm, after the change, I still don't get any profile informationl.
13:58:58 <aleth> Maybe the libpurple code is broken somehow?
13:59:39 --> jb has joined #instantbird
14:00:01 <aleth> Does it fetch the avatar OK?
14:03:56 <-- jb has quit (Quit: jb)
14:08:49 --> jb has joined #instantbird
14:09:10 <qheaden> aleth: libpurple seems to fetch the image okay.
14:09:11 <-- jb has quit (Broken pipe)
14:09:44 <qheaden> I just tried getting the profile info in Pidgin, but comes back with an error saying this profile is in a language or format that is not supported at this time.
14:10:14 <qheaden> I think Yahoo made some change to their profile system, and prefer clients use the contacts API.
14:10:21 <aleth> I wonder if Yahoo these days just link to a profile webpage or something
14:10:22 <qheaden> But I don't think it can be used without an API key. :-S
14:10:29 <qheaden> Yeah, I think so.
14:10:51 --> jb has joined #instantbird
14:10:59 <-- jb has quit (Broken pipe)
14:10:59 <qheaden> profiles.yahoo.com/<username>
14:11:07 <qheaden> Everyone doesn't have, or want, a public profile thoughl
14:13:46 <aleth> Maybe the "language or format" is HTML :P
14:16:12 <qheaden> :P
14:23:24 <instantbot> New Core - Yahoo! Messenger bug 2080 filed by qheaden@phaseshiftsoftware.com.
14:23:30 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=2080 cri, --, ---, qheaden, NEW, Buddy Authorization Handler Doesn't Work
14:25:16 <instantbot> qheaden@phaseshiftsoftware.com requested review from clokep@gmail.com for attachment 2653 on bug 2080.
14:26:20 --> jb has joined #instantbird
14:26:25 <-- jb has quit (Broken pipe)
14:29:21 <instantbot> qheaden@phaseshiftsoftware.com cancelled review?(clokep@gmail.com) for attachment 2653 on bug 2080.
14:29:22 <instantbot> qheaden@phaseshiftsoftware.com requested review from clokep@gmail.com for attachment 2654 on bug 2080.
14:29:23 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=2080 cri, --, ---, qheaden, NEW, Buddy Authorization Handler Doesn't Work
14:38:33 --> jb has joined #instantbird
14:38:36 <-- jb has quit (Broken pipe)
14:39:19 <aleth> atuljangra: check your etherpad
14:41:23 <qheaden> It looks like libpurple code extracts data from an HTML profiles page, but I think Yahoo has changed their profiles stuff recently.
14:41:45 <aleth> Sounds like a painful thing to have to do in the first placce.
14:42:16 --> jb has joined #instantbird
14:42:30 <aleth> It smells "officially unsupported"
14:45:12 <aleth> qheaden: "In order to access Social Directory data in your application, you’ll need to get a Yahoo! API key and configure it to use Social Directory. " as you suspected.
14:46:31 <aleth> OTOH It says the same thing for the Yahoo Messenger API
14:46:46 <aleth> http://developer.yahoo.com/messenger/
14:49:21 --> novabyte has joined #instantbird
14:49:26 <-- jb has quit (Ping timeout)
14:50:40 <-- mpmc has quit (Quit: Instantbird 1.5a1pre -- http://www.instantbird.com)
15:03:18 --> atuljangra has joined #instantbird
15:03:35 <atuljangra> aleth: ping.
15:05:19 <qheaden> aleth: Yeah, it looks that way. :(
15:05:47 <qheaden> I'll have to let clokep know when he gets back.
15:06:05 <aleth> qheaden: You don't use the Messenger API, do you?
15:06:12 <qheaden> aleth: No.
15:06:30 <aleth> atuljangra: Did you see the etherpad?
15:06:47 <atuljangra> aleth: Yes. I wanted to discuss the problem with the flow.
15:07:28 <aleth> Well, first of all, this code looks a lot better than the previous version :)
15:08:15 <atuljangra> Ok :) Previous version was mostly playing around with things. This one is more subtle I guess.
15:09:24 <aleth> I'll give you some feedback on the code flow, but your top priority should probably be to finish Filelink as fast as possible so that can be reviewed.
15:10:48 <atuljangra> you mean mostly UI?
15:11:07 <aleth> Yes. The dialog improvements, the preference pane, etc.
15:11:11 <atuljangra> aleth: Could you give all the feedback on bitbucket? I becomes easier to track. :)
15:11:16 <aleth> atuljangra: No.
15:11:23 <atuljangra> aleth: OK :)
15:11:32 <aleth> I can't do this on bitbucket because there is no obvious place to put it there.
15:11:57 <atuljangra> Comment on the commit, on top? :s
15:12:17 <aleth> But I have questions too.
15:12:33 <atuljangra> Ok :)
15:12:39 <aleth> handleFileTranfer is called only by filetransfer objects?
15:13:07 <atuljangra> Yes.
15:13:37 <aleth> So the file transfer uses this to report failure or problems, and handleFileTransfer then decides what to do>
15:13:54 <atuljangra> Yes.
15:13:55 <aleth> OK, got it.
15:14:18 <aleth> Why doesn't the conversation listen for notifications sent by the FileTransfer instead?
15:14:51 <atuljangra> like the way file-transfer-start and file-transfer-end is handled?
15:15:17 <-- novabyte has quit (Quit: bye bye)
15:16:12 <aleth> Right, but with the prplConversation doing the listening.
15:16:44 <aleth> I'm just trying to understand why your design is the way it is here
15:17:52 <atuljangra> Okay. In case of failure, we want to offer other file transfer methods too. So that is going to be handled by the handleFileTransfer method.
15:18:17 <atuljangra> While in case of start and end we just want to inform the ui about the event.
15:18:35 <aleth> Part of my confusion is the naming I think. Basically you are saying handleFileTransfer is actually something like handleFileTransferFailure?
15:19:15 <atuljangra> Yes, sorry about that. Actually in course of coding, I decided to change the nature.It should be handleFileTransferFailure.
15:21:03 <aleth> Maybe we can postpone the discussion about whether to use notifications instead of handleFileTransferFailure until flo comes back.
15:21:40 <atuljangra> aleth: Whatever you say. This can be changes easily.
15:21:57 <aleth> But what is definitely wrong is where the check for if a transfer takes too long is.
15:22:28 <atuljangra> Okay. Elaborate please :)
15:22:40 <aleth> If we start with the best available file transfer method, do we expect progress to get faster when we switch to a less good method?
15:24:03 <atuljangra> We can, but we don;'t have any choice. If the file transfer is slow, either we can offer filelink or we can try another method.
15:24:21 <aleth> What I am saying is, if the connection is too slow, will changing the method help?
15:25:01 <aleth> I don't understand how that could happen?
15:26:03 <atuljangra> I'm not sure. And I'm just speaking over my head, but maybe the "less good" method may perform better somehow.
15:26:10 <atuljangra> This is totally vague now.
15:26:14 <aleth> True.
15:26:23 <atuljangra> What would you want in this case?
15:26:53 <aleth> I just think the check for slowness starting at let percentFTCompletion =...  should not be in each file transfer method.
15:27:35 <atuljangra> Okay, so it should be in top two and then we can switch to filelink?
15:30:28 <aleth> I may be wrong on this, but I think the UI (conversation.xml) should decide whether it is taking too long, and offer Filelink at that point. If the user then accepts this offer, the UI tells the file transfer to abort. (While the handleFileTransferFailure stuff handles what happens when a particular method fails. So this assumes that changing the method won't improve performance.)
15:31:05 <aleth> The UI would be able to monitor progress of ongoing file transfers in a similar way to how the download panel monitors the progress of ongoing file transfers.
15:31:18 <atuljangra> Seems good to me.
15:31:22 <aleth> I'm not sure how this is done (notifications?), maybe you do?
15:31:41 <atuljangra> Yes,  notifications can be helpful here.
15:31:55 <aleth> This avoids each method having to decide for itself whether things are going quickly enough, and duplicating a lot of logic.
15:32:30 <atuljangra> Yes, this seems better than current logic.
15:32:43 <atuljangra> So do you want me to wait for flo and then implement this, or implement it now?
15:33:12 <qheaden> aleth: Looks like this is the profile URL used: http://lxr.instantbird.org/instantbird/source/purple/libpurple/protocols/yahoo/libymsg.h#41
15:33:29 <aleth> I suspect it may be easier to implement this when you add the download panel and the corresponding data flow, so maybe this should wait for now.
15:35:32 <aleth> For now I would suggest changing the handleFileTransfer name, improving the comment, and fixing the small issues in the etherpad. This shouldn't take more than half an hour or so, and then you can move on to finishing Filelink.
15:35:35 <atuljangra> aleth: Okay :)
15:35:58 * atuljangra afk dinner
15:35:58 <aleth> Does that sound sensible?
15:36:09 <atuljangra> aleth: Yes, I agree with all of it :)
15:36:24 <aleth> flo may be able to look in in a day or two, and it would be nice to have a Filelink patch ready for him ;)
15:38:34 <atuljangra> Yes. I'll try my best :D
15:41:00 <aleth> atuljangra: This is what you use for debug logging: http://lxr.instantbird.org/instantbird/source/chat/modules/jsProtoHelper.jsm#386
15:41:22 <atuljangra> aleth: noted.
15:41:39 <aleth> So you can easily call those as the file transfer objects refer to a conversation.
15:46:41 * mconley_ is now known as mconley
16:01:08 <atuljangra> yup. :D
16:06:20 <aleth> I left some comments on bitbucket too.
16:06:37 <atuljangra> aleth: Read them.
16:37:36 <qheaden> I'll be back later on.
16:37:41 * qheaden is now known as qheaden_away
16:49:48 --> Mook_as has joined #instantbird
17:03:33 <-- aleth has quit (Quit: Ciao)
17:04:53 --> qlum has joined #instantbird
18:07:29 --> unghost has joined #instantbird
18:19:04 <-- qlum has quit (Ping timeout)
18:19:26 --> qlum has joined #instantbird
18:30:26 <-- mconley has quit (Connection reset by peer)
18:30:42 --> mconley has joined #instantbird
18:49:04 --> Mic has joined #instantbird
18:49:04 * ChanServ sets mode +h Mic 
18:50:02 <-- atuljangra has quit (Quit: http://www.mibbit.com ajax IRC Client)
18:51:28 <Mic> Hello
19:05:21 --> atuljangra has joined #instantbird
19:06:49 <-- mconley has quit (Connection reset by peer)
19:07:03 --> mconley has joined #instantbird
19:07:46 <-- qlum has quit (Ping timeout)
19:08:08 --> qlum has joined #instantbird
19:36:00 <-- atuljangra has quit (Quit: http://www.mibbit.com ajax IRC Client)
20:32:17 <-- qlum has quit (Ping timeout)
20:32:39 --> qlum has joined #instantbird
20:36:39 --> FireFly_TB has joined #instantbird
20:49:29 --> EionRobb has joined #instantbird
21:50:38 <-- qlum has quit (Connection reset by peer)
22:01:37 --> mpmc has joined #instantbird
22:06:22 <-- mconley has quit (Input/output error)
22:16:47 <-- unghost has quit (Quit: Ухожу я от вас (xchat 2.4.5 или старше))
22:44:08 <-- Mic has quit (Quit: Instantbird -- http://www.instantbird.com)
22:44:51 --> wnayes has joined #instantbird
22:47:24 * qheaden_away is now known as qheaden
23:09:33 <-- FireFly_TB has quit (Ping timeout)
23:12:30 <-- Tonnes has quit (Connection reset by peer)
23:14:58 --> rosonline has joined #instantbird
23:21:14 --> clokep has joined #instantbird
23:21:14 * ChanServ sets mode +o clokep 
23:23:12 <clokep> qheaden: Umm...all these bugs you're filing as "critical" aren't critical.
23:23:18 <clokep> "Critical" pretty much means "Instantbird won't start.
23:23:46 <qheaden> clokep: Ahh okay. So it should be "major"?
23:23:54 <clokep> That or normal, yes.
23:24:58 <clokep> Just don't make it critical. ;)
23:27:19 <qheaden> :)
23:28:33 <qheaden> clokep: I was doing some research into how libpurple handles Yahoo profiles. I think their profile code is now broken, except for obtaining the user's account icon.
23:28:57 <clokep> OK, i'm catching up on logs still.
23:29:14 <instantbot> clokep@gmail.com granted review for attachment 2654 on bug 2080.
23:29:16 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=2080 maj, --, ---, qheaden, NEW, Buddy Authorization Handler Doesn't Work
23:29:31 <clokep> aleth: We don't use the "Yahoo Messenger API" so that doesn't mean anything. ;)
23:30:45 <qheaden> clokep: From what I see libpurple attempts to access profiles.yahoo.com, and tries to extract data from the page's HTML. But I think Yahoo recently made changes to their profile pages.
23:31:00 <qheaden> Also, I can't seem to access a profile with the profiles.yahoo.com/<username> URL format.
23:31:10 <-- EionRobb has quit (Ping timeout)
23:31:11 <clokep> qheaden: Please wait. I'm reading the logs.
23:31:16 <qheaden> Oh okay. :)
23:31:41 <clokep> qheaden: Did you check Pidgin's bug tracker to see if there was any bugs about this?
23:32:02 <qheaden> clokep: No. I'll take a look now.
23:32:15 <clokep> (Not that I don't believe you, just for verification. :))
23:33:23 --> EionRobb has joined #instantbird
23:33:27 <qheaden> clokep: Ahh, I found it https://developer.pidgin.im/ticket/12624
23:33:44 <qheaden> Opened 3 years ago. :-S
23:34:09 <clokep> qheaden: So note all this information down that we've found and move onto something else.
23:34:12 <clokep> Buddy icons, I think.
23:34:24 <qheaden> clokep: Okay, I'll place it on the bug.
23:35:29 <qheaden> clokep: BTW, did you get my message about the patch queue?
23:35:39 <EionRobb> qheaden: do you have an example profile that you use for reference?
23:35:47 <clokep> qheaden: Yes.
23:35:55 <qheaden> EionRobb: Yeah, I did. My ibprpltest account.
23:36:00 <qheaden> *I do
23:36:21 <EionRobb> http://pulse.yahoo.com/ibprpltest ?
23:36:45 <clokep> That doesn't work.
23:36:48 <qheaden> EionRobb: Apparently, you can't access profile pages with usernames anymore.
23:37:09 <EionRobb> sux
23:39:23 <qheaden> Too bad the Yahoo contacts API can't be used without an API key.
23:40:50 <clokep> qheaden: How hard would it be to add a test for bug 2080? :P
23:40:54 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=2080 maj, --, ---, qheaden, NEW, Buddy Authorization Handler Doesn't Work
23:41:26 <qheaden> clokep: Not sure. It has to do with UI notifications.
23:42:36 <qheaden> clokep: Would you prefer if I use the patch queue, or continue with the yahoo-prpl branch in the main repo?
23:43:25 <clokep> qheaden: I want you to use whatever makes your work efficient.
23:44:12 <qheaden> Okay, I'll keep the patch queue so I can switch between patches and make it easier to diff.
23:44:40 <clokep> Good.
23:44:47 <clokep> That was the answer I was hoping for. ;)
23:45:07 <qheaden> For the buddy auth test, perhaps we could simply add an observer for buddy authorization, and when the observer is called, pass the test?
23:45:29 <clokep> Maybe.
23:45:33 <qheaden> Of course do some object checks.
23:49:28 <clokep> qheaden: I'll try to commit that fix soon.
23:49:31 * clokep is packing for his trip.