Find published dossiers by topic, company, product or technology.

Showing 41–60 of 196 dossiers

Meta’s approved U.S. teen settlement makes daily limits and nighttime blocks default on Instagram and Facebook

The settlement has crossed from proposed agreement to approved operating constraint. Meta now says the two-hour limit counts activity across Facebook, Instagram and detected multiple accounts, while teens also gain controls for non-algorithmic feeds and autoplay; most terms are required to remain in place for ten years.

ZCode uploaded local repositories without consent — then Z.ai open-sourced the client after the backlash

The useful lesson is broader than one coding assistant: repository indexing can quietly become a data-export boundary. ZCode’s response improves inspectability going forward, but builders using AI coding tools still need to know exactly which indexing, wiki and memory features send source code or Git metadata off-device.

GitSpawn shows how a repository’s own Git config can escape AI coding-agent safety boundaries

The useful lesson is architectural rather than vendor-specific: coding agents inherit execution paths from ordinary developer tooling. If an agent shells out to Git without sanitising repository-local configuration, a hidden `.git/config` can become a host-level command channel that bypasses the controls users think govern the model.

LinkedIn Ads API adds a 1,000-segment audience cap as Legacy Geo shuts down August 31

Audience-management systems can now fail with `SEGMENT_LIMIT_EXCEEDED`, while old geography identifiers begin returning invalid-field errors after August 31. LinkedIn also opened the Matched Audiences API to applications from qualified developers, increasing the importance of handling these limits correctly.

GitHub rewrote Copilot’s 800,000-line agent runtime in Rust with agents doing most of the coding

The useful part is not the 800,000-line headline. GitHub has published unusually detailed receipts for a production-scale agent-assisted migration: roughly $120,000 of token spend, 14.5 weeks of incremental releases, dozens of regressions, extensive compatibility tests and a workload-specific jump from 7.55 to 120 session lifecycles per second.