MS Teams is down
teams.microsoft.com
teams.microsoft.com
I hope it burns with fiery hot flames.
Teams is not quite as bad in terms of stability. The UX and performance are terrible though.
Yet.
The PWA is ass.
Re: sibling comment: I'm European, not native English speaker.
HN is lucky to have so many non-native English speakers and they/you are all welcome here. We don't let HN users criticize others for their English - especially since most of the rest of us have no second language at all.
Error descriptions are probably too much to ask these days - I would bet they'd be perceived as intimidating by the UX group, given that the same group seems to prefer a level of discourse appropriate for grade-school classrooms.
A error code would be wonderful, though, since it would be a nice unique search term. It could be put in small greyed-out text in a bottom corner, too, to make everyone happy.
Rust's community got huge benefits out of work to improve the error messages from its compiler and tooling, but we didn't see a lot of real effort to mimic that even in other programming languages, let alone the wider tool ecosystem. A few people, here and there, put in some effort, but nothing at scale.
For Rust this work was imperative because their slogan is "A language empowering everyone to build reliable and efficient software" not "A language with terrible error messages that only nerds can handle" so I'm not surprised other people weren't doing this before Rust showed how much difference it makes, but I was surprised they didn't learn from that.
There’s an effectively-secret deployment of Mattermost Cloud for the “teams without whom the company cannot exist”.
Anything official that needs to be shared and recorded for the company or requires widespread notification is through Teams, but then individuals are all using their own apps and management thinks Teams satisfaction is above 90% according to some surveys that no one I've talked to has filled out.
Published Time: 6/28/2023 7:50:04 AM
Current status: We’re reviewing a recent configuration change which may have unexpectedly resulted in impact. We’re determining our next steps to resolve the impact.
This quick update is designed to give the latest information on this issue.
Published Time: 6/28/2023 7:17:19 AM
Title: Users may be unable to access the Microsoft Teams service
User impact: Users may be unable to access the Microsoft Teams service.
More info: Users may be unable to load Microsoft Teams via the "teams.microsoft.com" web page and desktop app.
Users may see an “Operation failed with unexpected error” message.
While we're focused on remediation, users with access to a desktop build that is cached, may not experience the impact.
Current status: We’re reviewing application logs to identify the root cause and determine a mitigation plan.
Scope of impact: Impact is specific to users who are served through the affected infrastructure and are not using a cached desktop build.
Next update by: Wednesday, June 28, 2023, at 2:00 PM UTC
Published Time: 6/28/2023 6:43:01 AM
Title: Users may be unable to access Microsoft Teams using web browsers
User impact: Users may be unable to access Microsoft Teams using web browsers.
More info: Specifically, users may be unable to load the "teams.microsoft.com" web page and see the error message "Operation failed with unexpected error."
Current status: We're reviewing service monitoring telemetry to determine our next troubleshooting steps.
Scope of impact: Impact is specific to any user who is served through the affected infrastructure.
Next update by: Wednesday, June 28, 2023, at 2:00 PM UTC
https://www.statista.com/statistics/1033742/worldwide-micros...
are there any new updates on this rewrite?
i guess "just" the MS Teams website has an issue?