Urgent.News

the world's headlines, one feed

Editions

Tech

Microsoft has pulled a small but vital Teams update which could have let users ignore all those annoying work chats for good - I just hope it comes back soon

A pulled Teams update could have allowed users to keep annoying chats muted with new controls.

Microsoft has pulled a small but vital Teams update which could have let users ignore all those annoying work chats for good - I just hope it comes back soon

Microsoft has temporarily withdrawn a planned update for its Teams platform that would have allowed users to better organize and ignore unwanted chat notifications. The update aimed to group all muted chats together in a dedicated area, making it easier for users to stay focused and reduce stress caused by unnecessary alerts. However, Microsoft has decided to roll back the update, apologizing for the inconvenience.

The new grouping was designed to help users quickly access and manage their muted conversations while keeping meeting chats separate and easily accessible. Unfortunately, Microsoft has not provided any information on the reason for the delay or when the update will be reintroduced, leaving users to wait for potential relief from the constant influx of chat notifications.

Written by urgent.news from TechRadar's reporting — not their text. Machine-written — it may contain errors, so check the original before relying on it.

Also reported by 1 other outlet

Read the original at techradar.com →

More in Tech

Agile fatigue isn't about Agile. It's about who holds the stopwatch.

Your stand-up routine lasts 45 minutes. No one in that room thinks it's a stand-up routine. You're basically giving a status update with unnecessary details.

  • Agile fatigue stems from lack of trust among team members, not the Agile framework itself.
  • Stand-up meetings often last too long with unnecessary details, perceived as interrogations.
  • Trust erosion leads to developer burnout and disconnect between Agile practitioners and business.

Cómo solucionar el error \"Text content does not match server-rendered HTML\" en Next.js App Router

Cómo solucionar el error "Text content does not match server-rendered HTML" en Next.js App Router Este error ocurre cuando el HTML generado en el servidor (SSR/SSG) no coincide con el árbol de React…

  • Error occurs when server-rendered HTML HTML does not match React's client-side rendered tree
  • Solutions involve using suppressHydrationWarning, useEffect, and proper conditional logic

Why I Don't Put Tenant-Specific Validation in My FastAPI Endpoints

Multi-tenant applications have a way of turning simple endpoints into surprisingly complicated pieces of code. At first, tenant-specific validation seems harmless.

  • Tenant-specific validation complicates fastapi endpoints as they take on too many responsibilities.
  • Pydantic v2's validation context allows tenant-specific rules without hard-coding tenant names.