We recently switched from being a small team piloting Mattermost to using Teams as it rolls out to the whole company. We sorely miss Mattermost. It'll be nice to be able to reach more people in the company via chat than we could before, but everything about the UI is lacking, except maybe how replying works.
I'm sorry to hear to hear about that! Just curious, What's better about the replying in Teams? (Disclosure: I work at Mattermost)
The Horror of Microsoft Teams
331–340 of 344 posts
Re: The Horror of Microsoft Teams
#332Earlier quoted context omitted.
Who cares if an application's UI elements look the same across platforms? I want it to work on the platform I am using. I simply do not care what it looks like on someone else's platform, and I especially do not want to pay a performance penalty so some designer can have a virtual feather in their cap over it.
My opinion is that the OS should not be responsible for providing native elements to the application. If this is true then the application is tightly coupled to the OS implementing these components. In a perfect world, every application would have minimal dependencies required by the OS, and completely encapsulate their runtime and UI components, making them very portable... which is basically web apps, hence Electro…
Re: The Horror of Microsoft Teams
#333Some people honestly seem oblivious to any current chat status, launching into complex questions and expecting immediate replies just because you seem alive right now. I’m sorry but once I’m “in conference call” or otherwise really busy, you should get the hint. I shouldn’t need a chat client that lets me be virtually invisible just to get work done.
And generally, I hate chat for work. E-mail/bug-track is enough. I want to deal with things when I actually have time to deal with them, not when someone else assumes I have infinite availability.
Re: The Horror of Microsoft Teams
#334Earlier quoted context omitted.
Apart from some abstract legal paperwork requirements like those, I honestly don't see much difference between both privacy wise. If the company really requires privacy and owning their data, they should setup some hosted slack clone themselves.
AFAIK, Slack will store user data on servers in the US. For most European countries (if not all), Microsoft can guarantee that data won't leave that country. Especially for privacy sensitive sectors (e.g. finance), that can be a hard requirement.
Re: The Horror of Microsoft Teams
#335I could add so much to this, and in fact, recently closed a text file enumerating issues I had with Teams because I felt it wasn't a good use of my time, since I felt like I was the only one having problems with it. A few more points, in case anybody in the Teams team is reading: 1. Implement filters. Filters for teams, filters for channels, filters for search results. I can't filter my Files by file type, so it's a…
Re: The Horror of Microsoft Teams
#336Earlier quoted context omitted.
Reminds me of the NET SEND command in windows 2000-xp. Allowed sending a popup text message to specific (or all with a wildcard!) machines on a network. Sure there were times where such a feature would be convenient ("server going down for maintenance, please save your work", etc), but overall ripe for abuse. They disabled it in a service pack and took it out altogether in subsequent versions.
Back in my senior year of high school during Spanish class I naively used NET SEND to send a message to one of my classmates. The only problem was that I failed to specify the user in the command and instead used *. This ended up sending a message to all computers in the school district. I remember the computer administrator coming into the class saying “Are you aware one of your students is sending messages to the e…
Re: The Horror of Microsoft Teams
#337Earlier quoted context omitted.
I think Teams is exactly excellent because it allows you to secure your collaboration tool. Especially valuable post GDPR where you really don’t want your non-tech savy employers putting privacy data into some online Trello board, or slack/discord for that matter. The fact that teams is just part of your 365 platform is soooo awesome in non-tech enterprise that it’s hard to describe just how useful it is. But basical…
Why is it okay to put data in teams and not in trello?
For any new vendor you can't put the same data unless/until you have all these legal arrangements in place; and if that vendor says "ah, we're in USA, we don't care about GDPR" then you simply can't use them for such data.
Re: The Horror of Microsoft Teams
#338I use both daily. I think the biggest problem with Teams can't be discovered by feature comparisons and performance metrics. Teams enables a company to "secure" the application in the same way other MS products can be. That makes the product easy to sell, but in practice, it prevents Teams from being an effective collaboration tool. If I want to create a new channel, I need to get approval from IT. If I want to invit…
Re: The Horror of Microsoft Teams
#339Earlier quoted context omitted.
That's effectively what I do as well, but we don't have a corporate Slack account. Teams is great for internal communications on long-running projects. It's well suited to that and I wouldn't substitute Slack. When used well, it cuts down on a ton of internal emails and status updates. I don't really blame IT for locking down Teams. It makes a lot of sense for all the reasons you mention and many more. It's just that…
Our Teams is basically completely open and not locked down at all. I still hate it.
Re: The Horror of Microsoft Teams
#340Probably the worst thing for me is that Teams seem to be able to hold like 6 chat messages in memory, if I scroll to the past it starts loading and it takes about 5+ seconds to load 6 more. If I go back it starts to load the messages I just seen again. Performance-wise it's catastrophically bad