Gaim 2.0.0beta1 Released
BerkeleyDude writes "Gaim 2.0.0beta1 has been released! Here is the changelog.
New features include account status, away messages, etc, UPnP and NAT traversal support, new UI for buddylist, chat windows and preferences."
To me, it seems like their stance on not encrypting passwords is a backwards. Having a non-encrypted passwords policy does not make sense to me, as it leaves things wide open.
support Jingle? Didn't see that in the changelog...
Big question for me - Does it support video chat with people on the Yahoo! network? It's a major deal-breaker for most of the people I administer windows and mac computers for. :-(
Help! I'm a slashdot refugee.
This really bugs me, and is the reason I will not be upgrading to Gaim 2.0
* Removed "Gaim usage" and "Idle time reporting" preferences; behavior now always uses mouse/keyboard when available
I do not have Gaim report my idle time, largely for work reasons. If I am busy at work or whatever, I don't want the "obligation" of having to reply to a person that notices that I am no longer idle. This is a very common thing, and I prefer that that remains private. As far as anybody else should be concerned, I am away. It doesn't mean I am avoiding the person, but sometimes you have other things that need to get done, and I don't want to have to explain that to people that I don't want upset at me.
A community-oriented lyrics site
"And it still doesn't support AIM encryption. The only way to have a secure IM with gaim is to talk to another gaim user.
I still don't understand why their developers chose to do this. One of the few things that is right with AIM is the secure-chat feature. It's fairly easy to set up, and its very secure.
Because:
Simple. A little over a year ago, I contacted one of gaim's core developers about gaim's difficulties with file transfers when any of the party is NAT'd. He didn't know or care about the file transfer stuff, so he put me in contact w/ another core developer. The second guy was even worse; he was in charge of file transfers and such, but outright told me that he didn't care if things didn't work in NAT'd environments and that things would probably never change. Though I cannot remember the conversation, verbatim, I do remember this: not only was he pretty damn rude (whereas I had been more than polite), but he didn't care that the code he was in charge of didn't work well.
I gave it some thought, and decided that if the developers of gaim have attitudes like this, it is not a project that I want any part of. <shrugs> What's more: IM has become an integral part of staying in touch with people. It's right up there with email. If the developers of the defacto standard IM client for *nix don't care if it has issues and don't care to fix those issues, how in the hell do people honestly expect anyone to switch from windows to a FOSS *nix (ie. linux, freebsd, etc). Having bugs is one thing, but not even caring about those bugs? Psssh.
(And, yes, I know the changelog says that they've fixed some of the NAT issues... but for me, I've already decided that the apathy about the quality of their product is cause enough to permanently stay away from gaim.)
/dev/random
After spending over an hour trying to get it to compile with the voice/video support only for make to choke on something in mediastreamer, I did get it running fairly easily after that. (Fedora Core 4, KDE)
My first impressions are mixed. There seems to be a bug in the handling of the new away window on the buddy list, as it has completely vanished on me once and sometimes it contains the message-window-style formatting bar which by itself suddenly vanishes.
I'm also annoyed at the size of the status buttons. I shrunk the ones for the individual protocols all the way down and got rid of them, but there's still that giant one and it would be nice if it were smaller.
I love the little effect where new messages "scroll up" from the bottom, as though the text entered is moving right up into the window. I've seen numerous complaints about it, but I think it's very neat.
File transfers work now in AIM. FINALLY. Previously, I'd had a 20% success rate, primarily when I disabled iptables. It worked flawlessly when I tested with some friends last night, which is nice because now I don't have to tell them to go e-mail me stuff.
I did get pretty annoyed because I knew the theme could be controlled through Gnome, but from KDE, I could NOT find the Gnome theme control! I Googled, I checked a ton of menu options and documentation, and there was no way to do it without logging out and logging in under Gnome. I thought this release was uglier than past releases and this was the first time I'd tried to theme it.
I still think Guifications needs to be included as standard rather than a plugin. Every other client I've used has it standard, and in fact, some like Trillian even have it better, displaying the message text rather than just "xyzperson has messaged you."
Overall, I'm quite impressed, but there's quite a bit of work that needs to be done I'd think.
actually, this _was_ the case. the Gaim-vv devs were all ready to merge into CVS HEAD, but Sean Egan changed all the hooks for voice and video without any notice, all so google's voice chat could be integrated. this means that all the gaim-vv work was essentially for naught, and it seems that the devs have given up merging in the support. the lead gaim-vv dev updated his blog with the situation, and others like Christian "ChipX86" Hammond chimed in with their personal horror stories working with Sean Egan. Egan has alienated most of the other GAIM contributors, who refuse to work with him anymore. sadly, it looks like Kopete will still be the only IM client for linux with cam support.
I looked at the sourceforge page, and it says that they're just giving up on gaim-w. If Sean Egan is such a tard and so many developers won't work with him, why don't they give up on gaim instead, and make their own fork and tell everyone that theirs is the one with voice and video support? It seems to me that that would be a good plan at this point...
Disclaimer: IANAL. This post is, however, legal advice, and creates an attorney-client relationship.