The AI Ping-Pong: When Every Reply Is a ChatGPT Screenshot

A Hacker News thread with 104 points and 48 comments captures a growing developer frustration: being inundated with AI-generated responses that are context-free, often wrong, and forwarded by people who clearly haven't read them.
What's happening
The original poster (theorchid) describes three incidents:
- Found malware on GitHub, asked an AI for advice — got nothing useful. Opened a GitHub discussion. First reply: the exact same text the AI had given them. Called it out, comment deleted. Second reply: same AI response again.
- Asked a business owner a question at work. Got a ChatGPT screenshot back. Replied that it was wrong. A minute later: another ChatGPT screenshot. The owner never read either answer.
- Got a Reddit DM, replied, went back and forth. After a few messages realized it was an AI agent.
Other developers pile on with similar stories. programmertote recounts: “Last week, my boss, Chief Data and Analytics Officer, dumped an AI-generated proposal (~7 pages) on how to structure semantic layer on top of our dbt models. As the Data Engineering lead, I had to read it and found a few glaring issues… Yesterday, one of my coworkers shared another obviously AI-generated 5-page draft of an SOP on how to reintegrate old metrics. I think we will all become AI-output-reviewers eventually.”
jadar wonders if we’ll soon be forced to execute on AI output instead of sharing it: “If you can reason yourself into a working system, you know what you’re talking about. If not, then it’s not worth taking the time to figure it out.”
Practical responses
- jochem9: “Ask them to share their prompt instead. Calls them out on their AI bs and gives a way forward to share what they actually thought.”
- LPisGood: “Why not ask your AI to review their AI slop? That which can be sent without thought can be responded to without thought.”
- sixtyj envisions automated replies: “This text was automatically generated and has not been reviewed before being sent. It’s AI garbage and I refuse to read it. Do it again. And do it better.”
Takeaway for devs
Blindly forwarding AI output erodes trust and creates busywork for reviewers. Setting a norm — share the prompt, reason about the output, or risk being ignored — could slow the AI ping-pong. As one commenter put it: establish a consensus that distributing unread AI slop is not acceptable.
📖 Read the full source: HN AI Agents
👀 See Also

Claude-Code v2.1.94 adds Mantle support, fixes critical bugs
Claude-Code v2.1.94 introduces Amazon Bedrock support via Mantle with the CLAUDE_CODE_USE_MANTLE=1 environment variable, changes default effort level to high for most users, and fixes 15+ bugs including rate-limit handling, macOS login issues, and plugin system problems.

OpenAI and Rivals Publish Agent Plugins: One Package Format for AI Agents
OpenAI, Amazon, Microsoft, Cursor, and Vercel shipped Agent Plugins 1.0, an open standard for packaging agent extensions. Build once, run across ChatGPT, Codex, Copilot, Cursor, and more.

Claude Code v2.1.129: Plugin URL flag, force sync output, and 20+ fixes
Adds --plugin-url flag to load plugin zips from URL, CLAUDE_CODE_FORCE_SYNC_OUTPUT for Emacs eat, and fixes /context token waste, cache TTL downgrade, and OAuth race.

Apple's libibverbs Hides GPUDirect RDMA Symbols; Zero-Copy Metal Buffer RDMA Works on macOS
A developer discovered that Apple's RDMA subsystem accepts Metal GPU buffers for zero-copy network transfers and found hidden ibv_reg_dmabuf_mr symbols suggesting GPUDirect RDMA is possible on macOS without kernel modification.