AI Weekly Malaysia

Cloudflare launched Cloudflare Traces in open beta, extending automatic tracing beyond Workers to the whole request path — security rules, transformations, cache decisions, routing, Worker execution, and origin handling appear as spans in one request-level timeline. It ships with a baseline sampling rate plus Trace Rules to override per-matching-traffic, W3C traceparent context propagation, in-dashboard timelines, and OTLP export to any compatible endpoint. Cloudflare says its own teams debug with internal traces that can hit thousands of spans per request across dozens of services, and Workers Tracing (with KV, R2, D1 and Durable Objects instrumentation) was the earlier step in exposing that.

Why: If you already run Cloudflare in front of an origin, you can enable tracing per domain in the dashboard with no code changes, which means cache-hit/miss and rule-evaluation decisions stop being guesswork when you're debugging latency. The Trace Rules override matters for cost and noise: you can keep the baseline sampling low and only capture full traces for the traffic you actually care about, and the OTLP export plus W3C traceparent forwarding means these spans can land in your existing backend instead of forcing you onto Cloudflare-only tooling.

Researchers at Northeastern University, working with Consumer Reports, tested 21 late-model vehicles from 17 automakers (including Cadillac, Chevrolet, Ford, Lucid, Rivian, Tesla and Toyota) plus 30 companion mobile apps. Nineteen of the 21 vehicles sent traffic to at least one third party — including Adobe, ContentSquare, Google, Microsoft, Meta, Snap and Yahoo — and 7 of the 30 apps handed over sensitive data such as VIN, email, phone number and precise location to tracking and advertising companies. Pairing the app to the car roughly doubled the exposure to advertising and tracking, per the peer-reviewed study.

Why: If you ship a mobile app that embeds third-party analytics or ad SDKs, this is a concrete measurement of what 'linking an account' does: the study found app-to-vehicle pairing roughly doubled tracking exposure, and 7 of 30 apps leaked VIN, email, phone and precise location. Check whether your own SDKs collect precise location and device identifiers, and whether logging a user in with a stable ID merges an anonymous device profile into an advertising profile. Note the study covers US-market vehicles and apps, and names no Malaysian automaker, telco or app, so this is a privacy-engineering lesson for local builders, not a local policy or regulatory finding.