Find published research by company, product, platform or technology.
Showing 141–160 of 204 dossiers
beehiiv has moved AI crawler policy from a voluntary robots.txt signal to an enforceable publisher control for Max and Enterprise custom-domain sites. Its new dashboard tracks 22 AI and search crawlers, while separate structured-data and llms.txt features target AI discovery rather than access control.
Preferred Sources is now global, appears inside Google’s AI-search experiences, and has an embeddable publisher button. Google says readers are twice as likely to click a source after marking it preferred.
The August 20 tagging overhaul collapses Google’s lightweight tag and GTM into one platform, changing how marketers manage measurement code without requiring existing Google tags to behave differently on-page.
Neon’s beta backend now combines Postgres branches with Node.js Functions and S3-compatible Object Storage that inherit branch semantics. For builders, that makes ephemeral preview/test environments more complete: database state, backend code and object data can move together instead of requiring separate production-adjacent services.
Qwen3.8-27B is now available as open weights on Hugging Face and ModelScope. For builders, the important change is not another benchmark bump: a comparatively compact 27B model now combines native vision, long context, controllable reasoning and OpenAI-compatible serving paths for local or self-hosted coding and agent workloads.
This is separate from LinkedIn’s Ads Legacy Geo cutoff already tracked by BTN. Profile and compliance integrations can fail more quietly: the request may still succeed while a field the application expects simply disappears or becomes null.
A 50M+ subscription cohort gives AI SaaS builders a more useful retention benchmark than conversion anecdotes: high-retention monthly apps renew 57.9% of subscribers at the first opportunity versus 30.2% for low retainers, with the gap narrowing later. The study is observational, not causal.
WebKit’s Safari MCP server turns browser debugging into an agent-callable interface. It runs locally and makes no network calls itself, but captured page data is sent directly to the connected agent, so browser-session trust and model data handling become part of the development security model.
Patreon is no longer only a destination for fans who already know a creator: most creators now have access to a discovery feed and public-post funnel, with vendor-reported membership gains suggesting distribution inside Patreon is becoming a meaningful acquisition channel.
Agent Identity is moving from a standalone credential boundary into a mainstream serverless runtime. Cloud Run can now assign agent identities and register agents/MCP servers automatically, reducing custom discovery and identity plumbing while keeping the runtime integration itself in Preview.
Cloudflare has inverted a long-standing Workers assumption: Node.js compatibility is now on by default for current compatibility dates. That reduces setup friction for many npm packages, but it also means developers need to understand compatibility-date boundaries, partial APIs and explicit opt-out flags.
The newer `critical=false` daemon control changes ECS Managed Instances from an all-daemons-are-instance-critical model to an explicit reliability trade-off: logging, metrics or security agents can fail without forcing application workloads off the host, while ECS still emits health events and action logs.
Quattro’s unified programmable shell is a real architecture change rather than a theme refresh. Omarchy 4.0.2 now hardens package, installer, SSH and input paths, while current user reports of Quickshell crashes and a runaway-memory event illustrate the new central shell’s blast radius.
Copilot code review now moves from advisory assessment toward a governed merge gate. The public preview remains off by default, and GitHub’s current docs let administrators separate AI approval itself from whether that approval counts toward required-review policy.
The interesting part is not another AI scanner. Cloudflare is connecting source-code evidence to what is actually deployed and being attacked at the edge, validating findings outside the model, then preparing both a code patch and, where appropriate, a narrowly scoped WAF mitigation for customer review.
npm v12 disables dependency lifecycle scripts, Git dependencies and remote-URL dependencies by default unless projects explicitly allow them. GitHub has now also expanded npm trusted publishing and made malware scanning a gate before staged packages can be approved.
Tailcat is deliberately smaller than a tailnet: peers exchange a short connection token out of band, then Tailscale’s data-plane code tries direct UDP and falls back to DERP. The trade-off is that the new tool has no stability or service guarantees yet.
The architecture is unchanged—Quack/CONNECT, a stable extension ABI, new storage and parser foundations—but the migration window is now concrete. Builders can test real 2.0 alpha clients before the projected October release.
Cloudflare’s first half-year DDoS report records 935 network-layer attacks above 1 Tbps and a 519% Q1-to-Q2 increase, but says 96.62% of attacks stayed below 500 Mbps and 90.60% ended within 10 minutes. The figures are Cloudflare-network telemetry, not a neutral census of the internet.
Cloudflare now sits on both sides of the policy boundary. Site owners can publish and enforce crawler preferences, while developers using Cloudflare’s own crawl API must declare intended uses and can receive hard failures when a target site disallows them.