If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Skype 2.1 Beta Brings New Features To Linux

Phoronix: Skype 2.1 Beta Brings New Features To Linux

For anyone that extensively uses Skype on Linux, you will probably want to head on over to the Linux Skype Developer page to fetch the latest beta. Skype has just rolled out the first 2.1 beta (2.1.0.47 Beta) of the Linux Skype client, which adds several new features and also brings a number of fixes and other improvements. The new Skype Linux features are high quality video codec support, Skype's SILK audio codec support, PulseAudio compatibility, SMS sending support, chat messaging editing/removing capabilities, contact groups support, typing notification in chat, chat picture support, mood messages, video/mobile icons are now visible in the contact list along with bookmarked chats, and also added are contact labels/tags. Beyond these key features to Skype 2.1 for Linux, the beta release also brings a number of improvements ranging from better ALSA support (including USB headsets) to an enlarged tray icon...

I'm glad that at least they are clearly still working on it. In the last version (2.0.72) only skype-static-oss worked ootb in Karmic. This new beta works OK so far, and finally supports pulse.

Skype is the only proprietary software I use right now (besides a broadcom wifi binary). If a proprietary game stops working with your system you can move on, but it sucks if it's an application you use every day.
I can just hope that one of two things happen:
Skype becomes increasingly popular and the protocol is eventually reverse engineered.
Skype starts charging, making it easier to move everyone to a free alternative.

Oh, the classic "any software whose source code isn't in the open can contain backdoors!" claim. If there was a backdoor in Skype, it'd probably be in the network itself, not the client software.
ps. That post is just slightly incoherent. Sources hidden, facts obscured, would make a very bad article.