All times are UTC.
00:01:39 <-- DGMurdockIII has quit (Connection reset by peer) 00:06:19 <-- Ornthalas has quit (Quit: KTHXBYE) 00:08:11 --> hicham has joined #instantbird 00:36:00 --> Seji has joined #instantbird 01:04:03 <-- Amfi has quit (Ping timeout) 01:19:00 <-- hicham has quit (Client exited) 02:08:22 --> mib_bkruhb has joined #instantbird 02:08:35 <mib_bkruhb> ? 02:08:46 <clokep> Hello mib_bkruhb. 02:08:50 <mib_bkruhb> Hi. 02:09:01 <clokep> How's it going? 02:09:06 <mib_bkruhb> Pretty good. 02:09:14 <mib_bkruhb> I was on the Instantbird website. 02:09:14 <clokep> Good! 02:09:25 <clokep> Yes? 02:09:25 <mib_bkruhb> May I ask what the "vision" of the project is? 02:09:43 <mib_bkruhb> Are you targeting general users, corporate intranets etc. 02:09:45 <clokep> I think http://instantbird.org/ will explain it well. :) 02:10:48 <mib_bkruhb> Have you had any feedback regarding using Instantbird with eJabberd or Openfire? 02:11:26 <clokep> I'm not familiar with either of those. 02:11:44 <clokep> Jabber is supported (XMPP) but I'm guessing that's different then eJabberd? or was that a typo. :) 02:11:55 <clokep> Openfire I'm not familiar with. 02:12:03 <mib_bkruhb> eJabberd is an open source XMPP server, ditto for Openfire. 02:12:20 <mib_bkruhb> I'm looking around for possible solutions to use on an organizational intranet. 02:12:20 <clokep> Ah, does it not work fine w/ them? 02:12:53 <clokep> Oh, Instantbird should work fine with them (AFAIK). It uses the same backend as Pidgin/Adium/Finch to connect to networks if that helps. 02:13:00 <mib_bkruhb> Haven't checked, getting approval to install something on the QA lab is a pretty laborious task (2-3 weeks), so I try and do a bit of fact-finding before hand if possible. 02:13:28 <clokep> Understandable. 02:13:34 <mib_bkruhb> I notice that it says it doesn't need admin permissions to install? 02:13:43 <mib_bkruhb> (BTW, thanks for your time) 02:13:44 <clokep> It shouldn't. 02:14:13 <clokep> Installer, etc. is all based on Mozilla stuff (Firefox/Thunderbird) so if those work, Instantbird should too. 02:14:31 <clokep> No problem! I'm really not busy now...and unfortunately most people are asleep right now. 02:14:54 <mib_bkruhb> Alright. I like the look of the software and I'm trying to push open source where I can. 02:15:14 <mib_bkruhb> I'll do a bit more reading and see if I can get it on the short-list. 02:15:20 <mib_bkruhb> Thanks again. :) 02:15:24 <mib_bkruhb> Good night. 02:15:37 <-- mib_bkruhb has quit (Quit: http://www.mibbit.com ajax IRC Client) 02:15:39 <clokep> Goodnight! 02:15:43 <clokep> Let us know if you have more questions... 02:37:15 <-- chrisccoulson has quit (Quit: Ex-Chat) 03:54:15 --> tymerkaev_away has joined #instantbird 04:14:28 --> rikki has joined #instantbird 04:15:38 <-- clokep has quit (Quit: Instantbird 0.3a1pre) 04:48:00 <-- tymerkaev_away has quit (Ping timeout) 06:55:23 <flo> clokep: "If there's going to be a supre easy way to do it once you work on js-proto stuff again then don't worry about it." or maybe I need to worry about it to make it super easy ;) 06:56:25 <flo> clokep: I've tried to sign-up for SkypeKit beta. They haven't send me anything (except maybe a confirmation email). 07:08:22 <-- flo has quit (Quit: Instantbird 0.3a1pre) 07:08:26 --> flo has joined #instantbird 07:08:27 * ChanServ sets mode +qo flo flo 07:09:09 <-- flo has quit (Quit: Instantbird 0.3a1pre) 07:09:49 --> flo has joined #instantbird 07:09:49 * ChanServ sets mode +qo flo flo 07:29:07 --> hicham has joined #instantbird 07:56:54 <flo> Good morning :) 08:04:16 --> Amfi has joined #instantbird 08:07:05 --> Even has joined #instantbird 08:07:05 * ChanServ sets mode +o Even 08:07:45 <instantbot> florian@instantbird.org set the Resolution field on bug 517 to FIXED. 08:07:46 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=517 nor, --, ---, florian, RESO FIXED, Incorrect number of comments 08:19:01 <hicham> Good Morning 08:27:23 <-- Mic has quit (Quit: Instantbird 0.3a1pre) 08:28:15 --> Mic has joined #instantbird 08:28:22 <Mic> morning 08:45:02 <Mic> flo: maybe there's a way to make some money with customized and adapted versions of Instantbird for companies? 08:46:22 <Mic> I don't know how things work in this environment as they could as well do customization themselves if they want to 08:47:23 <Mic> Maybe they need means to lock down the application to connect to certain networks only or what else they might need 08:48:30 <flo> there could be interesting situations :) 08:59:44 <Mic> Do you have a rough idea what you'd like to see in 0.3? 09:00:26 <flo> the roadmap document is not really outdate on this 09:01:21 <flo> I still haven't done it, but I would like to document it differently, exposing it as projects, with steps, objectives, etc... 09:01:38 <flo> some of them we can drop and some which are not really needed for 0.3 that we would be glad to take 09:01:40 <Mic> Good to see the password manager on the list 09:02:29 <flo> I would like if most "projects" could be "probably doable in about one week" 09:02:32 <Mic> The project approach sound good 09:03:30 --> mokush has joined #instantbird 09:03:54 <flo> projects that we can probably drop include "advanced choices of sounds", "configurable notification for events" 09:04:00 <Mic> ah, mokush: .. I really should try to finish this extension 09:04:31 <flo> some projects that I would love to take if they are ready but that could wait for 0.4 if not: better logs, Sync, JS-IRC, ... 09:04:33 <Mic> Project that contributor could take or projects for you 09:04:54 <Mic> Just as overview on the status for interested users? 09:05:31 <Mic> Seems to me that clokep is making good progress on the js-irc btw 09:05:48 <flo> if I manager to clarify enough to get contributors able to "jump in" and work efficiently on projects that are on the critical path of 0.3, I'll be really happy :) 09:06:12 <flo> Mic: I have the same impression. 09:06:14 <Mic> Using the password manager could mean that we could reuse the Fx password-syncing part of Weave 09:06:33 <flo> but there's still a long way to go before it's going to support as many features as the current C IRC. 09:06:38 <Mic> (maybe, I haven't looked into yet) 09:06:44 <flo> and lots of areas of his work are blocked by my js-proto work 09:07:04 <flo> Mic: yes, you probably want to reuse the password sync engine 09:07:20 <flo> it also means that people will be able to use a master password for instantbird :) 09:08:18 <Mic> The next days I'd like to try if I could create a patch from the changes so far and apply it to an uptodate clone of the Fx sync repository 09:08:49 <Mic> Would be nice if it works without much hassle 09:09:50 <Mic> Is there any way you can recommend to stay uptodate with another repository while working on your own? 09:11:58 <mokush> Mic: have you got more work on it? 09:12:28 <flo> Mic: nothing I can really recommand 09:13:04 <flo> but maybe cloning the other repository, working in a branch on that clone, and pulling regularly the default branch and merging it into your own branch would be workable 09:13:36 <Mic> mokush: not yet, but I know that idle (or away when idle) breaks invisibility mode, so I'm going to disable this setting before becoming invisible and restore the old setting when the status is changed to something else 09:13:56 <mokush> that sounds good 09:14:12 <flo> Mic: doesn't that sound like a core bug? 09:14:13 <Mic> Well, the user could still meddle with this setting while being invisible .. 09:14:46 <Mic> I haven't checked.. so far I was under the impression that we explicitly change status to away 09:15:15 <Mic> Are we only exposing a libpurple feature there? If yes then it would be a bug 09:15:28 <flo> If I remember well we don't do it if the user is already away or busy or offline 09:15:45 <Mic> ok, I'll check that first 09:15:53 <flo> so maybe we should add a special case for invisible too 09:15:58 <Mic> if that's the case I'll add invisible too 09:16:21 * Mic is starving. Back after snack. 09:31:16 * flo has updated the instantbird code on lxr, has decided he is tired of doing it, has scripted it, and added it to the crontab :) 09:33:43 --> kaie has joined #instantbird 09:56:57 --> tymerkaev_away has joined #instantbird 09:57:25 * tymerkaev_away is now known as tymerkaev 09:57:39 <-- tymerkaev has quit (Quit: I must go. Good bye!) 09:58:00 --> tymerkaev has joined #instantbird 10:00:04 <Mic> by the way I also meant things like 'fixing the authorization request' dialog for 0.3 10:00:28 <Mic> * 'fixing ... dialog' 10:18:42 --> chrisccoulson has joined #instantbird 10:52:29 <-- hicham has quit (Client exited) 10:52:47 --> hicham has joined #instantbird 11:05:46 --> GeekShadow has joined #instantbird 11:24:51 --> hicham_ has joined #instantbird 11:25:10 <-- flo has quit (Quit: Instantbird 0.3a1pre) 11:26:41 <-- hicham has quit (Ping timeout) 11:26:44 * hicham_ is now known as hicham 11:57:20 --> flo has joined #instantbird 11:57:20 * ChanServ sets mode +qo flo flo 12:10:21 <-- rikki has quit (Quit: Instantbird 0.2) 12:57:36 <-- mokush has quit (Client exited) 13:26:04 --> clokep has joined #instantbird 13:26:12 <-- GeekShadow has quit (Ping timeout) 13:27:36 <-- hicham has quit (Client exited) 13:33:57 <flo> nice, we have a new msn crash :) 13:35:20 <clokep> Mic: I've made what looks like good progress on irc-js...but I haven't really done much. :) 13:35:33 <clokep> Just translated the RFC into pseudo code mostly. 13:36:58 <clokep> Its really nice to have the addons manager working again though. :) Thanks for doing the partial back out. 13:39:09 <-- Morian has quit (Ping timeout) 13:39:43 --> GeekShadow has joined #instantbird 13:39:51 <flo> clokep: "Just translated the RFC into pseudo code mostly." what if it was all that was needed? ;) 13:40:32 <clokep> Unfortunately its not. :) Cause most the decisions about what to do after receiving response hasn't been written yet! :) 13:40:54 <-- tymerkaev has quit (Ping timeout) 13:44:13 --> Mic|web has joined #instantbird 13:44:45 <flo> clokep: what's currently blocking you (if anything)? 13:45:24 <clokep> flo: Opening a chat room. I can open a conversation no problem (new Conversation duh), but chats I couldn't figure out. 13:45:57 <flo> is the problem only with the joinChat thing, or any chat room? 13:46:36 <clokep> I couldn't get joinChat / DefaultChatRoomValues or whatever the variable is to work. 13:46:53 <clokep> I didn't try ridiculously hard, but I was getting not implemented errors. 13:47:18 <flo> and if you (first) hard code the channel you want to join? 13:48:30 <clokep> Not sure what you mean? 13:49:10 <flo> these ChatRoomValues things are only used to interact with the join chat dialog 13:49:56 <flo> if you for example decide that you always want to join #test (and so you don't need the join chat dialog to work), do you have another problem with opening the chat? 13:51:10 <Mic|web> just my two cents: 13:52:02 <clokep> I need to look at what I was trying, one second. 13:52:07 <Mic|web> don't you have to implement joinChat yourself (ie sending right commands to the server?) and to create an object representing the chat yourself? 13:52:48 <clokep> flo: joinChat stills requires "aComponents" which AFAIK is the "ChatRoomFieldValues", am I confusing something? 13:58:35 <Mic|web> clokep: you can create one to one conversations but not multi user chats? 13:58:45 <clokep> Mic|web: Yes. 13:59:02 <Mic|web> ok, have you seen that a conversation for MUCs requires extra methods? 13:59:45 <Mic|web> getParticipants(), .. 14:00:16 <Mic|web> http://lxr.instantbird.org/instantbird/source/purple/purplexpcom/public/purpleIConversation.idl#131 14:00:23 <clokep> Right, I see that. 14:00:24 <Mic|web> I hope I'm on the right track here 14:00:55 <-- GeekShadow has quit (Quit: The cake is a lie !) 14:01:04 <clokep> But from what I remember, flo had told me I can't just make a conversation and then say its a chat, you have to initiate the conversation differently? But perhaps I misunderstood. :) 14:02:20 <-- Even has quit (Quit: Instantbird 0.3a1pre) 14:03:37 <Mic|web> maybe the GenericConversationPrototype is wrong and you need something similiar for a chat/MUC 14:05:06 <Mic|web> It's 'implementing' the purpleIConvIM interface while you'd need purpleIConvChat if I'm not mistaken 14:05:49 <Mic|web> Well, maybe I'm completely wrong here though. I've never really looked at this code before .. 14:06:08 <clokep> Have you looked at http://hg.instantbird.org/instantbird/file/tip/purple/purplexpcom/src/jsProtoHelper.jsm Mic|web? 14:06:14 <clokep> That really has the stuff I need to implement. :) 14:08:04 <-- Zach has quit (Quit: Leaving) 14:08:54 <Mic|web> What I meant to say is: what if the right prototype class for chat's is not there yet? 14:10:26 <clokep> Ah, yes. Its possible. 14:10:55 --> hicham has joined #instantbird 14:12:19 <-- clokep has quit (Quit: Instantbird 0.3a1pre) 14:12:22 --> clokep has joined #instantbird 14:13:24 <flo> Mic|web: right! :) 14:14:04 <flo> clokep: I think you either need to adapt GenericConversationPrototype, or make something that inherits from it, or duplicate and modify it 14:14:19 <Mic|web> or refactor it? 14:14:37 <Mic|web> A GenericConversationPrototype and one for each IM and Chat? 14:14:59 <Mic|web> *both 14:15:33 <Mic|web> (if this makes sense) 14:17:36 <Mic|web> I'll be back later 14:17:46 <Mic|web> good luck with your work 14:17:52 --> mokush has joined #instantbird 14:18:19 <clokep> I don't think a Generic one for both would work very well, it'd probably make more sense to inherit from it. 14:18:42 <flo> go this way then :) 14:19:02 <clokep> So once I do that I can just create a new one of those objects and it'll open a chat, OK. :) 14:19:13 --> tymerkaev has joined #instantbird 14:21:32 <-- Mic|web has quit (Quit: http://www.mibbit.com ajax IRC Client) 14:24:12 <flo> clokep: something like this: http://pastebin.instantbird.com/398 14:25:25 <clokep> flo: Got it, so a lot of that stuff just isn't in the js-proto helper file yet. :) Makes more sense now. 14:25:54 <flo> js-proto helper is nowhere near finished. 14:26:13 <flo> it's just what I needed when I wrote the Omegle and JSTest plugins and that I thought should be shared 14:26:32 <clokep> Right, of course. I Just didn't realize the chat stuff wasn't in there yet. :) 14:33:11 --> DGMurdockIII has joined #instantbird 14:34:35 <clokep> Can I get this GenericChatConversationPrototype to inherit from GenericConversationPrototype? 14:37:01 <flo> it does in the code I pastebined 14:37:08 <clokep> Just by doing whatever needs to be added/overwritten and then GenericChatConversationPrototype.__proto__ = GenericConversationPrototype 14:37:12 <clokep> Arg. 14:37:17 <clokep> I didn't copy that line. :) 14:51:58 <clokep> Is there a simpler way to make a JavaScript object into an nsisimpleenumerator besides making a new nsiarray, appending all the elements and then return enumerate? 14:52:36 <clokep> Ah I have to go for a bit. 14:52:40 <-- clokep has quit (Quit: Instantbird 0.3a1pre) 15:01:46 <flo> clokep: http://lxr.instantbird.org/instantbird/source/purple/purplexpcom/src/jsProtoHelper.jsm#86 15:01:47 <-- hicham has quit (Client exited) 15:28:02 --> clokep has joined #instantbird 15:29:31 <clokep> Thanks flo. :) 15:30:00 <flo> as you can see that js proto helper isn't completely empty ;) 15:30:40 <clokep> Yup! I can see. :) 15:36:49 <clokep> Looks like I need a GenericBuddyPrototype too. 15:36:59 <flo> I'm looking for better names to differentiates "buddies" and "contacts" 15:37:26 <flo> clokep: as long as you don't try to add buddies in the buddy list, you don't need that 15:37:34 <clokep> flo: How about buddies and contacts? ;) 15:37:48 <flo> does it make any sense? 15:37:48 <clokep> I don't need purpleIConvChatBuddy? 15:37:57 <clokep> Thta's what getParticipants returns. :) 15:38:02 <flo> you need that :) 15:38:32 <flo> but I thought your magic code of the getParticipants function may create it on the fly :) 15:38:49 <flo> any idea of a better name to replace "buddy"? 15:39:36 <flo> currently a "contact" is a person we have some contact information about (it's possible to be aware of contact information on several protocols for a same contact). 15:40:10 <flo> a "buddy" is the information about an account of a contact. For example an AIM screename, and MSN address, ... 15:40:21 <clokep> flo: I don't think it can, I need to store stuff (i.e. op, etc.) so I think it'd be easier to just have an array of JS objects which implement purpleIConvChatBuddy. 15:40:33 <clokep> Right. Hmm... 15:41:48 <clokep> Buddy is really "Buddy contact information", but that's not a good descriptor. 15:42:05 <flo> hmm, are you sure? 15:42:21 <flo> if the contact is "Florian" and has an MSN and an AIM account, the contact is composed of 2 buddies. 15:42:36 <clokep> Yes, I agree. 15:42:45 <clokep> I think that terminology is OK as long as we /always/ use it. 15:43:01 <flo> I always used it because it's what is used in libpurple 15:43:25 <flo> but I've been rethinking some of the things in our buddy list implementation since this morning 15:43:33 <clokep> Unfortunately buddy & contact are kind of synonyms in English. :( (I.e. technical usage vs. colloquial usage). 15:43:42 <flo> and when I look at the description of "buddy" in a dictionary... that really doesn't seem to match 15:44:52 <flo> if we attempt to describe "buddy" as "one account of a contact", then it will get even worse when trying to describe "accountbuddy", which is a buddy, as seen by one of the accounts of the user :) 15:45:40 <clokep> "Address" might be a description you're looking for? 15:45:46 <clokep> I.e. an "email address" of the buddy. 15:45:52 <clokep> But in this case is the "AIM" address? 15:46:08 <clokep> Unfortunately I think "screenname" might be too specific? 15:46:23 <clokep> Since the "buddy" holds mor einfo than just a screen name, right? 15:46:53 <flo> hmm 15:47:13 <flo> screenname is definitely AIM-specific 15:47:20 <clokep> "user name"? :) 15:47:41 <clokep> I think it might help to list out what info is part of a contact and what is part a buddy? 15:48:59 <flo> do you read SQL? 15:49:09 <clokep> Yes. 15:49:23 <clokep> I'm a bit rusty, but I should be able to read it OK. 15:49:31 <flo> http://pastebin.instantbird.com/399 15:51:25 <clokep> So the "buddy" holds all the protocol specific stuff pretty much. 15:52:33 <flo> I'm not sure of the difference between: key VARCHAR NOT NULL, name VARCHAR NOT NULL, srv_alias VARCHAR 15:52:39 --> Mic1 has joined #instantbird 15:53:15 <clokep> :) That's fun haha. 15:54:06 <flo> I guess "name" is the username as formatted to be displayed, "key" is the same information but normalized (on AIM that means, lowercase and space removed), and srv_alias could be a display name set by the contact 15:54:29 <clokep> That's probably what it is, but those identifiers are poorly chosen. :( 15:55:01 <flo> I expect the content to be different on different protocols :-D 15:55:10 <flo> especially for the srv_alias part 15:55:52 <flo> I would like if I could avoid doing backward incompatible changes in that SQL schema without a very good reason to do so 15:56:47 <clokep> Makes sense. :) I'm at a loss for a word to call a "buddy". 15:57:05 <clokep> I mean a buddy is like a "friend" whihc is a subset of your "contacts". 15:57:13 <flo> "position INTEGER, icon BLOB" look like really poor ideas in the first place :( 15:58:04 <clokep> I suppose. How else would you store an icon though? ;) 15:58:22 <flo> in a different table! 15:58:41 <flo> so that we can share it when a contact uses the same icon on different buddies 15:58:52 <clokep> Ah, change it? ;) 15:59:09 <clokep> Is that sqlite database set up by libpurple or is i Instantbird code? 15:59:16 <flo> instantbird 15:59:31 <flo> libpurple handles the buddy list storage very differently 15:59:56 <clokep> I thought so. 16:00:06 <flo> first, what they call a "buddy" is what I call "accountBuddy". 16:00:08 <clokep> Well if you have a "Contact" i think the proper terminology would then be "Contact info"? 16:01:37 <clokep> I need to head to campus -- I'll think about it and be back in a few minutes. 16:01:38 <flo> then, they see the blist as a tree. Each buddy has a contact as parent, and each contact has a group as parent. 16:02:07 <flo> I'm not really sure I still want to change the word "buddy". At least in the SQL schema I think I'll keep it 16:04:50 <clokep> OK. :) And tags sound good. 16:04:55 <clokep> Anyway, I'll be back. 16:07:54 <-- clokep has quit (Ping timeout) 16:12:33 --> clokep has joined #instantbird 16:13:43 <clokep> Are you working on js-proto stuff then now or other stuff? 16:14:05 <flo> I wanted to make the buddy list work with the js-proto stuff today 16:14:22 <clokep> Oh, that'd be snazzy. I could use that too. 16:14:24 <flo> and started hitting various blocking points 16:15:31 <flo> I've almost decided that it's time to write a correct back-end for the buddy list and then plug libpurple into it (and throw the existing confusing code), instead of trying to adapt what we have now to make it "work" with JS proto 16:17:03 <clokep> That sounds like a lotta work. 16:17:39 <clokep> And possibly incompatible changes. ;) 16:17:49 <flo> the difficult part is to make sure my mind is clear about what needs to be done before I start touching the code 16:18:54 <flo> I'm also wondering how much of it can be done in JS :) 16:20:17 <clokep> Haha. This is the purplexpcom stuff you're thinking of touching? 16:21:00 <flo> yeah, I would like to change the XPCOM APIs around the buddy list 16:21:12 <flo> they have been a draft since 0.1 16:21:52 <clokep> Probably make sense to do it before we start writing other code around it then. 16:22:15 <flo> yes, I think the more we wait the more painful it will be 16:24:10 <flo> and if we could avoid having that kind of code in the UI: http://lxr.instantbird.org/instantbird/source/instantbird/content/buddy.xml#128 ... that would be so much better :) 16:24:48 <flo> deciding the status of a buddy based on the status of its accountbuddies is really not something the UI should do :) 16:24:54 <-- tymerkaev has quit (Connection reset by peer) 16:25:16 --> tymerkaev has joined #instantbird 16:26:43 <clokep> The UI should just have its status and display it? ;) 16:27:08 <flo> it should just display 16:27:18 <flo> not compute 16:28:14 <flo> having less to think about uninteresting things to display something useful gives more power for crazy add-on developers; ) 16:28:15 <clokep> Right. 16:30:37 <clokep> Yes, it does. :) 16:30:42 <clokep> Class time! 16:30:50 <flo> have fun! :) 16:33:42 <-- clokep has quit (Ping timeout) 16:43:37 <Mic1> What happens if a module contains a function that has been defined before? 16:43:53 <flo> I don't know 16:44:01 <Mic1> Is there a scope of the module and it will hide the other function or is there none and it will epically fail 16:44:04 <Mic1> ah, ok 16:54:13 <Mic1> The nsSimpleEnumerator is not really specific to the jsProtoHelper, maybe there is a better place to make such functions available? 16:55:03 <flo> yes 16:55:20 <flo> the reason why I put it there is initially I thought I wouldn't need to export it 17:07:59 <DGMurdockIII> some of my budedies are disapearing when i click on nthem 17:08:14 <DGMurdockIII> then a differnt one apperes 17:09:11 <DGMurdockIII> a restart of instant seem to fix it 17:12:46 <flo> comparing the availability of 2 buddies doesn't seem obvious 17:13:04 <flo> I would like if we could create a numeric value out of all the status information and compare it 17:13:43 <flo> but... how does this reflect that a buddy that has just talked to me while invisible is more likely to reply than a buddy of the same contact that has been idle for several days? 17:19:46 * tymerkaev is now known as tymerkaev_away 17:34:51 <-- DGMurdockIII has quit (Quit: get satisfied! :: www.unitedservers.de ««« (Gamers.IRC) »»» gamersirc.net ::) 17:36:12 <-- auscompgeek has quit (Quit: FATAL ERROR: Operation Succeeded) 17:41:28 --> Morian has joined #instantbird 17:41:28 * ChanServ sets mode +h Morian 17:47:25 <-- chrisccoulson has quit (Connection reset by peer) 17:48:45 --> chrisccoulson has joined #instantbird 17:58:30 --> GeekShadow has joined #instantbird 17:59:05 <Mic1> flo: if it's just about 'has talked to me recently' then you could model it by a high score that slowly decays with time until this bonus is gone after a while 17:59:22 <-- GeekShadow has quit (Client exited) 18:01:32 * tymerkaev_away is now known as tymerkaev 18:04:33 <-- tymerkaev has quit (Ping timeout) 18:07:36 <-- kaie has quit (Quit: Leaving) 18:07:46 --> hicham has joined #instantbird 18:08:56 <-- chrisccoulson has quit (Quit: Ex-Chat) 18:09:53 --> Wareczek has joined #instantbird 18:10:21 <-- Wareczek has quit (Quit: Instantbird 0.3a1pre) 18:11:21 --> Wareczek has joined #instantbird 18:11:27 <-- Wareczek has left #instantbird () 18:11:42 --> Wareczek has joined #instantbird 18:12:32 --> chrisccoulson has joined #instantbird 18:14:47 <-- Wareczek has quit (Quit: Instantbird 0.3a1pre) 18:18:19 <-- Gizmokid2005 has quit (Quit: =-O The Gizmo is gone!! Never fear for he shall return!!) 18:19:13 --> kaie has joined #instantbird 18:20:52 <flo> Mic1: I found the answer to my own question while I was going for dinner: this specific case doesn't matter because if someone has just said something, we will always reply through the same channel without comparing availability until there's a status change of one of the buddies, or the user does some UI action to change the destination of the messages. 18:25:45 <Mic1> We could extend protocols with a method that returns the number of remaining characters for a given string? 18:26:29 <flo> what's the purpose? 18:27:19 <Mic1> Making the UI show that the message can't be send because it's exceeding the limit (or when not exposing it, then treat it internally) 18:27:41 <flo> pastebin ? ;) 18:29:21 <Mic1> So others can a perfectly normal message via pastebin, only becasue it's a few characters too long? 18:29:32 <Mic1> *get 18:30:25 <flo> do you have protocols with very short limits (like twitter) in mind, or "regular IM protocols"? 18:30:43 <Mic1> I was thinking about Twitter and IRC 18:31:00 <flo> on IRC sending the message is several parts makes sense 18:31:01 <Mic1> They have limits I know 18:31:21 <flo> as long as there aren't a dozen of parts ;) 18:31:24 <Mic1> ok, so move it in the irc protocol 18:34:40 <Mic1> Defeating the sense of twitter: posting pastebin links and having a greasemonkey script that fetches and replaces the links by messages in the twitter feed :D 18:34:56 <flo> cool! :) 18:36:29 <Mic1> Going to suggest that, but I should file the "Audio-Personas for the visually impaired"-bug first :P 18:36:46 <Mic1> Keeping my todo list small ;) 18:42:52 <-- mokush has quit (Client exited) 18:51:27 <flo> good night! 18:51:29 <-- flo has quit (Quit: Instantbird 0.3a1pre) 18:57:10 <-- Mic1 has left #instantbird () 18:59:08 <-- hicham has quit (Connection reset by peer) 19:00:21 --> Gizmokid2005 has joined #instantbird 19:03:25 --> idechix has joined #instantbird 19:03:25 * ChanServ sets mode +o idechix 19:03:26 <-- idechix has quit (Quit: idechix) 19:03:43 --> idechix has joined #instantbird 19:03:44 * ChanServ sets mode +o idechix 19:06:14 --> hicham has joined #instantbird 19:27:32 --> clokep has joined #instantbird 19:29:38 <clokep> Mic & flo At least Mozilla's IRC servers don't have really small limits. The spec calls for short limits, but its not enforced. 19:30:58 --> Mic1 has joined #instantbird 19:32:47 <clokep> Mic1 I just said something to you. :) 19:32:55 <Mic1> I've seen it 19:32:59 <Mic1> What is the limit? 19:33:05 <Mic1> 512 characters? 19:33:14 <clokep> 255 by spec I think. 19:33:52 <clokep> 510 is the max. 19:34:14 <clokep> (and nicks are limited to 9 by the spec, but obviously not here) 19:34:23 <Mic1> 255 .. a bit less and they'd be competing with twitter ;) 19:34:54 <clokep> Well its 510 is the total message including the command and such. 19:39:58 * clokep is trying to find irc.mozilla.org's limit but apparently broke part of his protocol. :) 20:11:08 <-- chrisccoulson has quit (Quit: Ex-Chat) 20:11:16 --> chrisccoulson has joined #instantbird 20:28:37 * Mic1 shall post a complaint about method/variable naming in Sync 20:28:45 <Mic1> *should 20:29:34 <Mic1> One method contains "svc" as abbreviation of "service", five lines further they use just "s"; Funny things for History, Hist, Hi, H as well :S 20:35:33 --> kaie2 has joined #instantbird 20:37:45 <-- kaie has quit (Ping timeout) 20:37:45 * kaie2 is now known as kaie 20:40:14 <Amfi> Instantbird update on Win! :o 20:43:40 <-- Amfi has quit (Quit: Instantbird 0.3a1pre) 20:44:09 --> Amfi has joined #instantbird 20:45:37 <Amfi> With working addons! \o/ 20:46:26 <Mic1> Yes, it's great:) 20:47:02 <Mic1> clokep: have you extended the js protocol helper? 20:57:04 <Mic1> good night 21:04:43 <-- Mic1 has quit (Quit: Instantbird 0.3a1pre) 21:13:44 <-- idechix has quit (Quit: Instantbird 0.3a1pre) 21:15:18 <clokep> Mic1: Yes. I have. 21:16:05 <clokep> I'm not sure it works though. :) 21:43:42 <-- Gizmokid2005 has quit (Quit: =-O The Gizmo is gone!! Never fear for he shall return!!) 21:43:48 <-- clokep has quit (Quit: Instantbird 0.3a1pre) 21:53:42 <-- hicham has left #instantbird () 22:05:01 --> clokep has joined #instantbird 22:15:57 <instantbot> New purplexpcom - General bug 519 filed by clokep@gmail.com. 22:15:59 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=519 nor, --, ---, clokep, NEW, Extend jsProtoHelper to implement purpleIConvChat 22:21:45 <-- kaie has quit (Quit: Leaving) 22:51:29 --> Gizmokid2005 has joined #instantbird 22:52:12 <-- Gizmokid2005 has quit (Quit: =-O The Gizmo is gone!! Never fear for he shall return!!) 23:15:02 <-- Amfi has quit (Ping timeout) 23:24:06 <-- clokep has quit (Ping timeout) 23:27:38 --> clokep has joined #instantbird