WhatsApp Web Gains Native Audio and Video Calling with Screen Sharing and Device Switching
WhatsApp Web is finally adding native audio and video calling capabilities, allowing home users to make calls directly from the browser without relying on a separate desktop application.
Previously limited to messaging and reading chats, the web version will now feature a dedicated Calls tab displaying call history and favorite contacts. Users will also gain access to screen sharing and reactions, bringing the feature set close to that of the full desktop client.
Meta has enabled seamless call handoff between devices, so a conversation started in the browser or on a computer can continue uninterrupted on a smartphone.
For group calls, waiting rooms are being introduced. The link creator can activate an option requiring approval for entry, manually admitting participants or rejecting unwanted guests. This control is particularly valuable for business meetings.
Further enhancements include background noise suppression to filter out sounds from crowded environments and faster upgrade to HD video quality within the first seconds of a call rather than after initial low-resolution buffering.
Recently, WhatsApp also enabled username reservations, allowing calls to other users across platforms using nicknames without revealing phone numbers.
Related articles
Manticore Search Adds Built-in Authentication and Authorization Starting with Version 27.1.5
Manticore Search has introduced native authentication and authorization capabilities for SQL over MySQL, HTTP/HTTPS endpoints, and replication operations. The feature distinguishes between authentication, which identifies the requester, and authorization, which determines permitted actions such as read, write, schema, replication, and admin. Users can enable the feature via the auth directive in the searchd section of the configuration file, supporting both RT mode with auth.json storage and plain mode with an explicit path. Initial setup requires creating an administrator account, after which additional users can be managed through SQL commands like CREATE USER, GRANT, TOKEN, and SET PASSWORD. The system supports mysql_native_password, HTTP Basic authentication, and Bearer tokens, with mandatory SSL or HTTPS recommended for credential transmission. Detailed logging, permission checks, and phased rollout guidance are provided to minimize disruption in production environments.
88% of Enterprises Run AI Agents but Fewer Than 10% Generate Profits, Ronglian Cloud Reports at WAIC Forum
At the 2026 World Artificial Intelligence Conference, Ronglian Cloud highlighted that while 88% of companies have deployed internal AI Agents, fewer than 10% have achieved meaningful revenue from them. The company, which originated from call center and contact platform services serving tens of thousands of enterprises, organized the fourth WAIC Enterprise Agent Forum focused on evolution and commercial landing. Executives from retail, finance, and electronic signature sectors emphasized that buyers now demand proven ROI rather than token consumption metrics or experimental features. Ronglian Cloud outlined a four-stage maturity model ranging from basic Copilot assistance to fully autonomous business loops, noting most organizations remain stuck between stages two and three. The firm is shifting its own model toward effect-based payments and KPI-driven Agent performance in scenarios such as collections and private-domain operations, where one Agent can manage hundreds of thousands of customers at a fraction of human cost.
OAuth Authorization Server Built Without Storing User Profiles
The article details the evolution of an OAuth Authorization Server that deliberately avoids storing user profiles, relying instead on external identity providers for authentication. It addresses three core constraints: hundreds of dynamically created isolated APIs, a public SPA client without a BFF, and the inability of resources to query the AS on every request. The design separates concerns so the AS handles only clients, tenants, grants, audiences, scopes, keys, sessions, and token issuance while the Main API owns profiles and roles. Tokens are managed securely inside a Service Worker using a custom FedCM grant, eliminating races across tabs and reducing XSS exposure. The approach minimizes blast radius, simplifies compliance, and keeps the AS replaceable without affecting product domain logic.
Why a 202-Character License Key Uses ECDSA P-256 Instead of Ed25519 or RSA
A developer building offline license verification for a .NET desktop application evaluated Ed25519, RSA, and ECDSA P-256 before selecting the last option. The decision was driven by the requirement for zero external dependencies, keys short enough for manual entry from email, and support for key rotation without breaking existing licenses. Although Ed25519 offers faster verification and a smaller public key, it is absent from System.Security.Cryptography in both .NET 8 and .NET 10, with API approval only targeted for version 11. RSA-2048 produces signatures too long for practical use, resulting in a 571-character Base32 string that users would find cumbersome. ECDSA P-256 with SHA-256 delivers a fixed 64-byte signature that becomes a manageable 202-character key when encoded in Base32, while remaining fully available in the runtime. The article also covers performance measurements, the risks of ECDSA nonce generation, and the deliberate choice of the IEEE P1363 signature format to guarantee fixed-length output.