590
Report: Microsoft to face antitrust case over Teams
(arstechnica.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 13 May 2024
590 points (98.8% liked)
Technology
59562 readers
1981 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
how resource heavy and slow for what it is, how notifications break a lot of the time, how obtuse and unintuitive it usually is to do some simple stuff like sharing meetings and how everything thats not an absolute core feature will glitch out 8 times out of 10.
i'm sure some of these were fixed while they broke other stuff, they fuck around with it all the time. im thankfully not being forced to use it for a while right now.
To add: how I have "2 unread messages", but nothing when filtered for unread. My phone will forever have 2 unread messages.
We used Teams at the last org I worked at, we rarely had issues. The UI wasn't bad in my eyes, we had integrated our phone system into teams too. Calling someone on the other side of the country via teams was simple.
Admittedly the service did get worse before I left and there were a couple of Microsoft outages which cut all our text based communications for a day (phone system still worked)
I'm using slack right now but would prefer something self-hosted but that's well out of the scope of the current mob I'm with.
Not sure how long it's been since your last org, but a lot has changed in the Teams universe as of late (and mostly not for the better).
Eh, it works pretty well in our org. We use it for almost all of our meetings, and we have pretty much no issues. Then again, our entire team is on macOS and we have it integrated at the corporate level (so meeting rooms and whatnot use it), and it's a pretty solid experience.
My main complaints are:
We use Slack for text communication and impromptu video chats, so the chat issues don't bother me all that much.
so your main complaints are that its most basic usecase sucks, but it works quite well. which is it?
Chats are not the most basic use case for Teams, meetings are. And meetings work pretty well.
If you ever reach a point where self-hosting does become a possibility, I'd recommend checking out Mattermost.