Slashdot Mirror


Skype For Linux To Be Open-Sourced "In the Nearest Future"

rysiek writes "Seems like there might be a revolution in the works, as far as VoIP software for Linux is concerned. After mailing Skype support about Skype providing Mandriva RPM packages, Olivier Faurax got an answer which suggests that the Linux Skype client will be open-sourced. After asking for verification of whether that was the case, the tech support answer claimed it is going to happen, and that it's supposed to happen 'in the nearest future.' Now, this probably only means the client (the underlying protocol will probably be handled by a binary-only library), but even if that's the case, it seems like there is still reason to celebrate."

175 comments

  1. Yay by dgr73 · · Score: 4, Funny

    Means I can create a client to automatically order in chinese.. or maybe a chipotle burrito and some fresh underwear

    1. Re:Yay by BitZtream · · Score: 3, Informative

      You can do that without Skype's source code. There are plenty of SIP clients out there and in fact an entire PBX system for Linux that includes the ability to war dial and use text to speech scripts on calls already.

      I'd almost wager someone has already written an asterisk script to order for them.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    2. Re:Yay by khayman80 · · Score: 1

      Why buy new underwear when you can just use Chipotlaway?

    3. Re:Yay by dgr73 · · Score: 1

      I want a .. number .. 14 .. and number .. 27 .. with chipotle sauce ... please add fresh underwear.

    4. Re:Yay by geordie_loz · · Score: 1

      however. Having skype integrated into open source PBX as a trunk (using the binary protocal, and the know how of how to use from the skype source) would be pretty good..

    5. Re:Yay by mi · · Score: 2, Interesting

      Having skype integrated into open source PBX [...] would be pretty good...

      Asterisk supports Skype. As does FreeSWITCH.

      --
      In Soviet Washington the swamp drains you.
    6. Re:Yay by dgr73 · · Score: 1

      Because I didn't watch the South Park episode, so I don't know about Chipotlaway.

    7. Re:Yay by GameboyRMH · · Score: 2, Informative

      I met a guy in an Asterisk training course who was using it for telemarketing, and he told us it's commonly used in the industry :( It just seems so wrong...

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
    8. Re:Yay by WaywardGeek · · Score: 1

      Asterisk supports Skype [digium.com]. As does FreeSWITCH [freeswitch.org].

      From your link: "The SFA product will be the only solution that integrates Asterisk directly with Skype." It costs something like $80, and is closed-source. With an open-source Skype client, I doubt Digium's closed-source solution will remain the only solution for long.

      --
      Celebrate failure, and then learn from it - Nolan Bushnell
    9. Re:Yay by Anonymous Coward · · Score: 0

      I think you should stop eating burritos if they make you 'poop' your drawers.

  2. GUI Code Only by jisatsusha · · Score: 5, Insightful

    open gui code, but not communicate library.

    Not quite open source then, but I guess it's better than the situation right now. Still no way of ensuring there are no backdoors in the encryption though.

    1. Re:GUI Code Only by Nerdfest · · Score: 5, Insightful

      If you have the client code, you can pre-encrypt before the communications layer if you need the added security.

    2. Re:GUI Code Only by Anonymous Coward · · Score: 2, Insightful

      You're assuming you can feed anything into their comms layer. I suspect there'll be a heavy duty validation / sanity checking at that point already.

    3. Re:GUI Code Only by asdir · · Score: 3, Interesting

      Can someone please translate? Does that mean that an open client could be forked that works with skype but is not skype? Like, say, gizmo or ekiga? Thanks for enlightening a non-techie Linux enthusiast (yes, we exist :-) ).

    4. Re:GUI Code Only by quippe · · Score: 4, Insightful

      If you have the client code, you can pre-encrypt before the communications layer if you need the added security.

      *Could* that be possible, you would lose interoperability with windows clients, so why not relying on one of the truly foss voip projects availble?

    5. Re:GUI Code Only by Drakonik · · Score: 1

      Pretty much, as long as you could change the front-end to use some other VOIP protocol other than Skype. In fact, what I'd like to see is something like Pidgin for VOIP. Transparent support for many protocols. Then you can just have your contact list of friends and call them, regardless of what they use.

    6. Re:GUI Code Only by fearlezz · · Score: 3, Insightful

      Because a truly foss voip project requires a server or open ports on at least 1 side.
      Skype requires only 2 clients that speak the same protocol, the skype network handles the rest.

      --
      .sig: No such file or directory
    7. Re:GUI Code Only by hitmark · · Score: 2, Interesting

      sounds a bit like how the N900's phone and messaging system will work.

      --
      comment first, facts later. http://chem.tufts.edu/AnswersInScience/RelativityofWrong.htm
    8. Re:GUI Code Only by fearlezz · · Score: 1

      Okay, it's not really open source. But it does allow a whole range of new applications. For instance: sipskype bridges (for asterisk or any other pbx).

      --
      .sig: No such file or directory
    9. Re:GUI Code Only by dopeghost · · Score: 1

      I'd say no. Given the likely chance that they will open source only the gui code and not the protocol library, the program might as well be closed source. A program like Pidgin that wanted to include skype support would have to include a pre-compiled 'blackbox' file to actually communicate with anything, and since the source for this was not available, it could no longer be distributed as open source.

      --
      This UID is 7651 digits too high to subjectively infer IQ from.
    10. Re:GUI Code Only by BobMcD · · Score: 5, Interesting

      *Could* that be possible, you would lose interoperability with windows clients, so why not relying on one of the truly foss voip projects availble?

      I recently took my Warcraft guild down a voice-comm path from Ventrilo to Mumble. Mumble had a lot of things going for it - open source, penny-for-a-year server deal, and a much better experience overall. Everyone could hear everyone and the software worked great without a hitch. That being said, as of today we are back on Vent.

      See, while it worked great for us, no one else had ever heard of it, and no one would switch to it just for the benefit of talking to us. In the end we found Mumble made our lives more complex and in sum-total was not a better choice than Ventrilo.

      Vis-à-vis Skype - yes you would need a special client to handle encryption, but a simple checkbox could re-enable traffic with those Windows clients. What truly foss voip project inter-operates with those?

    11. Re:GUI Code Only by Malc · · Score: 1

      What would this do to their codecs, which are presumably optimised for regular voice/video? Would it increase the bandwidth requirements?

    12. Re:GUI Code Only by SLi · · Score: 1

      I doubt that. If the binary part is the codec+protocol, good luck trying to stuff anything except audio (and preferably voice then) through it. Lossy compression works poorly for encrypted data.

    13. Re:GUI Code Only by SLi · · Score: 5, Insightful

      It wouldn't work at all. Nearly all voip, and I'm sure Skype is no exception, uses lossy compression for the audio. If you stuff encrypted data in, you'll just get garbage out.

    14. Re:GUI Code Only by TheRaven64 · · Score: 1

      Most SIP clients I've seen support STUN, which allows two NAT'd clients to talk to each other. The basic way that it works is for both clients to send a UDP packet to the STUN server. Their stateful NATs then set up a mapping from the public port to the private port. The server then forwards the address and port to each of the parties and then they can communicate with each other on that port. This needs a server set up on the public Internet, but so does Skype (so you can find the peer to peer network).

      --
      I am TheRaven on Soylent News
    15. Re:GUI Code Only by Anonymous Coward · · Score: 0

      Time to bust out some FEC. But that's just crazy.

    16. Re:GUI Code Only by jim_v2000 · · Score: 1

      How do you validate audio?

      --
      Don't take life so seriously. No one makes it out alive.
    17. Re:GUI Code Only by Alpha+Whisky · · Score: 1

      Most SIP clients I've seen support STUN, which allows two NAT'd clients to talk to each other. The basic way that it works is for both clients to send a UDP packet to the STUN server. Their stateful NATs then set up a mapping from the public port to the private port. The server then forwards the address and port to each of the parties and then they can communicate with each other on that port. This needs a server set up on the public Internet, but so does Skype (so you can find the peer to peer network).

      You just made fearlezz's point for him, I've highlighted the points where you did it. Yes, Skype needs servers, but the whole point is that Skype provides servers, some penniless foss project isn't going to provide servers which can cope with 18,989,413 clients at the same time (number plucked from Skype right now, the peak is probably higher).

      --
      it's = it is

      its = belonging to it

    18. Re:GUI Code Only by buchner.johannes · · Score: 1

      There is already a Skype API for (gui) programs to use. It operates on text commands.
      For example, you can already integrate Skype into Pidgin: http://code.google.com/p/skype4pidgin/
      And with some pidgin plugin for encryption (both on the Windows and Linux side, e.g. OTR or PGP), you can have private (text) conversations.

      --
      NB: The message above might reflect my opinion right now, but not necessarily tomorrow or next year.
    19. Re:GUI Code Only by Anonymous Coward · · Score: 0

      Shouldn't a normal NAT, like Linux's iptables is a symmetric type of a NAT? Then all communications has to happen through Skype servers.

      http://en.wikipedia.org/wiki/STUN

      STUN is just a NAT type discovery. It is not a panacea to circumvent good NAT implementations. The only way to avoid NAT is to not to use NAT and that will only happen with IPv6. Use IPv6 and NAT hacks like STUN are over.

    20. Re:GUI Code Only by Anonymous Coward · · Score: 1, Insightful

      How do you encrypt the audio?

      Assuming you are doing the encryption before the comms layer then..

      a) you could have done this already without the source code.

      b) you would have to do it the old way - analog style encryption in the digital domain. As the data is then put through lossy audio compression afterwards, this would leave very little bandwidth for the speech. The lossy compression may make most kinds of audio encryption impossible anyway.

    21. Re:GUI Code Only by TheRaven64 · · Score: 1

      And every SIP provider also runs a STUN server. I can use the STUN server that my SIP provider runs for any communication, not just communication with them or mediated by them, and there are other public STUN servers. You need to enter the address of one (or select one from a list of public ones), but you need to enter the address of your mail server into a mail client and end users seem to be able to manage that...

      --
      I am TheRaven on Soylent News
    22. Re:GUI Code Only by PReDiToR · · Score: 1

      Unless you can accurately predict how the datastream will be compressed.

      Sounds like a job for ... Oh who cares? It's still a proprietary protocol.

      !opensource

      --

      Do not meddle in the affairs of geeks for they are subtle and quick to anger
    23. Re:GUI Code Only by FireFury03 · · Score: 2, Insightful

      Because a truly foss voip project requires a server or open ports on at least 1 side.

      Plenty of free public SIP servers on the internet...

      Skype requires only 2 clients that speak the same protocol, the skype network handles the rest.

      I'm unclear on why you think that relying on the existence of a single proprietary network is better than relying on a SIP server (which may or may not be operated by yourself and you can switch to a different independent server if you want).

    24. Re:GUI Code Only by FireFury03 · · Score: 1

      some penniless foss project isn't going to provide servers which can cope with 18,989,413 clients at the same time (number plucked from Skype right now, the peak is probably higher).

      It is unlikely that a single project would need to support that many clients at the same time since SIP is a standard protocol which allows servers from many different service providers to interoperate, so the load is spread across many different providers. Additionally, you seem to be limiting yourself to "peniless FOSS projects" but there are a large number of commercial SIP servers out there who are supported by money made from gatewaying calls to/from the PSTN, etc.

      By your argument, none of the existing open standard protocols for other services are feasible either. I mean, absolutely no one is going to use SMTP to transfer their email because no single provider is going to provide enough capacity to support all the users. Except you're clearly wrong because SMTP is in wide use precisely _because_ no single provider has to support all the users. Even so, there are plenty of large service providers out there providing this service to a very large number of people (Google Mail, Hotmail, etc).

    25. Re:GUI Code Only by shaitand · · Score: 1

      "but you need to enter the address of your mail server into a mail client and end users seem to be able to manage that..."

      Really? That is news to me. Last I checked end users need a disc from the ISP to do that, or they call their tech, or in a real pinch their teenager.

    26. Re:GUI Code Only by Dark_Gravity · · Score: 1

      It wouldn't work at all. Nearly all voip, and I'm sure Skype is no exception, uses lossy compression for the audio. If you stuff encrypted data in, you'll just get garbage out.

      How would that be any different than unencrypted Skype for Linux?

      Ever since upgrading to the recent Linux client, all I get is garbage out.

    27. Re:GUI Code Only by Anonymous Coward · · Score: 0

      That depends on the location of the cut. If the codecs are hooked into the proprietary code, then yes, pre-encryption would just result in garbage on the other side of the compression-decompression. If they only keep the networking part a secret (P2P structure, encryption, etc.), then additional encryption could be added after compression but before the stream enters the proprietary code. That said, a binary module from that company is still very likely a trojan horse, so I don't care if additional encryption is technically possible.

    28. Re:GUI Code Only by jgrahn · · Score: 1

      Not quite open source then, but I guess it's better than the situation right now.

      No, a worse situation. More people will become locked into a proprietary protocol, and ...

      Still no way of ensuring there are no backdoors in the encryption though.

      ... and it's also that.

    29. Re:GUI Code Only by gerddie · · Score: 1

      Afaik Pidgin uses plugins, so if the blackbox file was compiled properly (i.e. of 64 bit with -fPIC) one could create a plugin that is loaded at run-time. Important is what you need to compile and link it, libpurple is LGPL, so no problem, but pidgin.h in pidgin-dev states its GPL, so if that's needed, then it can not be distributed.

    30. Re:GUI Code Only by Anonymous Coward · · Score: 0

      They get an ISP disc for every email address they email? That's news to me...
      If they can handle typing username@domain.top for email, they can handle an SIP-address which is in the exact same format.

    31. Re:GUI Code Only by Walzmyn · · Score: 1

      Yeah, but maybe somebody will fix the damn bug where my picture disappears when I expand a video chat.
      Or the KDE guys could make it mesh so I don't have to disable desktop effects
      Or there's the bug that about 1 out of 4 times when I expand the video chat window, the actual image of the other caller stays the same..

      Yeah, the skype people could fix this. But they haven't for a long time and frankly I've got more faith in the FOSS community. They fix everything else that's wrong with my computer pretty quickly.

    32. Re:GUI Code Only by BikeHelmet · · Score: 1

      My experience was a bit different.

      We were using Ventrilo, but one person had a really crackly mic, so I googled for alternatives and suggested Mumble. We tried it, and the guy was instantly clearer. Nobody had any problems hearing him.

      Too bad the crackly mic syndrome was passed on to me. On two computers, Mumble is completely useless - it's so bad they can barely hear me.

      We're back in Vent, because even with his crackly mic, he's more understandable than I was. :P

    33. Re:GUI Code Only by Bootarn · · Score: 1

      It's not enough. Having a binary library still prevents Skype from running on ARM based netbooks, for example.

      Seems like there might be a revolution in the works

      I fail to see how open-sourcing a GUI is a revolution of any kind.

    34. Re:GUI Code Only by hitmark · · Score: 1

      do people even use mail clients any more?

      seems most use some sort of webmail interface these days...

      --
      comment first, facts later. http://chem.tufts.edu/AnswersInScience/RelativityofWrong.htm
    35. Re:GUI Code Only by Kashgarinn · · Score: 1

      Mumble is great.

      it's invariably better than ventrilo for all the things you listed. Why would you even consider going back? You just tell people it's effing awesome, and if you don't use it, you're a noob: http://www.videosift.com/video/N00B-Boyfriend

      "no one would switch to it just for the benefit of talking to us." - so it's not the programmes fault, it's that no one likes you?

      Grow some balls and use mumble.

    36. Re:GUI Code Only by BobMcD · · Score: 1

      Instead I chose to grow some balls and make the best choice for my group's objectives - playing World of Warcraft, as opposed to/rather than supporting open source software.

      If Mumble wants to gain some traction, they ought to look at accepting Ventrilo clients.

    37. Re:GUI Code Only by shaitand · · Score: 1

      If they don't want their data to be an ISP's hostage they do. And if they don't want their inbox searched by the FBI without warrants.

      Of course the anti-spam effort have pretty much outlawed private mail servers so downloading/deleting the mail as fast as you can is about all you have left.

    38. Re:GUI Code Only by fearlezz · · Score: 1

      I'm saying that a single proprietary network is technically better. It's just that the average person can't install or configure a sip softphone, while skype is accessible to the masses. How many people do you know, that take a laptop with a sip client with them on vacation? I know just one: myself. But I know several people who bring their laptop with skype.

      That's exactly what makes skype so interesting. A lot of our customers live on other continents. Since they know how to install skype, it could save a lot of money if office users could skype through the pbx.

      --
      .sig: No such file or directory
    39. Re:GUI Code Only by FireFury03 · · Score: 1

      It's just that the average person can't install or configure a sip softphone

      Really? What makes it so much harder than Skype? The only additional thing the user needs to do is enter the SIP server address - this is akin to configuring an email client, which is something "the average person" has been doing for years.

    40. Re:GUI Code Only by fearlezz · · Score: 1

      The realm, outbound proxy, a STUN server and/or NAT settings, DMTF protocol, the codec. Which are named different on the different softphones, and never located on the same page. And optionally the port, of course some umts providers block sip. Not to mention that several sip providers lock logins to their fixed ip.

      SIP is really really great for us techies. But i'm pretty sure that at most 5% of my colleagues could configure a softphone.

      --
      .sig: No such file or directory
    41. Re:GUI Code Only by FireFury03 · · Score: 1

      The realm, outbound proxy

      Most people aren't going to be using an outbound proxy, so complaining that everyone needs to configure it is bunk.

      a STUN server and/or NAT settings, DMTF protocol,

      The defaults are fine for this stuff for the class of user we're talking about.

      the codec.

      Autonegotiated - leaving this as the default is fine unless you have some specific requirement.

      And optionally the port

      Again, the class of user we're talking about here will not need to touch this.

      of course some umts providers block sip.

      Such UMTS providers will no doubt have contractual terms prohibiting *any* VoIP, not just SIP. Also, plenty of UMTS providers block Skype too.

      Not to mention that several sip providers lock logins to their fixed ip.

      Eh?

      SIP is really really great for us techies.

      Ok, let me run you through what I did to get Ekiga working on my system: I fired it up, stuck in my user name, password and server address. That's it. Now admittedly, the server happens to be a Callweaver server that I run, but that is irrelevant - it could equally be a commercial SIP server and would have been just as easy to set up in Ekiga.

      Similarly, to get SipDroid working on my cellphone, I simply put in my username, password and server address. And to get my F1000G wifi phone working, I did exactly the same (note: the F1000G is an unstable piece of crap, don't buy it).

      But i'm pretty sure that at most 5% of my colleagues could configure a softphone.

      You must work with some really thick people then. If you can configure your email client, you can configure a SIP phone. There really isn't anything complicated about it. Sure, there are lots of settings you _could_ change for specific situations, but for the users we're talking about here they can pretty much leave everything set to defaults except the username, password and server address.

  3. WTF is "the nearest future"? by wcrowe · · Score: 2, Interesting

    I'm trying to grasp what could possibly be the "nearest future"? A picosecond from now? But of course, you could have half a picosecond, and half that, and half that, etc.

    --
    Proverbs 21:19
    1. Re:WTF is "the nearest future"? by jisatsusha · · Score: 5, Funny

      Planck time, of course.

    2. Re:WTF is "the nearest future"? by Galestar · · Score: 1
      --
      AccountKiller
    3. Re:WTF is "the nearest future"? by unts · · Score: 1

      Keep halving it and eventually you'll be in the present.

    4. Re:WTF is "the nearest future"? by clone53421 · · Score: 1

      lim future(t)
      t->now+

      --
      Alexander Peter Kristopeit bought his basement from his mommy for one dollar.
    5. Re:WTF is "the nearest future"? by clone53421 · · Score: 3, Insightful

      Yes, but it'll take infinitely long to get there...

      --
      Alexander Peter Kristopeit bought his basement from his mommy for one dollar.
    6. Re:WTF is "the nearest future"? by Ignatius · · Score: 1

      sort of

          t_planck = sqrt( hbar * G / c^5 ) = 5.3912e-44 s

      see http://en.wikipedia.org/wiki/Planck_units for details.

    7. Re:WTF is "the nearest future"? by Anonymous Coward · · Score: 0

      In several languages, the superlative (formed in English like "nearest") can also mean something more along the lines of "very near." I imagine this is probably the case in French. It isn't in English, but a non-native speaker might not notice when he goes to translate his superlative expression into English.

    8. Re:WTF is "the nearest future"? by mister_playboy · · Score: 3, Funny

      Actually, it's impossible to be anywhere other than the present.

      --
      Do what thou wilt shall be the whole of the Law ::: Love is the law, love under will
    9. Re:WTF is "the nearest future"? by clone53421 · · Score: 2, Funny

      Free candy tomorrow.

      --
      Alexander Peter Kristopeit bought his basement from his mommy for one dollar.
    10. Re:WTF is "the nearest future"? by Anonymous Coward · · Score: 0

      In several languages, the superlative (formed in English like "nearest") can also mean something more along the lines of "very near." I imagine this is probably the case in French. It isn't in English, but a non-native speaker might not notice when he goes to translate his superlative expression into English.

      Correct. English "next" is simply a variant of "nearest". Compare German nahe and nächst (pronounced exactly like "next").

    11. Re:WTF is "the nearest future"? by Kjella · · Score: 1

      Would you mind telling my head that? It keeps leaping back and forth and sometimes warps it altogether.

      --
      Live today, because you never know what tomorrow brings
    12. Re:WTF is "the nearest future"? by hldn · · Score: 1

      in the nearest future, future events will affect us all in the nearest future. future.

      --
      http://www.accountkiller.com/removal-requested
    13. Re:WTF is "the nearest future"? by Anonymous Coward · · Score: 0

      >>nächst (pronounced exactly like "next")

      It's not.

    14. Re:WTF is "the nearest future"? by unts · · Score: 1

      I suspect YOU know that *I* knew that, but still, I'm disappointed that you got modded insightful and I didn't get a "funny" :(

    15. Re:WTF is "the nearest future"? by clone53421 · · Score: 1

      Yes; well, the mods appear to be hard to please today. I didn't get anything for this comment, either.

      --
      Alexander Peter Kristopeit bought his basement from his mommy for one dollar.
    16. Re:WTF is "the nearest future"? by rdnetto · · Score: 1

      Yeah, but *whose* present?

      --
      Most human behaviour can be explained in terms of identity.
  4. This could be incredible... by BobMcD · · Score: 4, Interesting

    I use a lot of voice software on my laptop, and Skype is one of the few that is fine with my not using a headset. I'm not certain how it does it, but I assume they're filtering the sound coming out of the speakers against the mic input. I've always wanted to take Skype's client and plug it into, say, Ventrilo.

    Could this open up that possibility?

    1. Re:This could be incredible... by Anonymous Coward · · Score: 0

      I don't have a problem with most of my voice chat apps and not using a headset. However, they're all push to talk setups.

      Skype will on occasion enter a feedback loop and start outputting this horrible wail. As soon as I make a noise, it stops, but only for a while.

    2. Re:This could be incredible... by BikeHelmet · · Score: 1

      I'm not certain how it does it, but I assume they're filtering the sound coming out of the speakers against the mic input.

      Shifting windows. The software waits for a unique and easy to identify sound or frequency to be played, then tries to detect it. It checks how long it took for it to be picked up, then establishes a rough time for when the filtering has to be done, which is usually accurate within 1ms.

      The filtering is beyond me - but I'm surprised programs can get the first bit so wrong. Measuring audio "ping" is easy - and if you don't immediately discard your played back audio from the buffer, surely some smart coder or mathematician can figure out how to filter it out?

      I suppose skype also considers acoustic characteristics like distance from speakers to mic, and records how the frequency is altered when playing/hearing a "control" sound, to make the filtering more effective?

      I knew there was a purpose for the startup sounds programs play! :P

  5. Seems largely pointless. by fuzzyfuzzyfungus · · Score: 4, Insightful

    With something like Skype, pretty much all the stuff of interest is in the protocol(and the weird stuff that it gets up to, burrowing through firewalls and being designed to be heavily resistant to inspection and so forth). The UI isn't ghastly; but it isn't very interesting.

    Obviously, this is exactly why Skype would be OSSing the GUI and not the protocol binary blob; but it is also why the news isn't of much interest. As long as basically all the program's important functions depend on a binary blob you can't see what it is doing, you can't port it to other architectures, you are really no better off than if the whole thing were binary.

    1. Re:Seems largely pointless. by Anonymous Coward · · Score: 2, Interesting

      I agree that this isn't news, but I don't think it's pointless.

      With the binary blob being available as library (well, it is speculated anyway), one can VoIP-enable one's own applications (whether it's an IM cilent or tech support tool) with a piece of code that is tested and is known to work well under all kinds of different configurations. A lot of the free VoIP out there isn't quite up to snuff, and requires a lot of end-user mucking around to get to work.

    2. Re:Seems largely pointless. by Anonymous Coward · · Score: 0

      Ding ding ding ding ding!!! You win the prize. If they're not OS'ing the protocol, this is utterly meaningless.

    3. Re:Seems largely pointless. by Youngbull · · Score: 2, Insightful

      you could potentially integrate Skype into Empathy or Pidgin if the license is right so I think it's a good thing!

    4. Re:Seems largely pointless. by Interoperable · · Score: 1

      As a few other have pointed out, it could lead to a lot more clients supporting the Skype protocol. Integration into the Linux desktops and their messengers/VOIP clients could be a real advantage. I certainly wouldn't mind dropping one extra piece of software in favor of a more integrated approach. It may also provide some useful code for webcam interfaces since they can still be patchy on Linux machines.

      --
      So if this is the future...where's my jet pack?
    5. Re:Seems largely pointless. by Hurricane78 · · Score: 1

      Yes you are. If you think like me: Wrap the whole thing in a server. Don't even think about writing a GUI for it. Write a SIP wrapper. Then put that gateway on one single server, and tell Skype to go fuck themselves. ^^

      --
      Any sufficiently advanced intelligence is indistinguishable from stupidity.
    6. Re:Seems largely pointless. by DdJ · · Score: 1

      It's neither completely perfect nor completely worthless.

      If they're actually putting the protocol implementation out as a binary-only library, and encouraging open source development on top of that, this enables some freedoms without enabling all freedoms.

      For example, this makes it possible for me to write a program that monitors a twitter feed, looks for certain keywords in it, and when it finds them, calls me via Skype and uses my own text-to-speech code to read the message containing the keyword out loud to me.

      In theory, it also lets me implement my own IVR application on top of the protocol. You know what I mean, "say yes to continue", that kind of crap. We could build an IVR Wikipedia tool for the blind with this.

      So: some freedoms, yes, but certainly not all the freedoms folks might want.

      If you think about it, it's really a little like using a credit card processing system. You have hooks to do certain financial transactions, and building that into your applications lets you do valuable things, but you don't have the complete freedom to do whatever you want with the financial protocols.

    7. Re:Seems largely pointless. by Malc · · Score: 1

      I would love a UI that makes sense, on Win32 and Mac OS X.

    8. Re:Seems largely pointless. by Anonymous Coward · · Score: 0

      Almost every complaint I have seen about people using skype on linux are about integration with the OS (particularly sound/video APIs and hardware drivers). There are plenty of people who don't like the closed nature of the protocol, that's not likely to change and they mostly use other VoIP/IM software.

      Even with a binary blob there is much that can be done to improve the robustness and integration of the software. It's true that it's not a huge step forward in getting skype support for other architectures.

    9. Re:Seems largely pointless. by FireFury03 · · Score: 1

      one can VoIP-enable one's own applications

      You can already do this by using an industry standard VoIP protocol. There doesn't really seem to be much benefit in using an undocumented proprietary protocol instead.

      A lot of the free VoIP out there isn't quite up to snuff, and requires a lot of end-user mucking around to get to work.

      If by "low end mucking about" you mean typing in your chosen service provider's address, like everyone's done with email clients since the dawn of time. Hell, if you enjoy being locked into a single vendor there are a number of service providers that ship locked down SIP clients so you don't even need to do this.

    10. Re:Seems largely pointless. by FireFury03 · · Score: 1

      If they're actually putting the protocol implementation out as a binary-only library, and encouraging open source development on top of that, this enables some freedoms without enabling all freedoms.

      Sounds quite dangerous to me - you're needlessly giving a third party the option to pull the plug on your project if they desire whilst also integrating all their security holes, backdoors and downright bad programming into your software.

      We could build an IVR Wikipedia tool for the blind with this.

      But why would you want to use a proprietary protocol with limited software and hardware support to do this? Seems more sensible to use an industry standard protocol.

      So: some freedoms, yes, but certainly not all the freedoms folks might want.

      I don't see this as giving people much freedom. I see it as giving people just enough rope to accidentally hang themselves by tempting them into using an inappropriate technology in preference to well supported and proven industry standard technologies.

    11. Re:Seems largely pointless. by DdJ · · Score: 1

      But why would you want to use a proprietary protocol with limited software and hardware support to do this? Seems more sensible to use an industry standard protocol.

      I don't have enough information at my fingertips to respond to this. Are there any industry standard protocols for this that are already as widely deployed today as Skype? That are already being used by as many customers in as many settings? If so, sure. If not, that answer might provide the answer to your own question above.

      I do know that whenever I hear about people doing general-purpose IP telephony, I hear about exactly two things: either Skype, or some service where the fact that it's IP-based is irrelevant and you should just treat it like a normal phone call. Now, maybe all those other things are using standard protocols, but if so, I'm not sure that helps much if you end up going through the old phone networks anyway.

      (If you add special-purpose IP telephony, you'd have to add Ventrilo and TeamSpeak to the list of things I hear about all the time. But those also use proprietary protocols.)

    12. Re:Seems largely pointless. by Zerimar · · Score: 1

      eBay doesn't own the protocol, so you'll have to go to Joltid if you want that portion open sourced.

    13. Re:Seems largely pointless. by FireFury03 · · Score: 1

      I don't have enough information at my fingertips to respond to this. Are there any industry standard protocols for this that are already as widely deployed today as Skype?

      Yes - SIP is by far the most common industry standard protocol, predates Skype and is used pretty much everywhere. If you have a VoIP system in your office it is almost certainly SIP based, and the PSTN is increasingly using SIP internally.

    14. Re:Seems largely pointless. by Weezul · · Score: 1

      Skype's front end & brand were sold to eBay for a shit ton of money, but the creators held onto the protocol. Skype's original creators recently threatened suit over the underlying protocol. An open source Skype could redevelop the underlying protocol.

      --
      The Christian religion has been and still is the principal enemy of moral progress in the world. -- Bertrand Russell
    15. Re:Seems largely pointless. by kimimo · · Score: 1

      Hi, just wanted to let you know that our team at imo.im has actually implemented skype into our IM client (https://imo.im) without actually having to download skype. Does this help you?

  6. Good riddance, crappy ugly Skype client by neiras · · Score: 1

    Hopefully this means that libpurple, telepathy et al will be able to make Skype calls.

    Once you get users out of a proprietary client, it's that much easier to transition them to a more open equivalent.

    "You mean I just get a SIP account and calls cost less than with Skype?" Sold!

    1. Re:Good riddance, crappy ugly Skype client by Anonymous Coward · · Score: 0

      Telepathy can already make Skype calls on Maemo 5/N900. SIP too. But no Skype video calls yet.

      The problem with transitioning of course is when they ask "how do I call my Skype buddies with SIP?"

    2. Re:Good riddance, crappy ugly Skype client by neiras · · Score: 2, Informative

      The problem with transitioning of course is when they ask "how do I call my Skype buddies with SIP?"

      It works for the calling-landlines case. For everyone else, there are SIP->Skype gateways like Gizmo5's OpenSky.

    3. Re:Good riddance, crappy ugly Skype client by shutdown+-p+now · · Score: 1

      Hopefully this means that libpurple, telepathy et al will be able to make Skype calls.

      That's pretty much it - this is the only real advantage to be derived from this. Not Skype somehow becoming "open", but that Pidgin, Ekiga etc can all support it as yet another protocol.

      I wonder also... even if they release it as a Linux libskype.so, I can't imagine it being very strongly tied to Linux. I mean, how many system APIs would such a thing really need? Mostly just networking... and otherwise it's just x86 (and hopefully also amd64) code. In that case, it could probably be wrapped into a loader and API shims that would let it be used in Windows as well - it would be tricky, but the makers of a few popular multi-network clients (such as Trillian) might be willing to go to those lengths.

  7. IOW by pedestrian+crossing · · Score: 2, Informative

    Not OSS. Nothing to see here, move along...

    --
    A house divided against itself cannot stand.
    1. Re:IOW by daid303 · · Score: 2, Informative

      Yes it is OSS. It's not GPL, but an open source frontend with the right license would still be OSS.

    2. Re:IOW by binarylarry · · Score: 1

      So then the Nvidia drivers are OSS right? I mean they ship with some open source parts.

      FAIL

      --
      Mod me down, my New Earth Global Warmingist friends!
    3. Re:IOW by daid303 · · Score: 3, Informative

      The open source parts are open source (shocking!), just like an open source frontend on top of closed source libraries still is an open source frontend.

      Is the full driver then open source, no. Is full Skype open source, no. But is the driver glue open source, yes. Is the frontend open source, yes.

    4. Re:IOW by shadowknot · · Score: 1

      The open source parts are, the closed source parts aren't. Characterizing the entire package as OSS would be wrong but to say it's not open source at all is also wrong.

    5. Re:IOW by quippe · · Score: 1

      The open source parts are, the closed source parts aren't. Characterizing the entire package as OSS would be wrong but to say it's not open source at all is also wrong.

      The OSS GUI is dependant on the closed library; viceversa you cannot say the library is dependant on the GUI.
      So if you want a FOSS system implementation, having skype means installing non-FOSS whichever is the GUI -> FAIL

    6. Re:IOW by Anonymous Coward · · Score: 0

      When (if) the code is released, Skype will be *exactly* as OSS as the Nvidia drivers.
      Which the community labels as not open source.

    7. Re:IOW by 2muchcoffeeman · · Score: 2, Informative

      Yes it is OSS. It's not GPL, but an open source frontend with the right license would still be OSS.

      If the underlying driver isn't also GPL'd, then it's not open-source.
       
      And as long as we don't have access to that underlying driver, we have no way to guarantee that there's no backdoor into our communications.
       
      Of course, we already know that the Austrian interior ministry has confirmed it has no problem listening to Skype conversations.
       
      If Austria can do it, it seems likely that other governments have that capability (even if they claim otherwise despite documentation to the contrary).

      --
      Prevent Windows piracy. Use Linux instead.
    8. Re:IOW by jisatsusha · · Score: 1

      You're absolutely right about that. But to claim that "Skype for Linux to be open-sourced" is misleading at best, if it only includes a small portion of the Skype codebase.

  8. protocol will probably be ... binary-only by TheGreatOrangePeel · · Score: 5, Insightful

    So, assuming the OP is right, they're basically open-sourcing a telephone where the only thing you can change is where the numbers are placed and what the handset looks like. Maybe I'm missing the point, but how does this benefit anyone?

    1. Re:protocol will probably be ... binary-only by RanCossack · · Score: 2, Interesting

      So, assuming the OP is right, they're basically open-sourcing a telephone where the only thing you can change is where the numbers are placed and what the handset looks like. Maybe I'm missing the point, but how does this benefit anyone?

      Well, that's not a bad analogy at all... to answer your question by continuing it a bit, imagine "what the handset looks like" is "covered in spikes" and "where the numbers are placed" is "at random" on their default handset.

    2. Re:protocol will probably be ... binary-only by jareth-0205 · · Score: 1

      I'd say that having a bit more control of the implementation of sound would lead to less problems in the future (the constantly-moving linux sound architecture has until recently had Skype on a constant catch-up). Also could lead to integration with Pidgin or similar IM-aggregators, which wouldn't be a bad thing.

    3. Re:protocol will probably be ... binary-only by FlyingBishop · · Score: 1

      Well, you also have control over the cord that connects the handset to the receiver, so you have a lot more control over how the sound gets to you than you would otherwise.

      But I'd rather use Pidgin.

    4. Re:protocol will probably be ... binary-only by AcidPenguin9873 · · Score: 1

      How about integrating the binary-only Skype support into Ekiga or Pidgin or whatever other open-source video/conference/chat programs? Gets close to using one program for all of your real-time communcation needs, regardless of protocol...Skype was the big missing protocol in most of those programs, IMHO. Hopefully it wouldn't be too hard to write a wrapper layer around the binary Skype library and make it appear as just another protocol library/plugin to those programs.

      Also as FlyingBishop brought up, it takes the (somewhat buggy) audio/mic/video/webcam support out of their closed code, so hopefully it will get cleaned up or just replaced entirely by Ekiga/Pidgin/etc.

    5. Re:protocol will probably be ... binary-only by bill_mcgonigle · · Score: 1

      where the only thing you can change is where the numbers are placed and what the handset looks like. Maybe I'm missing the point, but how does this benefit anyone?

      Are you old enough to remember when we had to rent phones from the telephone company? When you couldn't
      go to an electronics store and by the phone you want? Suffice it to say, the Bell phones stunk, if you wanted to do anything but what they expected you to (the quality was great for sitting at a desk and talking). My childhood friends' mothers all had 50' handset coil cords and these soft plastic cushions glued on the back so they could talk while working in the kitchen. Today, cordless/headset is a no-brainer.

      Skype's echo cancellation on non-headsets is fantastic. I can just sit in front of a laptop and talk without any tuning. Once OSS gets there it will be 'good enough' and disrupt Skype, but until then, better to have the option of using a decent client.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
  9. Did you RTFM ? by BESTouff · · Score: 1

    Nowhere in the article (er .. blog post) it's said that there will be a binary component. It's just a guess from a comment from some random guy. So no need to ague ad libitum on what will be Free software or not, let's wait.

  10. Nope by ledow · · Score: 4, Insightful

    I call bullshit. I think it's just a tech support guy misunderstanding (and it seems a bi-lingual conversation so the chances of that are even higher).

    Open-sourcing Skype is very different to allowing Mandriva to add a non-trademarked icon to the Skype software (a bit like bundling Firefox - fine so long as you respect the trademark on the name and/or the logo and their requirements), or put a Mandriva icon onto the package etc. The two are discussed interchangeably and I don't see how they are related.

    I think it's more likely a massive misunderstanding on the basis of zero evidence / poor translation. At best, I reckon that Skype for Linux will allow itself to be packaged more easily.

    1. Re:Nope by Mooga · · Score: 3, Funny

      I agree, I just called Microsoft and they also told me that they would "open source Windows 7 in the nearest future."

      --
      ~ Mooga
    2. Re:Nope by Anonymous Coward · · Score: 2, Informative

      Story has been confirmed at the Skype Linux blog:
      http://share.skype.com/sites/linux/2009/11/skype_open_source.html

      They are making an open source UI to allow better integration with distros.

    3. Re:Nope by ofaurax · · Score: 3, Informative

      First, I'm not an employee of Mandriva. I didn't ask for anything other than an official skype RPM for Mandriva, on the skype download page or on the Mandriva repositories (in "non-free"). There's nothing to do with icons or trademark. As english is not my native language, I asked for clarification when reading "part of the opensource community". The answer is "will become open source in the nearest future." If you don't trust my language skills, just read the "blockquote tag" answers from the tech support. I only copy/pasted.

  11. Cautiously Optimistic? by mrpacmanjel · · Score: 1

    From a practical perpsective this is good news and a step forward.

    However, if part of this "open source" announcement means a binary-blob needs to be included on an open-source OS (e.g. Linux) should we still be worried?

    Off the top of my head I can think of graphics cards, wireless network adapters, software and scanner-type devices that need binary "blobs" to be usable.

    I am worried because this could be a growing trend of reliance on companies policy of releasing binary only software onto a open-source OS.

    E.g. I have a laptop with an ATI-based graphics card (r200M). I have been using the closed source driver to enable me to enjoy meaningful 3d-accelerated performace on my laptop. Unfortunately the new version of the driver(9.10?) now considers my card "legacy" which means the previous version (9.2) will not compile with the latest Xorg release.

    If the driver was *fully* open source then at least something can be done about it.

    I had to deal with this with MS Windows - it's one of the many reasons I use Linux.

    1. Re:Cautiously Optimistic? by lbbros · · Score: 1

      IIRC R100+ chips are supported by the open-source Radeon driver, which also includes 2D, 3D and kernel mode-setting.

      --
      A CC-licensed illustrated horror novel
    2. Re:Cautiously Optimistic? by BitZtream · · Score: 2, Insightful

      I had to deal with this with MS Windows - it's one of the many reasons I use Linux.

      Perhaps you jumped to Linux without considering that it wasn't the end all be all solutions that you were told it was?

      When switching from Windows to Linux you give certain things up, when switching from Windows to MacOS you give certain things up, and indeed when switching from Linux to * you give certain things up. If you didn't, they would all be equal/the exact same and you'd have no reason to switch at all.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
  12. Abandonware in 3....2....1.... by mpapet · · Score: 4, Insightful

    This is the same old story. The business doesn't want to support a Linux client so they open the code they have and abandon it.

    I didn't bother reading TFA so maybe someone else can inform us how would one go about acquiring the binary blob in the future? What distros will the blob track? What about an ARM build? Ebay wants to limit their dev hours but abandoning the gui doesn't help them much.

    Which is why I think they'll just abandon the OS altogether sooner rather than later and put a happy face on it with this stunt.

    --
    http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
    1. Re:Abandonware in 3....2....1.... by charlesnw · · Score: 1

      Um.... maybe you didn't notice but Ebay sold skype to a VC firm.

      --
      Charles Wyble System Engineer
    2. Re:Abandonware in 3....2....1.... by petrus4 · · Score: 1

      This is the same old story. The business doesn't want to support a Linux client so they open the code they have and abandon it.

      Yes, but doesn't it being open code, mean that you can then host it on Sourceforge etc, and then develop it yourself? If the company is giving you the source, they don't need to keep doing the development for you; you can take it in the direction you want.

    3. Re:Abandonware in 3....2....1.... by wagnerrp · · Score: 1

      What distros will the blob track?

      What makes you think they will 'track' any distro? If they're OSing the GUI, the only thing left in the blob is some networking and crypto code. That can easily be statically linked, and then you just let the distros handle the UI dependencies on their own.

  13. How slashdot works by RiotingPacifist · · Score: 4, Funny

    1) In a bilingual conversation, Skype support employee says "Skype will from now on be part of the open source community."
    2) Blogger posts saying that Skype will be open sourced in nearest future
    3) get reposted on various blogs
    4) ???
    5) Verified "news" on slashdot

    --
    IranAir Flight 655 never forget!
    1. Re:How slashdot works by DMiax · · Score: 1

      4) when requested clarification, support states explicitly "it will be open sourced in the nearest future" in plain english (as all the rest of the conversation was, only the blog is bilingual)
      FTFY (F as in "filled")

    2. Re:How slashdot works by ofaurax · · Score: 1

      "will become open source in the nearest future." is from the tech support, not from me.

    3. Re:How slashdot works by Kjella · · Score: 1

      5) Verified "news" on slashdot

      6) Other more or less reputable news media "lifts" it from slashdot
      7) Somebody references it on wikipedia
      8) Other more or less reputable news media "lifts" it from wikipedia
      9) Somebody adds more sources to wikipedia
      10) Welcome to 1984 - and then some

      --
      Live today, because you never know what tomorrow brings
    4. Re:How slashdot works by Veggiesama · · Score: 1

      11) Increased attention causes Skype PR person to officially deny rumors, and everyone forgets this whole non-event ever happened.

  14. The first thing I'll build: by Hurricane78 · · Score: 0, Troll

    A Skype-SIP gateway server. And then abandon all and everything that is Skype from my systems. (Except for the gateway on one server, of course.)
    I'll open-source that too, and will make huge enterprisey pitches for the PHBs, until the closed-source virus that is Skype dies out for all eternity, until the end of all time.

    --
    Any sufficiently advanced intelligence is indistinguishable from stupidity.
    1. Re:The first thing I'll build: by JustNiz · · Score: 1

      Why bother copying Skype's protocol? Just do your own and make it opensource. And of you run your own free server (just make money from advertising or something, not charge for the service itself) you'll take customers away from Skype immediately.

    2. Re:The first thing I'll build: by Anonymous Coward · · Score: 0

      Oh look! A skype SIP gateway http://www.skype.com/go/sip/

  15. Re:haha! by dgr73 · · Score: 0, Redundant

    Mod parent redundant

  16. SKYPE? by Anonymous Coward · · Score: 0

    U mean the worst VIOP/Teleconference software out there? Who even uses it? They must be on the way out to consider such a move.

  17. Preencryption: only maybe by Anonymous Coward · · Score: 0

    If they use some kind of codec, it would assume certain things about the data (being voice data, frequency limits and spectrum, etc.) which might be totally mixed up by prepending an encryption. So maybe sound quality would be horrible, or decryption on the other side totally impossible.

  18. It is not opensource, until... by mi · · Score: 2, Insightful

    Now, this probably only means the client (the underlying protocol will probably be handled by a binary-only library), but even if that's the case, it seems like there is still reason to celebrate

    The source is not open, until I can build and use it on FreeBSD/amd64 or some other "exotic" platform like that...

    Interestingly, the oft-criticized Java has always been more "open-sourced" (even before going GPL), than what the excited write-up is preparing to "celebrate"... Must all be about managing expectations...

    --
    In Soviet Washington the swamp drains you.
    1. Re:It is not opensource, until... by True+Grit · · Score: 1

      Now, this probably only means the client (the underlying protocol will probably be handled by a binary-only library), but even if that's the case, it seems like there is still reason to celebrate

      The source is not open, until I can build and use it on FreeBSD/amd64 or some other "exotic" platform like that...

      Interestingly, the oft-criticized Java has always been more "open-sourced" (even before going GPL), than what the excited write-up is preparing to "celebrate"... Must all be about managing expectations...

      Right, and the reason for Java's more 'openness' was because its equivalent of a protocol (its bytecode specification) was just as 'open' as the rest of it.

      This is the Internet we're talking about, open protocols are *FAR* more important than open clients of closed protocols.

      Have we already forgotten the history MS & SAMBA? Hello?

      Except for Skype users, who are already locked-in to the protocol, there really *is* nothing to see here, so folks, lets just move along...

  19. Re:Abandonware in 3....2....1.... or not by nangus · · Score: 1

    I would actually be perfectly happy with a situation like this. This was as far as I can understand the original purpose of the gpl before people started going crazy and getting greedy. People wanted to be able to fix software that was created and then abandoned. With the source being closed the only way to fix a closed chunk of software would be to totally recreate the software using best guess as to what it was doing and how.

    If a manufacture no longer wishes to support something, this is the best solution imo. OSS can never truly become abandoned, if I find some software that I like and it is no longer supported.

    I am free:
    --take the software
    --update the libraries
    --fix any bugs
    --share (maybe start a project so other people can make fixes)
    --???
    --profit.

    That is what the gpl meant to me before people got greedy, before people started to worship, before it became a religion...

  20. having visual hallucinations by viralMeme · · Score: 1

    "The business doesn't want to support a Linux client so they open the code they have and abandon it"

    How do you deduce this from a single blog post ..

    "the Linux Skype version will become open source in the nearest future"

    1. Re:having visual hallucinations by dotgain · · Score: 1

      How do you deduce this from a single blog post ..

      Maybe he isn't. Perhaps he's drawing from his experience over the last decade of vendor after vendor treating FOSS like a red-headed freckled stepchild.

  21. update from linuxcrunch by itwadi · · Score: 2, Informative

    After contacting Skype's representative,Linuxcrunch.com got an update for this issue: "We appreciate our user community's enthusiasm and realize this is something they have been wanting for a while. We realize the potential of the open source community and believe that making Skype for Linux an open source application will help to speed up its development and enhance its compatibility with different versions of Linux. While it is our goal to make Skype for Linux source code available to the community in the nearest future, we are not at a point to disclose an exact release date yet."

    --
    http://www.itwadi.com
  22. The audio support is ghastly by xant · · Score: 1

    Skype is a huge source of pain when people discuss Linux audio. It's possible to get it working (mainly by pretending pulseaudio doesn't exist), but so many people have so many problems with it that there's still a widespread belief that it's completely broken. If only the client-facing parts get open sourced, the audio interface ought to be part of that. The protocol, as far as I can tell, works pretty damn good (despite it occasionally telling me someone's offline when I know they're not). I'm fine with not having access to that. But I really want someone to put in decent audio compatibility.

    --
    It's rare that you're presented with a knob whose only two positions are Make History and Flee Your Glorious Destiny.
    1. Re:The audio support is ghastly by Zencyde · · Score: 1

      I can't help but agree with you more on this. My only problem with getting Skype to work is getting it to find my microphone. Yet, I can't seem to do that. Hopefully this FOSS stuff will, indeed, fix the problem.

      --
      What day is it? Could you please tell me?
  23. Speculations suck by Anonymous Coward · · Score: 0

    Skype is an evil closed source platform as we speak.

    I believe it once I see it. And "open sourced" can mean anything at all, tell me the license when the deed is done. If it's done!

    In other news Luxemburg might declare war on the US of A...

    We don't need shit like this on /. thank you.

  24. The first thing I'll download. by Ostracus · · Score: 1

    "I'll open-source that too, and will make huge enterprisey pitches for the PHBs, until the closed-source virus that is Skype dies out for all eternity, until the end of all time."

    Much like Apple will die out. Here's a clue, Skype did for VOIP what Apple did for computers. Made it easier for the average person to be a participant.

    Right now getting Skype running is simple download, install, run, create account, enjoy. SIP is a little less Plug and Play.

    --
    Shai Schticks:"You don't make peace with friends, you make peace with enemies"
    1. Re:The first thing I'll download. by FireFury03 · · Score: 1

      Skype did for VOIP what Apple did for computers. Made it easier for the average person to be a participant.

      Not really. Skype made VoIP more _visible_ because they happened to be pretty good at marketing, but the only thing "easier" about it is the lack of customer choice. Compare:

      Skype: Install it and it works.
      SIP: Choose a service provider, install a client, enter your service provider's address and it works.

      So the only real difference here is that with Skype you don't have to pick a service provider, which means that you don't get to choose the one that is going to be most suitable for you. I guess if people are too lazy to shop around for a good deal then they deserve everything they get.

      Admittedly, Skype tries to work around people with busted network configurations - in these cases the choice comes down to: SIP - doesn't work at all, Skype - works but the connection is unusably bad.

    2. Re:The first thing I'll download. by Disgruntled+Goats · · Score: 1

      So the only real difference here is that with Skype you don't have to pick a service provider, which means that you don't get to choose the one that is going to be most suitable for you.

      I'm pretty sure most people installed Skype because they made the determination that it was the most suitable for themselves. I don't see any reason why someone would be using Skype if they didn't it suitable for their use.

    3. Re:The first thing I'll download. by FireFury03 · · Score: 1

      I'm pretty sure most people installed Skype because they made the determination that it was the most suitable for themselves.

      I'm pretty sure they installed Skype because they didn't know there were any alternatives. To a lot of people, Skype and VoIP are synonymous.

    4. Re:The first thing I'll download. by Disgruntled+Goats · · Score: 1

      I'm pretty sure they installed Skype because they didn't know there were any alternatives. To a lot of people, Skype and VoIP are synonymous.

      And yet they wouldn't continue to use it if they didn't find it suitable for their own use.

    5. Re:The first thing I'll download. by FireFury03 · · Score: 1

      And yet they wouldn't continue to use it if they didn't find it suitable for their own use.

      Did I say it was unsuitable for their own use? No, I did not - I said that they don't get to choose what is the most suitable for them.

  25. Yessssssssss! Not. by Anonymous Coward · · Score: 0

    You'd throw a party for just about anything it seems. Who cares if they threw us a bone (GUI). Unless they free the protocol, stop making fuss for no reason.
    Free as in binaries included. Pfft.

    PS. No really, what would we be happy about?

    1. Re:Yessssssssss! Not. by bjhavard · · Score: 1

      PS. No really, what would we be happy about?

      The main reason that this is good news is that the current client has a number of problems (audio / video compatibility issues with various sound systems, cameras etc) and that the closed Linux development has been glacially slow. Even if the protocol is still closed, the OSS community can help sort out these problems and add enhancements, making the client better for everyone.

  26. This .. by SlashDev · · Score: 1

    .. is not open source. There is no such thing as partial-open source software, if that were the case, I could write software code in Perl that shows an interface, that calls DLL functions and call it open source. Sorry, no reason to celebrate here... Move along..

    --

    TOP DSLR Cameras Reviews of the top DSLRs
    1. Re:This .. by Keyper7 · · Score: 1

      While I agree that going fully open source would be better, opening up the GUI is good because we no longer are forced to comply with Skype developers' concept of usability and aesthetics. There mere fact that I will now be able to get rid of that damned MANDATORY tray icon is a good reason to celebrate.

  27. Official statement from Skype by Keyper7 · · Score: 2, Informative
  28. does skype even run on 64-bit machines? by drfireman · · Score: 1

    Last I checked, a few months ago, there didn't seem to be any simple options for running skype on a 64-bit GNU/Linux machine.

    1. Re:does skype even run on 64-bit machines? by vlm · · Score: 1

      Last I checked, a few months ago, there didn't seem to be any simple options for running skype on a 64-bit GNU/Linux machine.

      http://wiki.debian.org/skype

      "Video did not work for me, but otherwise it was all fine."

      --
      "Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
    2. Re:does skype even run on 64-bit machines? by Disgruntled+Goats · · Score: 1

      So basically it's highly useless for the loads of people because they want the video function.

    3. Re:does skype even run on 64-bit machines? by Anonymous Coward · · Score: 0

      Could of been a v4l version 1 incompatability?

      Google v4l1 using v4l2

  29. Re:haha! by dgr73 · · Score: 1

    Mod parent redundant, not offtopic.

  30. About time... by MikeUW · · Score: 1

    I remember getting reamed-out by a support tech on the Skype forums for even hinting that an open source client might make solving problems alot easier - I hope he enjoys eating his words now.

    Ever since moving to Linux, Skype has been the only thing other than MS Office that doesn't have an equal in terms of both quality and user base (at least, where user base is a factor). The main problems with Skype on Linux has been its ability to keep the client compatible with the constantly changing landscape in sound systems, from OSS, to ALSA, to PulseAudio, to ...? Add to that the multitude of versions/distros, etc. If the client is open sourced, then you can download the responsibility of porting the application to different environments onto those with the skill/time/inclination to do so. And if nobody ever does port the client to sound system x on distro y, then at least they would have a valid reason to say there's not enough demand to bother.

    Just my general opinion anyway.

  31. Less than ideal, but a huge improvement by feranick · · Score: 1

    Obviously the protocol will remain closed source. However everything else, apparently will be open. Basically anybody can build not Skype support into their applications. For example Empathy will have built in support for skype, or even GoogleTalk! Now this is less than ideal. But given that the main problem in the current client is the mess in which it has to operate (PulseAudio support, mainly), and the painfully slow development cycle, this can only be good news.

    1. Re:Less than ideal, but a huge improvement by Jeremy+Visser · · Score: 1

      For example Empathy will have built in support for skype, or even Google Talk!

      Are you trying to imply that Empathy doesn't already support Google Talk?

      'cause if you are, you're wrong -- it has supported Jabber for years (install package telepathy-gabble if it doesn't work for you), and the latest couple of versions have even supported Jingle-based voice and video chat.

    2. Re:Less than ideal, but a huge improvement by feranick · · Score: 1

      No, no! My wrong wording. I mean to say that Google talk will be able to support Skype. Apologizes...

  32. Corporate "open source" for... by CAIMLAS · · Score: 1

    The corporate meaning of "open source" seems to be, as often as not, "we will not support it any longer, but we want a client on your platform and you can use it". Their support and implementation of the Linux client thus far has been, if anything, sub-par and fairly static in development changes.

    --
    ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
  33. Bluetooth support finally? by Anonymous Coward · · Score: 0

    Maybe some FOSS hackers can finally make bluetooth work on Skype. (and I don't mean bluetooth libraries from 2002)

  34. Works for me by Jeremy+Visser · · Score: 1

    I use 64-bit (Ubuntu 9.10, Skype 2.1 beta), and video works for me.

  35. I wonder if ... by Anonymous Coward · · Score: 0

    Involvement with Nokia & Maemo has anything to do with this ?

  36. Is audio part of the UI? by kresho · · Score: 1

    Assuming that the UI includes the part how the audio stream reaches the audio driver, this is great news. Someone could finally fix the audio issues (use ALSA non-exclusively or even make it use PulseAudio). Furthermore, this would make it possible to bridge skype and FreeSwitch or Asterisk. Imagine making skype calls an integrated part of your company's telephone network without resorting to dirty tricks!

  37. Excellent News by MundoExchange · · Score: 1

    This will help us out incredibly. As a volunteer organisation helping promote education in Isaan, Thailand this will reduce the potential for costs considerably. We try to use Linux as best we can as we cannot afford to buy expensive operating systems and our computers are getting on a bit and aren't anywhere near as good as modern systems. Our Gap year students, volunteers and founders mostly use Apple + Microsoft to communicate but with Skype being added to Linux we can all keep in touch whilst keeping the costs down. I'm glad Skype have decided to take the road of "multicultural" Open Source developers as the community will drive the project home to a stable finish and ensure that everything is transparent within it. We were thinking of going down the Google Voice route but this has definitely made us change our minds.

    --
    Volunteering for social justice in Thailand, Guatamala and the Dominican Republic.
  38. Can customize the GUI... by js_sebastian · · Score: 1

    With something like Skype, pretty much all the stuff of interest is in the protocol(and the weird stuff that it gets up to, burrowing through firewalls and being designed to be heavily resistant to inspection and so forth). The UI isn't ghastly; but it isn't very interesting. Obviously, this is exactly why Skype would be OSSing the GUI and not the protocol binary blob; but it is also why the news isn't of much interest. As long as basically all the program's important functions depend on a binary blob you can't see what it is doing, you can't port it to other architectures, you are really no better off than if the whole thing were binary.

    Well, the OSS frontend will use the binary back-end, implicitly documenting its APIs to some extent. This means that you can write your own frontend with a better GUI than the horrible one provided by skype. Better yet, one could probably write a plugin for chat/voip applications allowing them to use skype as a backend, so you won't even have to run a separate skype application anymore.

  39. Anonymous Coward by Anonymous Coward · · Score: 0

    What is the drive to continue using a proprietary protocol where there is an open, standards-based protocol (SIP) that already has such a wide-spread implementation? The skype "front-end" being open-sourced provides no more benefit to anybody than MS "open-sourcing" a front-end that writes docx files for the sole purpose of ensuring the survival of their proprietary document formats.

    Besides, if the front-end depends on a closed source library to function it absolutely can not be under the GPL. As Stallman states, allowing this would "open up a hole in the GPL big enough to drive a truck through".

    Garbage. And to the concern about "opening ports for sip" this is also irrelevant unless you are hosting your own SIP server instead of using any of the free SIP services / proxies. SIP+RTP would function in the exact same manner as skype in this regard.

  40. compete with google video chat by rusl · · Score: 1

    When I read this headline my first thought was this is to complete with Google. Google is planning to release google video for linux when they do a netbook OS or something like that. So many netbooks use linux (even though wondows is making inroads). And people buy netbooks for VOIP - I did. Right now Skype on Linux is clunky. It is doable but it is also a pain. Skype is also almost synonymous with VOIP. Few people know what VOIP is but many know what Skype is. Like Kleenex. But Google could disrupt that gravy train because Gmail is so ubiquiotous and it really isn't far away from having the video chat work from "inside" Gmail - if they did it on Linux too for netbooks they could really usurp that title the way Google Usurped Yahoo's king of the search engine title so long ago.

    Just my thoughts. I was pining for the Linux Google Video feature a while ago while I was setting up Skype (and it was a pain) because I thought it might be easier. Also it would be much easier to use with my email addressbook than the few people I have bookmarked in Skype.

    But the problems with Skype in Linux are relatively minor: things you can (and we do) hack around. But this is a big obstacle for many non-techy users like my wife who had to wait for me to do it for her. So if they open up Skype (or just symbolically go through the motions and get more geeky hacking) then may;be they can get over the little bugs like figuring out the quirky microphone settings required for skype to work on my netbook well... such that I don't have to hack it my self and people have no reason to desire a Google replacement.

    Still it will be tough for Skype because Gmail video can really just blow they away if it is done half well - 1 program instead of two - or 0 (browser doesn't count) obstacle to adoption.

    --
    Stupidity is its own reward.