your project fucking sucks (ficd.sh)

A provocative critique calls out a growing problem in the FOSS world: “project slop” — low‑effort, often dishonest repositories that mimic the trappings of real open‑source projects but lack substance. While LLMs and AI tooling have amplified the volume of such artifacts, the deeper issue is cultural: release‑first, marketing‑heavy projects that seek attention rather than solving real problems. That pollution clogs discovery, buries useful work, distorts what “open source” means, and trains newcomers to copy performative patterns instead of learning stewardship and maintenance practices. The author gives practical signals for maintainers and reviewers: red flags include hype‑first websites and templates, Day‑one calls for contributors, heavy community scaffolding without real activity, AI‑generated READMEs, emoji‑overuse, stack‑bragging before purpose, GitHub‑only “git” tools, and announced projects that lack implementation. Green flags are small scope, post‑fact README, no premature community scaffolding, the author using the project, and documentation‑first sites. The solution urged is cultural gatekeeping — defending norms, honesty, and responsibility in stewardship (not excluding beginners), so that openness retains meaning, maintainability, and trust across the ecosystem.