singularly unproductive day. discovered libxode is leaky. fairly majorly. looked towards fixing a couple of more random segfaults in gaim. discovered why our "ordered" insert isn't acting very ordered, i need to write a GComparFunc. in fact, i need one for groups, one for persons, and one for buddies. but i didn't write them yet. faceprint started making the other protocols person-aware. that's a good thing: freaky things happen when you sign on a protocol that isn't person-aware. (for those who aren't familiar with what i'm doing, faceprint and i are working on a gaim source tree, re-doing the buddy list internals and display to support what i call persons, where a person is a collection of buddies that are all the same real-life person. everybuddy calls this concept a "contact".). I've also started in on the blist manipulation code, I've got a dialog that will eventually allow you to add/edit a person mostly displaying right, now i just have to make it do stuff and display data and not just widgets.
in other gaim news, some idiot has been posting to the gaim-devel list. on one hand, its great that the list is actually getting used. on the other hand, we've explained why encrypting the .gaimrc provides a false sense of increased security umpteen times now. People don't seem to even listen beyond the fact that we disagree. they know it all; us developers know nothing. chipx86 will be posting an entry to our faq giving a summery of what he and i had to repeat again in a series of emails today, that way we can hopefully reduce future instances of this request to a reference to the faq. which leads to my second most frequent gripe: chipx86 and i go to the trouble to write a faq that answers a significant number of the questions that hit the sourceforge forum, the #gaim irc channel, and the bug and support requests. but no one reads the faq, even though its linked to from gaim's home page. sometimes they don't even read it if you tell them to go directly there (give them the url). what's worse is when they try to tell me that their question isn't answered, when i wrote that part of the faq. </end gripe>