329
Audio & Video Production327
Automation & Workflow221
Software Development246
Marketing & Growth202
AI Infrastructure & MLOps150
Writing & Content Creation199
Data & Analytics131
Customer Support128
Design & Creative152
Sales & Outreach120
Operations & Admin97
Photography & Imaging141
Voice & Speech129
Education & Learning119
After a Bluesky outage, many users blamed “vibe coding” with AI tools, even though Bluesky said the issue came from an upstream provider.
In short: A brief Bluesky outage led many users to blame AI-assisted “vibe coding,” even though Bluesky said the issue came from an outside provider.
Bluesky, a social network, had intermittent service disruptions on Monday. Bluesky said the problems were caused by an “upstream service provider,” meaning a company Bluesky relies on, like a utility provider that helps keep the lights on.
Even so, many Bluesky users quickly pointed fingers at the Bluesky team and accused them of “vibe coding.” That phrase is commonly used to mean relying too much on AI to write software code, sometimes without fully understanding it (like copying a recipe you cannot read and hoping dinner turns out).
The anger did not come out of nowhere. In recent weeks, Bluesky leaders have publicly talked about using AI coding tools. Founder Jay Graber said engineers and some non-engineers use Claude Code, which is an AI tool that helps write code. Technical advisor Jeromy Johnson said Claude wrote about 99 percent of his code recently, and CTO Paul Frazee also encouraged using AI tools.
Bluesky also announced a side project called Attie, which lets people create custom feeds by chatting with a bot. Some users worried this signaled more AI inside Bluesky, even though Graber said the goal was to give people more control, not to generate posts.
As more companies admit they use AI to help build software, “AI did it” may become the default blame when something breaks, even without proof. The bigger question is whether companies can explain, in plain terms, how they check AI-written code and how they prevent mistakes.
Source: Arstechnica