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

Showing 21–40 of 299 dossiers

Android Bench 2.0 shows frontier coding agents still fail most multi-day Android tasks

Android Bench 2.0 moves coding-agent evaluation away from small repository fixes toward dependency upgrades, app builds, migrations and other jobs that can take a human engineer days. The results expose a much larger reliability gap than short-task benchmarks—and show that the agent harness can materially change cost and outcome.

X has replaced Creator Revenue Sharing with Original Content Rewards — and U.S. payouts now require X Money

X’s replacement creator program is now live enough to expose a new dependency: U.S. creators must route Original Content Rewards payouts through X Money, and one X Money account can connect to only one X account. Eligibility and qualified-impression rules remain unchanged.

Cloudflare Workers replaces 3MB and 10MB compressed bundle caps with one 64MiB uncompressed limit

The change makes heavier frameworks and dependency trees deployable to Workers without plan-specific compressed-size ceilings, but it also changes what builders need to measure: the operative limit is now uncompressed Total Upload rather than the gzip number they may have optimized around.

Zipchat’s rebuild shows how platform risk reshaped its AI SaaS economics

Zipchat is useful as an operating case study, not a comeback story. Founder-reported figures show how a prior platform dependency failure influenced a new AI SaaS model built around reply-based pricing, channel diversification, revenue-based financing and tighter hiring discipline.

Chrome Web Store now defaults publishers to two extension slots and is retiring Featured badges

Chrome extension publishers now face individualized publication caps, with two slots as the default for new or low-history accounts. Existing extensions remain published, increases can be requested, and Google is also retiring the Featured badge while making recent reviews more important to ratings.

GitHub’s OAuth apps get short-lived tokens, multiple callbacks — and a wildcard setting worth auditing

GitHub OAuth apps can now use eight-hour access tokens with rotating refresh tokens, register up to 10 callback URLs, and explicitly control wildcard callback matching. New apps default to expiring tokens, while existing single-callback apps should review a legacy wildcard setting GitHub has now made visible.