Microsoft to retire Skype Desktop API

#1

Post by nezza-_- » Sat, Nov 02, 2013, 7:50 PM UTC

Microsoft to retire Skype Desktop API
networkworld.com

Re: Microsoft to retire Skype Desktop API

#2

Post by ffk » Sat, Nov 02, 2013, 8:22 PM UTC

All I can find on their developer webpage that they appear to support is Skype URIs. It's basically HTML tags that register the skype: service to send commands to skype. The functionality appears to be completely one way. The app sends a message to skype and skype takes over from there.

Skype API appears to be the same things as Skype Desktop API which is the ops focus.

SkypeKit which allowed developers to create a headless skype client is no longer accepting new developer registrations. https://support.skype.com/en/faq/FA12322/what-is-skypekit

I can't see anything at all about hardware that supports skype. This is probably through some enterprise BD channel. Hopefully they aren't being abandoned too.

Re: Microsoft to retire Skype Desktop API

#3

Post by wubbfindel » Sat, Nov 02, 2013, 8:25 PM UTC

Anyone know is this will effect the Skype4COM library?

I built a Skype bot using it for work just a few months ago. Really annoying if it is.

Re: Microsoft to retire Skype Desktop API

#4

Post by nezza-_- » Sat, Nov 02, 2013, 8:28 PM UTC

wubbfindel wrote: post #3

Anyone know is this will effect the Skype4COM library? I built a Skype bot using it for work just a few months ago. Really annoying if it is.

According to this it will stop working: http://stackoverflow.com/questions/18822634/will-skype4com-s...

Re: Microsoft to retire Skype Desktop API

#5

Post by matthewmacleod » Sat, Nov 02, 2013, 8:32 PM UTC

Last time I tried to use the Skype API, it was horribly broken, and the documentation was downright incorrect in several places. I guess it's not had any love for a while.

Re: Microsoft to retire Skype Desktop API

#6

Post by wubbfindel » Sat, Nov 02, 2013, 8:32 PM UTC

nezza-_- wrote: post #4

wubbfindel wrote: post #3

Anyone know is this will effect the Skype4COM library? I built a Skype bot using it for work just a few months ago. Really annoying if it is.

According to this it will stop working: http://stackoverflow.com/questions/18822634/will-skype4com-s...

Oh well. That's so daft. Will be either abandoning that project, or switching to another alternative that does support such an API.

Maybe a new API that works well with mobile too will be released in time for us to switch to it. Wouldn't take much to improve on the API, it is (was) horrible.

Re: Microsoft to retire Skype Desktop API

#7

Post by ancarda » Sat, Nov 02, 2013, 8:39 PM UTC

>These changes will significantly improve the call quality and speed of delivery of instant messages, while retaining excellent battery life of mobile devices.

How does scrapping a desktop API affect mobile in this way?

Re: Microsoft to retire Skype Desktop API

#8

Post by yelnatz » Sat, Nov 02, 2013, 9:00 PM UTC

ancarda wrote: post #7

>These changes will significantly improve the call quality and speed of delivery of instant messages, while retaining excellent battery life of mobile devices. How does scrapping a desktop API affect mobile in this way?

If the mobile skype app can call desktops, then maybe they interface with the desktop API.

Re: Microsoft to retire Skype Desktop API

#9

Post by tatata » Sat, Nov 02, 2013, 9:11 PM UTC

who cares, webrtc is here!

Re: Microsoft to retire Skype Desktop API

#10

Post by isaacwaller » Sat, Nov 02, 2013, 9:39 PM UTC

ancarda wrote: post #7

>These changes will significantly improve the call quality and speed of delivery of instant messages, while retaining excellent battery life of mobile devices. How does scrapping a desktop API affect mobile in this way?

Because Microsoft can update the Skype architecture so that it is more centralized like other IM applications. Right now a lot of Skype is peer-to-peer, which is not good on mobile. I, for one, am really looking forwards to this change.