SShortSingh.
0
ProgrammingDEV Community ·

Inertia 3.11 live props let pages refresh on server events without polling

A page showing an order as "Preparing" stays stale after the kitchen marks it ready, forcing customers to refresh. Common workarounds are polling the server or subscribing to a channel and reloading manually, which duplicates logic and fails to recover after dropped connections. Inertia 3.11 introduced live props, where the server declares which channels and events signal a prop has changed, and the browser refetches only that prop when one arrives. The author maintains Guren, a TypeScript fullstack framework on Bun and Hono, which added support for live props in version 2.36 via a live() helper and a WebSocket-based transport. The post walks through a small diner demo with a kitchen board and a customer tracking page, showing setup of broadcasting, a socket route, the client transport, and an OrderUpdated event; the demo's page updated within about 0.12 to 0.17 seconds of each click.

0
IndiaNDTV ·

FBI Seizes $1.2 Billion in Crypto Reported Stolen From Binance

The FBI announced on Thursday that it has taken possession of over $1.2 billion in cryptocurrency that was reported stolen last month from Binance. Binance is the world's largest cryptocurrency exchange by trading volume. The seizure marks a significant recovery of assets tied to the theft. The article provided limited further detail beyond the amount and the timing of the announcement. Reporting is based solely on the FBI's statement as relayed by NDTV.

0
ProgrammingDEV Community ·

osFoundry requires Claude Code to pin a commit when requesting a GitNest check rerun

osFoundry's MCP endpoint exposes a propose_gitnest_check_rerun tool that Claude Code calls to ask for a finished GitNest check to be retried. The tool requires six fields, including an expected change-set version and composition commit, so approval can recheck that the repository state has not moved. The author explains that GitNest's UI reduces check runs to a status using ordered rules where no runs means none, any failure means failed, and only full success means passed. A test script shows that naive shortcuts, such as treating the absence of failures as green, give wrong verdicts in 5 of 7 cases. The author therefore recommends that agents report individual check states rather than a single green verdict.

0
ProgrammingDEV Community ·

Idempotent Webhook Handling and Audited Recovery for Logistics Shipment Events

A design proposal describes how a logistics webhook consumer can process shipment status events exactly once during outages. Each request is authenticated and bound to a tenant before any deduplication occurs, so unauthorized senders cannot reserve event IDs. Deduplication relies on a database uniqueness constraint over the authenticated source, tenant, and event ID, with the deduplication record, shipment update, and audit entry committed in one transaction before acknowledgement. The author notes that a preliminary lookup is insufficient under concurrency, since the constraint must decide which of two simultaneous deliveries proceeds. The approach does not make remote side effects transactional or guarantee delivery order, and a failed database write must withhold success acknowledgement.

0
ProgrammingHacker News ·

Developer Adds RSA Key Support to swift-nio-ssh for Legacy EC2 Access

A developer needed RSA .pem key support to reach older Amazon EC2 instances, but the swift-nio-ssh library intentionally omits it. Rather than wait for upstream changes, they implemented the feature themselves and encountered several technical pitfalls along the way. The resulting work is published as a fork of swift-nio-ssh that includes RSA support and the latest security advisories. A blog post documents the modifications and the lessons learned. The author has offered to answer questions about the implementation.

0
ProgrammingDEV Community ·

Attributing AI Gateway Spend by Service Using Stateful Actors

An AI gateway bill shows total spend but not which service, environment, or tenant caused a sudden rise, which matters when several applications share one gateway. Attribution Wheel, an open-source TypeScript sample running on Telnyx Edge Compute, addresses this by attaching metadata such as service, environment, and tenant to each request via the x-ltg-metadata header. It groups spend by these dimensions, stores one daily ledger row per service, and compares each service against its own seven-day baseline. When a new anomaly appears, the system can send an SMS alert to an on-call number. The design uses one Stateful Actor per AI Gateway token group, a SQL ledger keyed by date and service to prevent duplicate rows, and a demo mode for testing without real traffic or alerts.

0
ProgrammingDEV Community ·

Tracing Claude Code sessions with OpenTelemetry to see what happens between prompts

The AGNT5 team, which builds a platform for running AI agents and workflows, used Claude Code daily but could not see why some sessions were slow or produced unexpected results. They enabled Claude Code's OpenTelemetry tracing, which records each prompt, model call, and tool call. The traces revealed Claude repeatedly checking package versions online from the shell, which the team fixed by adding one line telling Claude to use the versions in the skill file. The article explains how to run Jaeger locally to store and view the traces, and how to configure Claude Code to export them. It also describes the span structure and attributes that can be used to answer questions about a session.

0
TechnologyThe Verge ·

Whoop launches Humans, a social network for its wearable users

Whoop has launched a social network called Whoop Humans, starting Thursday, that lets members of its wearable devices share their data. Users can make their metrics, activities, and achievements visible to other Whoop wearers. The app also supports Story-style "Moments" with photos and captions, along with comments and reactions on other members' posts. Whoop markets the platform as "entirely human," contrasting it with rival networks it describes as full of AI, bots, and manufactured content. CEO Will Ahmed calls it the most verifiably human network ever launched, claiming every account belongs to a real, verified person.

0
ProgrammingDEV Community ·

Four Publishing Zones Help Engineers Share Work Without Leaking Proprietary IP

A developer building an automated multi-agent system chose publication as a primary defense for intellectual property, reasoning that published write-ups become prior art. While drafting a piece on how the system routes decisions, they realized the planned level of detail would reveal proprietary weighting logic, which would function as a manual rather than prior art. Unable to resolve the tension with a binary publish-or-hold rule, they rewrote the section repeatedly and found that the work stalled the wider publishing pipeline. They then adopted a four-zone classification scheme that sorts content by sensitivity, with a practical test asking whether a draft describes what a system does or how it does it. The approach borrows from tiered sensitivity models common in information governance and compliance.

0
ProgrammingDEV Community ·

Atlassian flags critical Apache Axis RCE in Confluence Data Center's remote API

Atlassian published advisory CVE-2026-90436 on November 9, 2026, describing a remote code execution flaw in Apache Axis, a third-party component behind Confluence Data Center's XML-RPC and SOAP APIs. The issue applies only when the "Remote API (XML-RPC & SOAP)" setting is enabled, though older installations often keep it on for scripts and integrations that outlive their original purpose. Atlassian rates it critical with a CVSS 4.0 score of 9.3, affecting Data Center versions 1.x through 9.x, while Confluence 10.x and later and Atlassian Cloud sites are not affected. The vendor recommends upgrading to 9.2.28 or a later fixed release and disabling the remote API as an interim containment step, verified by a 403 response from the Axis service endpoint. Because Atlassian cannot confirm whether any instance has been compromised, administrators are advised to review proxy logs for SOAP and XML-RPC requests and recent account and configuration changes.

0
WorldBBC World ·

Hegseth's Veterans Day group reprimanded at Arlington: the cemetery's conduct rules explained

A group linked to Defence Secretary Hegseth was reprimanded during a Veterans Day visit to Arlington National Cemetery. BBC correspondent Bernd Debusmann examines the reasons behind the reprimand. The piece focuses on the strict rules of conduct that govern the cemetery. It also traces the historical traditions that underpin those expectations of decorum. The report offers context on why such standards are applied at a site of national military remembrance.

0
ProgrammingDEV Community ·

Google's Decisions API Matches Jev on Accuracy but Trails on Speed

Google has launched the Decisions API, which runs its new Gemini Decision 1 model to answer fixed questions about an input rather than generating text. The endpoint, released on 11 November 2026, accepts text, images, audio, video, or PDFs and returns answers with confidence scores across yes/no, single-choice, and scored question types. A reviewer tested it against Jev on 200 banking customer messages with 10 labels, finding the two nearly tied on accuracy at 92.5% versus 92.0%. Jev was notably faster, with a median response time of 226 ms compared with 511 ms for Google's model. Pricing is close per 1,000 messages, with Google charging about $0.015 and Jev about $0.016.

0
ProgrammingDEV Community ·

PECL to Shut Down by End of 2027 After Revised Proposal

The PHP community has proposed a shutdown date for PECL, the legacy extension repository being replaced by PIE. James Titcumb's follow-up sets a January 2027 banner, a read-only switch in June 2027, a series of brownouts, and a full shutdown on December 31, 2027. The original draft had proposed running until the end of 2029, but reviewers including Rowan Tommins and Derick Rethans argued that freezing unpatchable packages for that long was risky. The timeline was cut to one year, and Derick agreed with the revised plan. No vote date has been set yet.

0
ProgrammingDEV Community ·

RGAA : les ratios de contraste et règles de couleur exigés par le référentiel

Le RGAA impose un rapport de contraste d'au moins 4,5:1 pour le texte courant et de 3:1 pour les grands textes, les composants d'interface et les éléments graphiques porteurs d'information. Il interdit également de transmettre une information par la couleur seule. Ces exigences forment la thématique 3 du référentiel, qui correspond aux critères WCAG 1.4.3 et 1.4.11, tous deux de niveau AA. Le seuil applicable au texte dépend de sa taille affichée et de sa graisse, et les textes en image sont soumis aux mêmes seuils. Des cas particuliers, comme les composants désactivés ou les logos, sont exemptés, et la correction consiste souvent à doubler la couleur par un texte, un pictogramme ou un motif.

0
ProgrammingDEV Community ·

Staged, Observable Retrieval for Insurance Claims Assistants with Node.js

An insurance claims intake assistant should treat retrieval as a bounded, observable pipeline rather than a single vector search call. The application should define a retrieval contract covering the document unit returned, mandatory metadata filters, index freshness, and citation context, kept behind an adapter so the vector vendor can be swapped. Effective alerting should flag a rising rate of answers lacking citable sources, since that often signals trouble earlier than a generic server error. Each retrieval attempt should emit a trace with a request ID, collection, filter hash, deadline, source identifiers, and an explicit outcome such as ok, empty, stale, or deadline_exceeded, without logging full claim documents. Latency budgets and stage limits should be written into the contract, with the system returning fewer cited results or declining to answer rather than silently widening queries.

← NewerPage 233 of 7334Older →