this post was submitted on 13 Nov 2024
1717 points (96.1% liked)

Technology

59555 readers
3421 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
 

That’s all.

EDIT: Thank you all for detailing your experience with, and hatred for, this miserable product. Your display of solidarity is inspiring. Now, say it with me:

Fuck Microsoft

you are viewing a single comment's thread
view the rest of the comments
[–] sunbeam60@lemmy.one 55 points 1 week ago (2 children)

In mean aside from the fact that almost all of that story is completely wrong, it’s a good story.

Source: Used to work at Microsoft and worked a lot with people from the Skype team.

[–] ToucheGoodSir@lemy.lol 28 points 1 week ago (2 children)
[–] sunbeam60@lemmy.one 94 points 1 week ago* (last edited 1 week ago) (1 children)

Skype made the call negotiation go through a central server (as does all systems nowadays). Skype was originally built on Kazaa technology to punch through firewalls without a central coordinator and that’s what Microsoft removed. They didn’t remove it to track the calling but to enable larger group calls on weaker devices which required video mixing on a central system rather than peer to peer call (where weaker peers couldn’t decode that many video streams). Calls up to 4 are still routed peer to peer if the backend can find routes through all firewalls.

Very very little of Skype was in the new Teams if anything. Teams was a rewrap of Communicator calling tech and was a response to Slack. The real time chatting had nothing to do with Skype either.

Skype lingered in Microsoft for a couple of reasons; Microsoft was crap at acquiring businesses back then, thinking that a hands off approach was best. It meant Skype never really became a proper Microsoft team - they still felt and acted like Skype employees and they didn’t manage to affect Redmond very well. Being acquired is super hard especially when almost all of the bigger business was in a different time zone and a different culture.

I was at a leadership development workshop with a tonne of Skype leaders about 10 years ago. They were still feeling incredibly frustrated and not understanding what was expected of them. It was a botched acquisition and the fault was on both sides.

[–] RaoulDook@lemmy.world 3 points 1 week ago (1 children)

So Teams calls of 1-4 people can send traffic direct peer-to-peer if they're on the same LAN right?
Do all calls of 5+ users stay centrally hosted on the cloud? These are the kinds of things that MS should document and make easily available for IT and firewall admins. Finding info on Teams ports wasn't easy in my experience.

[–] sunbeam60@lemmy.one 3 points 1 week ago* (last edited 1 week ago)

You’re way outside my scope of knowledge - I know a bit about the decisions they took 10 years, and not very much on what is happening today. I would imagine some of these limits are configurable and dynamic. I really don’t know.

[–] OsrsNeedsF2P@lemmy.ml 3 points 1 week ago

You should write a post sometime about what you know from the internals of Skype. I would read it.