Teams is a nightmare. Instead of just creating the simple chat that everyone was just asking for, they went full PhD and created a mix between a chat and a forum.
A Teams "channel" has counter intuitive behavior, the messages you send are more like forum threads, users can reply to them, and when that happens it reorders the whole messages to put that one at the bottom. It makes it impossible to "catch up" on a channel since people will happily reply to any messages so the ordering is completely random.
There is also a completely counter intuitive distinction between "groups chats" and "channels".
Teams is also the only chat service I know where there is an actual limit on the number of non-public channels you can have. After 30 channels have been created, you're doomed.
Want to remove an existing channel to make room for a new one? Nope, you cannot remove a channel, only "archive" them. Archived channels are removed after 30 days and there is no way to force their removal early. So basically if you reach 30 channels you have to wait minimum 30 days to create a new one.
Did I mention the UI is slow as hell, and half the screen space is used by unnecessary large padding between messages? I am rarely able to have more than 3/4 messages displayed on a 23" screen.
The only positive point of Teams is integration with outlook 365 and meetings. It works really well, quality is good, reliable, nice UI, présentation mode, screen share, etc
> The video chat is really good from experience though.
I have had a few people on calls with poor connection speeds. It degrades horribly by stuttering and distorting audio. It performs worse than a phone call. The best fix would be for Australia to fix its woeful internet.
When you load the web interface it identifies each person with their initials, not full name. This isn’t helpful when you have never met the person before.
Their status page is annoying me more and more with these recent outages.
Recalling the incidents in September, it's a bit cheeky they call that "99.93%" uptime (30 mins of downtime).
Having remembered that there were at _least_ 2 seperate 1 hour+ incidents where I was struggling to send messages in Sept, I went through to look at the history, and they seem to have purposefully hidden these incidents on the calendar. There's no way of listing incidents in a month.
The information and accessibility of the status page is obviously politically motivated by marketing.
If companies were honest, they would multiply downtime by the number of users at the time. Because of course, great uptime doesn't matter if it's only uptime when no one is using it in the middle of the night.
It's like when trains report 95% on time, except that the times when the service is delayed is when the trains are full. All the delays that actual people experience (person-hours) happen in that 5%.
Its interesting, I looked at that page earlier (~1145 EST) and it was actually tagged as an "Outage" rather than the "Incident" it is right now.
For me it has only been slow performance all morning. Its not good, but not what I would call "down" either. At least from my perspective. I could have a bunch of other folks who are completely unable to send messages and I just can't tell.
Be honest to your customers, or I will make sure our team switches to Microsoft Teams.