1. You can have skype from official sources on windows, linux, and on OSX. Ok, the experience may be sub par, but I'm pretty sure still better than with a reverse engineered unsupported solution.
2. Skype has lost traction, there is competition widely available. Why invest in something that is loosing popularity, and can have it officially for free?
3. Choosing C for implementing such a project is not a good idea. I'd not choose C for anything personally, but if I had to for whatever reasons, I'd only do it if I had plenty of resources for testing and verification of the solution, as the language has quite some gotchas, and to use it for network facing code, I'd think twice. For a poorly funded reverse engineering work, which will always play catchup with the official solution this is definitely not the tool, as you will have to sacrifice some testing because of the very nature of the project, thus you also sacrifice security. Maybe the sound code can be justified with C.
4. Licensing an unlawfully obtained code as LGPL is pretty controversial imho. (Your readme suggests you reverse engineered skype 5.5 client code. I'm pretty sure you violated the EULA with that. I'd not use your code given these circumstances even if it would work as advertised, but you surely couldn't defend GPL violation lawsuits given these circumstances)
[+] [-] kodfodrasz|9 years ago|reply
Also I'm not sure why would anybody support this.
1. You can have skype from official sources on windows, linux, and on OSX. Ok, the experience may be sub par, but I'm pretty sure still better than with a reverse engineered unsupported solution.
2. Skype has lost traction, there is competition widely available. Why invest in something that is loosing popularity, and can have it officially for free?
3. Choosing C for implementing such a project is not a good idea. I'd not choose C for anything personally, but if I had to for whatever reasons, I'd only do it if I had plenty of resources for testing and verification of the solution, as the language has quite some gotchas, and to use it for network facing code, I'd think twice. For a poorly funded reverse engineering work, which will always play catchup with the official solution this is definitely not the tool, as you will have to sacrifice some testing because of the very nature of the project, thus you also sacrifice security. Maybe the sound code can be justified with C.
4. Licensing an unlawfully obtained code as LGPL is pretty controversial imho. (Your readme suggests you reverse engineered skype 5.5 client code. I'm pretty sure you violated the EULA with that. I'd not use your code given these circumstances even if it would work as advertised, but you surely couldn't defend GPL violation lawsuits given these circumstances)
[+] [-] skypeopensource|9 years ago|reply
[+] [-] eng_monkey|9 years ago|reply