The PHP security team is giving advance notice: Upcoming security release Wed, Oct 21st 2026, 14:00UTC, two critical vulnerabilities, both rated CVSSv4 9.2. PHP users are encouraged to prepare to update. Earlier release if details become public or active exploit evidence.

Today we're repositioning Zernio. Agents won't just build the product. They'll run how it reaches customers. That's not a theory but it's already happening. We started with social integrations. Now it's ads, WhatsApp, messaging, and calls. Same API. So we're calling it what it is: marketing infrastructure for products and agents.

BREAKING: Today, we witnessed the future of marketing. Introducing Citation Outreach A profitable company can add +$3M/month by ranking in ChatGPT and Claude. 12 months ago nobody believed AI search could drive this much revenue. This is absolutely insane.

Lately, I’ve been seeing an alarming rise in clients receiving 30+ page "AI Slop" audits generated in seconds with zero critical thinking. These reports look visually impressive at a distance. They’re full of scary red exclamation marks, polished pie charts, and "URGENT" warnings. But when you actually open them up, the claims are laughably out of touch: 🚨 "Missing llms.txt file: CRITICAL SEO ISSUE." 🚨 "Missed blocked directory in robots.txt: HIGH RISK." 🚨 "Missing ALT tag on an icon file: CRITICAL ACTION REQUIRED." Let’s be honest about what’s happening here: 1. Minor noise is being sold as major strategy. An unoptimized alt tag on a decorative footer graphic isn’t killing your rankings. A missing llms.txt file isn't wiping you off Google. Turning low-impact, micro-level best practices into "critical site failures" is just a trick to create fake urgency. 2. Quantity is replacing quality. Clients are being handed 30 pages of generic, auto-generated bullet points instead of 2 pages of actual strategic insight. If an audit doesn't tie its findings directly to revenue, search intent, site architecture, or core technical blockers, it’s not an audit it’s an export script. 3. AI is being used as a substitute for expertise, not a tool. AI is incredible for efficiency, but using it to pump out generic audit templates without human validation destroys trust in the whole industry. If your audit reads like it was generated by a bot that has never looked at a search engine result page, throw it away. What’s the most absurd "Critical SEO Flag" you’ve seen in an automated audit recently?

Excited to share @profound has raised a $180M Series D, co-led by @sequoia and @kleinerperkins. Winning in AI Search requires an inhuman amount of work. That is why we are building the AI platform for marketers, underpinned by two things: 1/ Your AI Marketer, a marketing expert that proactively investigates your data, identifies opportunities, and then does the work while you stay in the loop. 2/ Context Manager, a living synthesis of your meetings, email threads, and brand data powering this new teammate. As your brand evolves, so does your AI Marketer. AI labs are pushing the frontier in fields like engineering, law, and finance. But marketing, one of the economy's most complex and consequential applications, has received far less attention. That’s why we’re expanding our applied AI research team. We’re bringing together research scientists, engineers, and IOI medalists to advance AI for marketing. Their focus: post-training models for marketing workflows, and building the world's first AI benchmark for real-world tasks in the field.

i am once again telling you that the reason this happens is because the agent is spamming api calls for reads and from this is violating facebook ads api TOS and how to solve for this is pull data through data pipeline and put into a data warehouse and reads only happen from warehouse and the api is only used for writes and by doing this you won’t violate fb tos and your agent wonts do 1000x api calls a second for reads