Editorial: Platforms and institutions are tightening control over how data flows — sometimes by removing conveniences, sometimes by hardening defaults. Today’s picks square those impulses: Google is taking away a long‑used Gmail feature, and the U.S. military is quietly removing ad trackers from service devices.
In Brief
U.S. military disables ad trackers on troops' phones and computers
Why this matters now: The U.S. military's disabling of advertising identifiers removes an easy commercial channel used to sell location signals that could reveal troop movements and base locations.
The U.S. military told Senator Ron Wyden that branches have been turning off operating‑system advertising IDs (the device‑level IDs adtech uses to follow users across apps) on a range of phones and Windows devices, after reports that commercial location datasets were being used to target U.S. forces in the Middle East. According to The Guardian, the Air Force and Special Operations Command have taken steps recently, while the Army says it blocked advertising IDs on Windows for years and on mobile by early 2026.
"These measures so far have not been effective at neutralizing this threat," Senator Ron Wyden warned, according to the reporting.
Turning off advertising IDs reduces a low‑effort source of signal for data brokers, but it's not a complete defense. Disabling a platform advertising ID doesn't stop other fingerprinting or correlation attacks, and it doesn't protect non‑service members — contractors, families, and civilians can still leak location info. Expect more policy pressure on the ad‑data marketplace and renewed interest in hardened device profiles, stricter app vetting, and network‑level protections for operational security.
Corporate America is getting hooked on open‑source A.I.
Why this matters now: Companies are shifting lower‑risk, high‑volume workflows to open models to cut costs, retain control, and run workloads on‑premise, reshaping how enterprises balance vendor risk and capability.
A New York Times feature reports that firms are increasingly experimenting with or adopting open‑source A.I. because it can be cheaper, customizable, and easier to run in‑house or on selected clouds. The article notes cautious stances toward foreign models and a preference for open alternatives that offer clearer control and legal posture; many companies route routine tasks (summaries, search, docs) to open models and save proprietary, frontier models for high‑stakes work. The NYT story highlights that open models are closing gaps rapidly, but enterprises still worry about copyright, supply‑chain provenance, and governance.
The practical takeaway for engineers: expect hybrid stacks where open weights handle bulk tasks behind strict guardrails, while SaaS providers or proprietary models handle specialized, high‑risk outputs. That pattern will keep demand high for model evaluation tooling, secure fine‑tuning pipelines, and explainability layers.
Deep Dive
Google: Gmail removes "Send as" for third‑party addresses (effective January 2027)
Why this matters now: Gmail's removal of the "Send as" feature will force users who send email from non‑Gmail addresses through Gmail's UI to choose new delivery setups months before the January 2027 cutoff.
"Important: Starting January 2027, Gmail will no longer support the 'Send as' feature for third‑party email addresses, such as @yahoo.com or @outlook.com," writes Google on its support page about the change.
Gmail's legacy "Send as" workflow let people host multiple identities or custom domains while using Gmail as the single composer and SMTP relay. Google says the change does not affect Google Workspace aliases or other Gmail addresses you own — meaning native Gmail and Workspace‑managed addresses should keep working — but that leaves a large group of users who used Gmail as a single pane to manage Yahoo, Outlook, and external custom domains in the lurch.
The consequences are practical and curatorial. Users and small businesses relying on Gmail for SMTP relaying have clear options: migrate domains to a dedicated email host (Fastmail, Proton, Runbox, etc.), move to Google Workspace so your custom addresses become Workspace‑managed aliases, or treat Gmail as a collection point (forwarding inbound mail) and use a separate mail client/SMTP provider to send. Each path has tradeoffs: moving DNS and MX records and setting up SPF/DKIM/DMARC correctly will protect deliverability but requires time and some DNS comfort; Workspace centralizes everything but is a paid move; and running separate clients fragments your workflow.
For engineers and administrators handling domain migrations, focus on these concrete steps now:
- Inventory: list every domain and address that currently uses Gmail's "Send as".
- Decide hosting: choose between an independent mail host, Workspace, or separate SMTP provider.
- DNS and auth: update MX records and publish SPF/DKIM/DMARC records for new senders before cutover.
- Test deliverability: use test accounts and monitoring to catch soft‑fails and spam folder issues.
- Client config: update mobile and desktop clients to authenticate using the new SMTP settings or the separate account.
A few subtler points matter for deliverability and user experience. If you switch SMTP providers, make sure the provider's IP reputation is known and include the sending domain in the provider's warm‑up plan if you're sending at scale. If you move to forwarding‑only patterns (Gmail as a PO box), be careful: many providers will mark forwarded mail differently unless you preserve authentication via SRS or similar. The January 2027 timeline gives roughly a year; treat it like a project with discovery, DNS changes, phased cutover, and a rollback plan.
Bottom line: this change nudges people away from the convenience of a single Gmail UI for many third‑party senders and toward either paid consolidation (Workspace) or more explicit ownership of mail infrastructure. If you manage domains or advise small businesses, start an inventory this week and schedule DNS/authentication work before the holidays.
Key takeaway: Gmail's policy is a deadline, not a mystery — use the next months to choose a hosting path, fix DNS auth, and test deliverability so users don't wake up in January 2027 with broken outbound identities.
Closing Thought
Policy and product changes are reshaping convenience into control: organizations are removing leaky identifiers and vendors are pruning cross‑provider shortcuts. For engineers and admins that generally means more setup work but clearer ownership and fewer accidental privacy or deliverability failures. Plan now — inventories, DNS checks, and a short migration sprint will save headaches later.