A Bluesky Writer Just Said No to AI Research Tools and 220 People Liked It Immediately

A writer on Bluesky posted something unglamorous this week and watched it get 220 likes: a plain statement that she has never used AI for any part of her writing — not the drafting, not the research, not even following up on Google's AI-generated summaries — and that she doesn't expect that to change. She offered two explanations. One was generational: she's in her forties and set in her ways. The other was philosophical: she hates the whole thing on a conceptual level. No caveats, no acknowledgment that others might reasonably disagree, no hedging about specific use cases. Just refusal, stated plainly.

What makes this worth paying attention to isn't the number — 220 likes is a Bluesky mid-range, not a viral event — it's who liked it and why the post generated the replies it did. This isn't someone describing burnout or algorithmic fatigue. It's someone articulating a position: that the objection to AI writing tools isn't primarily about output quality or job security, but conceptual. The tools are wrong in some way she finds difficult to fully explain to people who don't already feel it. That framing — "I hate the whole thing on a conceptual level" — maps almost exactly onto what creative workers have been trying to say in a vocabulary that keeps getting hijacked by adjacent arguments about copyright and compensation. The feeling comes first. The arguments come after.

The timing matters because Bluesky's AI and science conversation this week was simultaneously flooded with institutional optimism — news sources running positive coverage of AI research tools, a post about ONEST heading to the UN's Science, Technology and Innovation Forum to cover how governments are approaching AI, another about a paleontology machine learning model that was "over 90% accurate" at doing something the museum's press release didn't bother to specify. Against that backdrop of vague institutional enthusiasm, the writer's post functioned as a kind of ground truth: here is what a person who thinks carefully about language actually feels about these tools when no one is asking her to be diplomatic about it. The contrast with the Harvard professor who caught Claude fabricating research results and then handed it 100% of his work anyway is almost too neat — one person encountering AI's failures and doubling down, another encountering the same conceptual unease and opting out entirely.

The governance post that landed second in engagement this week — noting that Trump's new Council of Advisors on Science and Technology hands tech billionaires authority to write their own rules, as covered in depth when the council was announced — suggests the two posts are related in ways neither author stated explicitly. The writer who refuses AI on conceptual grounds and the critic who sees regulatory capture as the structural condition of AI development are responding to the same thing: a sense that the people building and deploying these tools have already decided what they're for, and that the rest of us are being handed the results. The refusal is not irrational. It's a reasonable response to not being asked.