Lobsters drops its vibecoding tag as the AI slop fight shifts to spam
The programming community retires an overloaded AI tag, creates ai-tooling and directs complaints about content without meaningful human authorship to its spam flag.
Lobsters has retired its vibecoding tag, but the argument over AI-generated submissions is still going. In a new moderator announcement, the computing discussion community said the tag remains on old stories but can no longer be applied to new ones. Its replacement, ai-tooling, focuses on the design, user experience and development of AI-powered tools.
The practical split is between what a submission discusses and whether it belongs on the site. The live guidelines now define spam to include content created without meaningful human authorship, alongside content designed to promote a commercial service. A moderator’s reply directs complaints about low-effort AI-generated content to that flag.
One tag was doing too many jobs
Moderator 355E3B said vibecoding had accumulated six conflicting uses: a technical topic, a marker for partly AI-related content, a label for AI output, a disclosure of AI authorship, a substitute for spam reporting and a way to shame people who use the tools. The moderator attributed increasing moderation work to the tag and surrounding discussions.
The announcement says some discussion of AI tooling remains relevant to Lobsters. The new tag is already visible on its own public page. This is a change to categorization and moderation guidance, rather than an announcement that every use of AI is prohibited.
That distinction matters because tags also power readers’ filters and subscriptions. A label for building AI tools does not necessarily identify every article written with AI assistance, or every post that mentions an AI product. Retiring a broad label therefore changes what a reader can reliably filter with it.
Members disagree about the replacement
In the English discussion, user apropos asks for a separate “Slop” flag and argues that moderation is failing to recognize generated blog posts. That is a participant’s assessment, not verified evidence of how much such content appears on the site.
The moderator responds that the spam definition was updated and says the old tag’s “tag of shame” behavior was causing moderation problems. Other replies disagree over whether shaming discourages unwanted content or makes discussion toxic. The new tag does not settle that disagreement; it moves the quality judgment into the moderation process.
The same announcement also describes a restriction on submitting code repositories directly, explicitly calling it pending an upcoming deployment. We have not verified that restriction as an active technical block. It should be distinguished from the visible new tag and the published spam rule.
For developers sharing AI workflows, the immediate message is concrete: explain the tool and why it is useful, while expecting authorship and submission quality to face separate scrutiny. For readers seeking a universal AI-content filter, ai-tooling has a narrower purpose.
