Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Microsoft to retire Skype Desktop API

networkworld.com

Post reply on HN
Print view View original

11–20 of 75 posts

Re: Microsoft to retire Skype Desktop API

#11

Post by ancarda »

isaacwaller wrote: post #10
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.

I don't see how that affects the API.

    [API] --> [Skype] --> [Other Skype Clients]
Rather than:

    [API] --> [Skype] --> [Microsoft Servers]
Changing how the network is built shouldn't affect the API in this way since there's an abstraction layer (The Skype program). It would really only affect those who have reverse engineered the Skype protocol and built their own clients.

As for making Skype more centralized, yes, that will improve the experience for mobile users but it can be done without scrapping the API.

IMO, this is an excuse to scrap it and not a legitimate reason.

Re: Microsoft to retire Skype Desktop API

#13

Post by ffk »

isaacwaller wrote: post #10
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.

Skype moved away from peer to peer for supernodes. Here's the article: http://arstechnica.com/business/2012/05/skype-replaces-p2p-s...

Re: Microsoft to retire Skype Desktop API

#14

Post by anonymfus »

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?

Windows powered laptops and tablets are and always were mobile devices for Microsoft.

Re: Microsoft to retire Skype Desktop API

#16

Post by fluxon »

"The Desktop API was created in 2004 and it doesn’t support mobile application development." So what? Desktop users built Skype with their Skype-to-phone and phone-to-Skype (Skype Number) subscription money. We want what we paid for: Skype API, and whatever apps and devices are supported by it. Mobile will necessarily have different apps and devices with some (perhaps) overlap. Developers should be courted to redeploy their apps to a Mobile API if they like, and if their customers want. Microsoft should leave Desktop alone, rather than dumbing it down and damaging ongoing Desktop product value. Microsoft has been perennially wrong about product value. This is just one more bold misstep.

Re: Microsoft to retire Skype Desktop API

#17

Post by fluxon »

WhiteDawn wrote: post #15

Anyone know if you can still use an older client to use the api? I guess if you can it's just a waiting game till the client becomes unsupported.

I just got a forced update with no way to cancel. But I haven't gone to OldApps to see how far back to go so that A) forced updates don't happen and B) the API and apps still work reliably. Don't know which version at which those two criteria are satisfied.

Re: Microsoft to retire Skype Desktop API

#20

Post by vyrotek »

A company I used to work for is panicking over this. One of their core products had an integration with Skype using Skype4Com for various reasons. They came to me recently asking if I had any recommendations for a better platform. (They knew Skype was a temporary hack but didn't expect it to die this fast)

Basically they need a white-labeled, web-based video conference solution. They'd like centralized recording with the recordings accessible via an API and support 1-to-1 and 1-to-N broadcasts. They've played around with TokBox and UStream but they're not the greatest fit.

If anyone knows of a company or is working on a startup in this space I'll gladly point them that direction. They're a global e-learning company with huge government/education contracts.

Post reply on HN