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

Showing 221–240 of 311 dossiers

Cloudflare makes Python Workers GA — with Hyperdrive and first-class platform bindings

The Hyperdrive integration was the practical database unlock; the larger September 21 change is that Python Workers themselves are now GA. Cloudflare is explicitly positioning Python as a production language on Workers, with native platform bindings and framework support rather than an experimental compatibility layer.

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.

Reddit opens Max campaign creation to third-party Ads API clients

The change makes Reddit's more automated campaign type usable by agencies, ad-tech platforms and internal campaign systems instead of only through first-party buying surfaces. It expands automation reach, but third-party builders inherit Max's creative and optimization assumptions rather than gaining a new manual campaign type.

Reddit’s tracked share of ChatGPT Search citations fell 86% in mid-August

A third-party GEO dataset recorded an 86.4% relative collapse in Reddit’s visible ChatGPT Search citation share while Google AI citation changes were much smaller. The result is a useful warning against building an AI-discovery strategy around one source platform, not proof of an OpenAI penalty or Reddit removal.

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.