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

GitHub staff are required to use Teams by Sep 1, 2023

twitter.com

Post reply on HN
Print view View original

471–480 of 725 posts

Re: GitHub staff are required to use Teams by Sep 1, 2023

#471

Post by Macha »

mk89 wrote: post #217
jacquesm wrote: post #194

Teams is so horrific we banned it. If you force us to use teams you'll have to find another supplier. Seriously, it is incomprehensible that Microsoft would ship something so utterly broken. I know they don't have a reputation for writing good software but Teams is on another level, and I don't mean that in a positive way. I've really tried to get it to work but it is so messed up that I don't think it can be done. M…

What's the issue with zoom? I think it's one of the best software I have on my machine. It never ever stopped working since I have it installed, not even in meetings/webinars with 1000+ people. And the integration with Slack is really convenient, you can start a meeting in seconds anywhere you are.

Meet does not require a desktop client to work reliably (it does, however, require a Chromium browser).

Zoom really tries to bury the browser link. First it says the meeting has launched, which it won't have if you don't have the client installed, then it tries to prompt you to download the desktop client, and only then does it reveal the web join link.

Our security team has banned the installation of Zoom after some of their issues in 2020.

Re: GitHub staff are required to use Teams by Sep 1, 2023

#472

Post by swasheck »

Gravityloss wrote: post #469

Flowdock > Slack > Teams. Slack and Teams have this really bad idea of hiding all messages in threads and having the users click around to find them from threads. Has any tool copied Flowdock's threading implementation? They got it right.

i was taken aback when i saw flowdock is owned by broadcom. seems a weird space in which to find a broadcom offering.

Re: GitHub staff are required to use Teams by Sep 1, 2023

#474

Post by mrguyorama »

blibble wrote: post #413
mrguyorama wrote: post #403

Earlier quoted context omitted.

Uh what? Every "Team" I have on the left side of my teams window has a "X hidden channels" message that I can click and that shows every single channel in the teams, including archived ones.

this is what I have to go through: https://allthings.how/how-to-hide-and-unhide-chat-in-microso...

Oh hiding CHATS, not channels. Yeah that's probably stupid.

Re: GitHub staff are required to use Teams by Sep 1, 2023

#476

Post by mrguyorama »

culopatin wrote: post #459
mrguyorama wrote: post #400

Earlier quoted context omitted.

Nah skype for business was the bomb. It worked exactly like 2005 MSN messenger, was simple, efficient, and screen sharing and video calling was hard so people wouldn't start a damn video call or ask me to join a video call for things that should be a damn email.

Except that keeping track of chats was as much of a pain as it is in teams. Things that were absolutely not a problem in MSN messenger in 2004

Every single chat I had in skype for business caused a transcript to be emailed to me.

Re: GitHub staff are required to use Teams by Sep 1, 2023

#477

Post by generalk »

jerrygenser wrote: post #445
generalk wrote: post #421

Regardless of what you think of Teams -- I myself have had nothing but poor experiences over 2.5 years of using it daily -- it's telling that Microsoft has to require folks to use Teams. I'm sure this is just Microsoft unifying everyone on the same comms platform, but seriously, I don't know anyone who chooses Teams. I know non-tech folks who chose Outlook 365 because of familiarity and then end up on Teams because i…

Why did you need HIPAA Compliance for your chat app? Internal discussion about patients that include PHI?

Bingo. Nearly impossible for our staff to do their jobs and not discuss something considered PHI.

Re: GitHub staff are required to use Teams by Sep 1, 2023

#478

Post by scott_w »

dbancajas wrote: post #470
ygjb wrote: post #209

Earlier quoted context omitted.

I will be blunt. Teams is an awful user experience; I have been using online collaboration tools since the BBS days, and while I appreciate and understand why and what they are trying to build, it is bad software. Every single experience I have had as a teams user in professional settings, interacting with communities, and being required to use it for interactions with my childrens schools since the 2020 shutdowns ha…

What is the specific complaint against it? Better yet can you come up with tools that you use instead of Teams? Is it xoom? Slack? Discord? MS is not my favorite company but my MS Teams experience has been relatively smooth.

> The platform is slow

> I regularly am confused by what I am meant to do, or how to resolve errors that occur;

Just to provide two examples of specific complaints from the parent post.

Re: GitHub staff are required to use Teams by Sep 1, 2023

#479

Post by emmanuel_1234 »

I don't get the hate for Teams. Working from home, it's the best tool I can think of:

- because the app is so slow, our IT suggested to use the web version instead, as such it can't detect the away/available status properly, meaning no one can see if you're in front of your computer working on some other windows, or actually away from your computer - the web app keeps getting disconnected, and fails to deliver messages and notification in time. It also fails to indicate that it's failing. It's therfore customary for message to take several hours to be sent to/received by the other party. It's the perfect excuse for ignoring your colleagues for hours, and be like "Oops. Teams, am I right?", wether you were actually around, or again, doing something else entirely.

Post reply on HN