Silence-Based Turn Detection Is Breaking Voice AI, and Longer Waits Make It Worse

·3 views

Voice AI systems currently rely on silence detection to determine when a user has finished speaking, triggering a response after a set pause threshold is crossed. This approach fails because people naturally pause mid-thought while speaking, causing the system to interrupt them before they finish. Raising the silence threshold to reduce interruptions introduces a new problem: longer response delays make voice interfaces feel broken, since unlike visual apps there is no loading indicator to signal the system is working. Researchers and developers argue that silence alone is too weak a signal, and that humans actually use syntax, prosody, and semantic completeness to predict when someone is done talking. A more effective architecture would use a lightweight language model to continuously estimate turn-completion probability from partial transcripts, treating silence as just one of several inputs rather than the sole trigger.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

How to Build a Delete Confirmation Modal in React with RTK Query and TypeScript

A developer tutorial published on DEV Community demonstrates how to implement a delete-with-confirmation workflow in a React TypeScript application. The guide uses Redux Toolkit Query (RTK Query) to handle API mutations and automatic cache invalidation after a record is deleted. A confirmation modal is triggered when a user clicks the Delete button, storing the selected agency ID in local state before any API call is made. Upon confirmation, the frontend sends the agency ID to a backend DELETE endpoint, which returns a success message displayed via React Toastify. The tutorial covers the full flow from component state management to API service setup using createApi and fetchBaseQuery.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

No Evidence OpenAI Has a Model Named Astra, Public Records Show

A review of OpenAI's publicly available model documentation through August 1, 2026 found no model named Astra, nor any launch timeline or roadmap entry for one. OpenAI's current documented model lineup centers on the GPT-5.6 family, which includes variants named Sol, Terra, and Luna. The name Astra is associated with unrelated projects elsewhere, most notably Google DeepMind's Project Astra, which has no connection to OpenAI. Experts caution that attaching an unverified model name to a well-known company can lend it false credibility. Decisions involving product planning, procurement, or technical integration should rely solely on OpenAI's official published documentation.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Trelix v2.11.0 Connects Jira and Linear Tickets Directly to Code Graph

Developer tool Trelix released version 2.11.0 on August 2, 2026, adding native connectors for Jira and Linear project-management platforms. The update joins two existing connectors for Xray and TestRail, giving all four integrations a unified interface built on a shared abstract base class. Once a project's tickets are synced, they are immediately wired into Trelix's code graph and begin influencing search rankings, with no manual webhook setup required. Each connector implements the same two methods — validate_config() and fetch() — ensuring missing credentials trigger clear errors before any network requests are made. Linked artifacts are processed in the same sync call rather than deferred to a background batch job, tightening the connection between issue-tracking context and code navigation.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Guide Explains RBAC, Policy-Based and Attribute-Based Authorization in ASP.NET Core

A technical guide published on DEV Community outlines the key authorization models used in modern web applications, including Role-Based Access Control (RBAC), claims-based authorization, and Attribute-Based Access Control (ABAC). RBAC assigns users to roles and grants permissions at the role level, making administration simpler but limiting flexibility for context-dependent access decisions. When role checks alone are insufficient, policy-based authorization in ASP.NET Core allows developers to encode arbitrary logic, such as restricting edits to a post's original author. The guide also covers resource-based authorization, custom authorization handlers, multi-tenant scenarios, and externalized policy engines. It is part of a broader series on authentication and authorization, building on earlier coverage of JWT validation and OpenID Connect.

0 comments Read more at DEV Community