www/adium.im 630:a4857c53da32: Transplant 0bd3fbc04cd0.

[commits at adium.im]

details:	http://hg.adium.im/www/adium.im/rev/a4857c53da32
revision:	630:a4857c53da32
branch:		rewrite
author:		Paul Wilde <me at paulwilde.co.uk>
date:		Sun Mar 18 13:31:49 2012 +0000

Transplant 0bd3fbc04cd0.

diffs (17 lines):

diff -r 645b1cca9a9f -r a4857c53da32 help/documentation/miscellaneous-av-skype-support.htmlfrag
--- a/help/documentation/miscellaneous-av-skype-support.htmlfrag	Sat Mar 17 22:06:35 2012 +0000
+++ b/help/documentation/miscellaneous-av-skype-support.htmlfrag	Sun Mar 18 13:31:49 2012 +0000
@@ -13,6 +13,9 @@
 <p><strong>Yes:</strong> The third-party <a href="http://xtras.adium.im/index.php?a=xtras&xtra_id=5011">Skype Plugin</a> allows Adium to use the <a href="https://developer.skype.com/Docs/ApiDoc">Skype <attr title="Application Programming Interface">API</attr></a> to display your Skype contacts within Adium and let you chat with them via text-based instant messaging. By the nature of the Skype API, it requires that the Skype program be installed and running.</p>
 <p><strong>No:</strong> It's not supported natively within Adium (i.e., without a plugin). The library that we use to support most protocols, <a href="http://trac.adium.im/wiki/LibPurple">libpurple</a>, doesn't support Skype at all right now, not even for chat. Until it does Adium most likely won't, either.</p>
 <p>Keep in mind that Skype is a proprietary, closed protocol, so it must be reverse-engineered before third-party clients like Pidgin and Adium can use it. Protocols like OSCAR (which <attr title="AOL Instant Messenger">AIM</attr> and ICQ are based on) and MSN have already been reverse-engineered, but they're much older than Skype, and reverse-engineering is hard. It will take a long time and won't happen at all unless someone chooses to take interest in it and dedicate significant time to the effort.</p>
+
 <h3>What about the Skype <attr title="Application Programming Interface">API</attr>?</h3>
-<p>We can't package the Skype <attr title="Application Programming Interface">API</attr> with Adium because of licensing issues, as the <attr title="Application Programming Interface">API</attr>'s files are not open source. Also, using the Skype <attr title="Application Programming Interface">API</attr>, as the Skype Plugin, means that Skype needs to be running.</p>
-<p>We want to do it right, with first-class support for the protocol in Adium, whether it's by a reverse-engineered implementation (of sufficient quality) or by an official embeddable library published by Skype. The former hasn't happened yet and we don't foresee the latter happening either, and we don't accept piggybacking on the official client as a substitute. So until one of those two happens, Adium will not have support for Skype.</p>
\ No newline at end of file
+<p>Using the Skype <attr title="Application Programming Interface">API</attr>, as the Skype Plugin does, means that Skype must be running. We don't accept piggybacking on the official client as a substitute.</p>
+
+<h3>What about SkypeKit?</h3>
+<p>The SkypeKit <attr title="Software Development Kit">SDK</attr> is currently in a closed beta and not publicly available. It is not licensed to be used in any open-source software, such as Adium and so needs to be rewritten. <a href="http://adiumxtras.com/index.php?a=xtras&xtra_id=5011">SkypeKit</a> also needs a skypekit-client program to be running in the background, so it puts us in the same boat as using the Skype <attr title="Application Programming Interface">API</attr>. It's certainly not an ideal situation and isn't a "magic bullet" for getting Skype into Adium. We will look at the feasibility of SkypeKit once it comes out of closed beta but until then it can't be used.</p>
\ No newline at end of file