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

Unofficial Microsoft Teams client for Linux

github.com

Post reply on HN
Print view View original

91–100 of 256 posts

Re: Unofficial Microsoft Teams client for Linux

#91

Post by netsharc »

teo_zero wrote: post #65
drdaeman wrote: post #47

Earlier quoted context omitted.

Screen sharing? Hold on, those extra-advanced features could wait. Microsoft should focus first on message delivery (notifications may be delayed for hours), showing media in chats (picture and videos fail to show most of the time) and just opening conversations correctly from notifications (message from a person opens a group chat, sometimes that forks a conversation, leading to loss of history). That’s the very bas…

If we're listing Team's idiosyncrasies, when you're chatting with exactly one person in a group chat after all the others have left, their name becomes "just me". You won't ever see their real name again.

First rule of Fight Chat: you do not talk about Fight Chat.

The idea of Fight Club but it's a bunch of corporate zombies arguing in a chat room amuses me.

Wait a minute...

Re: Unofficial Microsoft Teams client for Linux

#94

Post by aorth »

ErroneousBosh wrote: post #89
jacquesm wrote: post #69

The official client is absolutely terrible. But, I've found a much better solution: I tell all my customers Microsoft Teams doesn't work for us and they'll have to pick something else. Kudos for at least trying to address this, MS should hang their head in shame, this is not the hardest problem to solve these days. If we could do it in 1995 they should be able to do it 30 years later.

The web-based one works perfectly on Linux. If anything it's better than the native Windows app. Office 365 actually works better in Firefox in Linux than any other browser in Windows. It's like they've kind of given up on the whole OS thing, and have just decided to go with Linux.

True! I've been doing this for years on Linux. I use a dedicated Chromium instance in app mode:

  /usr/bin/chromium --ozone-platform=wayland --enable-features=UseOzonePlatform,WaylandWindowDecorations,WebRTCPipeWireCapturer --user-data-dir=/home/myuser/.config/chromium-ilri --app=https://teams.microsoft.com
Works incredibly well (put this in a `.desktop` file with `Exec=` and you can launch it via your desktop's launcher). Some of the settings may not be needed anymore, as Chromium has come a long way in terms of Wayland support. I use Firefox for everything else, but haven't tried Teams there.

Re: Unofficial Microsoft Teams client for Linux

#95

Post by Too »

ErroneousBosh wrote: post #89
jacquesm wrote: post #69

The official client is absolutely terrible. But, I've found a much better solution: I tell all my customers Microsoft Teams doesn't work for us and they'll have to pick something else. Kudos for at least trying to address this, MS should hang their head in shame, this is not the hardest problem to solve these days. If we could do it in 1995 they should be able to do it 30 years later.

The web-based one works perfectly on Linux. If anything it's better than the native Windows app. Office 365 actually works better in Firefox in Linux than any other browser in Windows. It's like they've kind of given up on the whole OS thing, and have just decided to go with Linux.

If by perfect you mean that you can’t have two chats open next to each other and toggling between chats is slow as molasses then yes.

Re: Unofficial Microsoft Teams client for Linux

#96

Post by varispeed »

jonathanlydall wrote: post #75
hosteur wrote: post #68

Please make an unofficial client for windows too. The official one sucks so much it is hard to even describe.

I use Teams on Windows extensively at work (for chats, calls, meetings, screen sharing). And I have zero issues with it. It’s been really solid for me since that major overhaul they did a couple of years back. Not sure what issues you have, but I wonder if perhaps that us NOT running 3rd party security products is a factor (we only run Windows Defender).

"Works for me, so it must for everyone else"

Re: Unofficial Microsoft Teams client for Linux

#98

Post by ahartmetz »

Tor3 wrote: post #81
Yumako wrote: post #72

Earlier quoted context omitted.

Some of my coworkers connect every day to our calls with Linux machines.

They almost certainly do via the web interface, as I do (and lots of others). It works in general, though for some reason Teams via a web browser will often have problems seeing the microphone, or getting sound, even though every other web page using mic/speaker will work. And some other issues, like not showing a shared screen without first going to chats and then re-expanding the shared screen. When aware of all th…

My Teams client for Linux is MS Edge for Linux with the web app, works pretty well except for slow navigation. File uploads, audio and video all work. Even screen and window sharing on Wayland. The desktop is KDE, so it provides the XDG portals and the compositor. Pipewire does audio and maybe video routing.

Re: Unofficial Microsoft Teams client for Linux

#99

Post by dontlaugh »

WD-42 wrote: post #76
jacquesm wrote: post #69

The official client is absolutely terrible. But, I've found a much better solution: I tell all my customers Microsoft Teams doesn't work for us and they'll have to pick something else. Kudos for at least trying to address this, MS should hang their head in shame, this is not the hardest problem to solve these days. If we could do it in 1995 they should be able to do it 30 years later.

The saddest part is that they copy and pasted Skype, which was a decent program at the time. If you open pamixer and look at applications using audio it still shows up as Skype there. At least as of a few years ago.

Some of the audio stack is probably still from Skype.

Re: Unofficial Microsoft Teams client for Linux

#100

Post by EbNar »

jacquesm wrote: post #69

The official client is absolutely terrible. But, I've found a much better solution: I tell all my customers Microsoft Teams doesn't work for us and they'll have to pick something else. Kudos for at least trying to address this, MS should hang their head in shame, this is not the hardest problem to solve these days. If we could do it in 1995 they should be able to do it 30 years later.

Teams is literally the worst program I have ever used. Whoever designed that interface should be publicly shamed.
Post reply on HN