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

Showing 261–280 of 319 dossiers

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.

Amazon joins YouTube Shopping so creators can tag products instead of relying on description links

The integration brings Amazon’s catalog into YouTube’s native shopping layer. It reduces the gap between product recommendation and purchase compared with description links, but access currently requires both YouTube and Amazon affiliate eligibility and is still limited to a select group of creators.

Cloudflare Containers exposed previous tenants’ disk data through unzeroed blocks

This was not a Firecracker escape or access to a live victim disk. It was a storage-isolation failure underneath the sandbox: researchers recovered foreign directory structures, database pages and complete SQLite databases from reused blocks, and Cloudflare had to fix allocation plus retire existing disks and cached snapshots.

Google Ads starts showing how many conversions your first-party data recovered

The shift is broader than another Ads dashboard metric. Google is connecting first-party data pipelines, conversion-recovery estimates, open-source marketing-mix modeling and causal geo experiments into one measurement stack — useful, but still heavily dependent on Google’s own modeling and internal benchmark claims.

Railway makes MySQL automatic failover generally available with Group Replication and HAProxy

Railway’s managed MySQL path can now gain automatic failover without rebuilding the database elsewhere. The trade-off is real operational complexity: conversion briefly drops connections, hard-coded URLs need manual repair, replicas are for failover rather than read scaling, and each extra database/proxy node consumes billable resources.