{"slug": "i-built-something-good-with-ai-now-some-developer-communities-don-t-want-to-see", "title": "I Built Something Good With AI. Now Some Developer Communities Don't Want to See It.", "summary": "A developer's open-source project Open Vectorizer, a Rust-based raster-to-SVG engine, was rejected from r/rust and Show HN due to policies restricting AI-generated content, despite the developer's assertion that AI assistance does not equate to low effort. The developer argues that blanket bans on AI-assisted work miss the distinction between thoughtful use and low-quality output.", "body_md": "I recently tried to share an open-source project I've been working on called **Open Vectorizer**.\n\nIt's a raster-to-SVG vectorization engine written in Rust. It runs locally, compiles to WebAssembly, has a reproducible benchmark suite, and competes surprisingly well with established tools like Potrace and VTracer.\n\nI wanted people to see it.\n\nMore importantly, I wanted contributors.\n\nThat's where things got weird.\n\nOpen Vectorizer felt like a natural fit for Show HN.\n\nIt's open source. It's technical. There's an interesting algorithm behind it. There are benchmarks people can reproduce and argue about, which I'm told is approximately 73% of Hacker News' renewable energy supply.\n\nExcept I couldn't submit a Show HN.\n\nHacker News is temporarily restricting Show HN submissions from newer users because of a large influx of people unfamiliar with the community.\n\nFair enough.\n\nAnnoying, but understandable.\n\nSo I tried Reddit.\n\nOpen Vectorizer is written in Rust, so r/rust seemed like an even more obvious place to share it.\n\nThe post was automatically removed.\n\nThe subreddit now requires project submissions to certify that they do not contain **significant AI-generated content**.\n\nAnd that's something I can't honestly certify.\n\nOpen Vectorizer has been developed with substantial AI assistance.\n\nSo I didn't repost it.\n\nSurely an MIT-licensed project actively looking for contributors belongs in an open-source community.\n\nTheir rules include:\n\nAll AI-generated content is low-effort and ban worthy.\n\nAt this point I had to appreciate the situation.\n\nI had an open-source project.\n\nI wanted humans to contribute to it.\n\nAnd some of the communities containing exactly those humans didn't want me to tell them about it because machines had helped write it.\n\nI actually understand why these rules exist.\n\nAI has made it incredibly cheap to produce software-shaped objects.\n\nYou can ask an agent to build a database, publish 20,000 lines to GitHub an hour later, write a triumphant launch post and have absolutely no idea whether the thing works.\n\nDeveloper communities are being flooded with this stuff.\n\nThat's a real problem.\n\nBut I think we're using the wrong filter.\n\n**\"Was AI used to write this?\" is increasingly becoming a poor proxy for \"Is this low-effort garbage?\"**\n\nThose are not the same question.\n\nImagine five developers.\n\nDeveloper A writes everything manually but uses IDE autocomplete.\n\nDeveloper B uses GitHub Copilot for completions.\n\nDeveloper C asks an agent to implement individual functions from detailed specifications.\n\nDeveloper D designs the architecture, writes tests, evaluates results and delegates much of the implementation to coding agents.\n\nDeveloper E types:\n\nmake me a vectorizer\n\nThey publish whatever comes back.\n\nWhich projects are AI-generated?\n\nThere's an obvious difference between D and E.\n\nBut drawing the line based on how many characters were physically typed by a human doesn't capture that difference particularly well.\n\nAnd that distinction is only going to become harder to make.\n\nThe first version of Open Vectorizer wasn't good enough.\n\nIt followed a relatively conventional vectorization pipeline: find pixel boundaries, simplify them and fit curves.\n\nThe results weren't terrible.\n\nThey also weren't good.\n\nCircles weren't quite circular. Sharp geometry got damaged. Small raster imperfections became vector imperfections.\n\nEventually I stopped working on it.\n\nLater, I revisited the problem with AI assistance.\n\nWe investigated whether machine learning was the answer. We discussed training a small vision model on synthetic SVG-to-PNG data.\n\nIt probably could have worked.\n\nI decided against it.\n\nInstead, the underlying deterministic algorithm was redesigned.\n\nThe important realization was that anti-aliased pixels aren't simply noise to discard. They contain information about how much of the original geometry covered each pixel.\n\nOpen Vectorizer now uses that information to reconstruct boundaries at sub-pixel precision. It detects corners and geometric primitives, generates candidate representations, rasterizes those candidates back into pixels and measures how accurately they reproduce the source.\n\nThat's how it can take a rasterized circle and produce an actual SVG circle instead of a vaguely circular collection of Bézier points.\n\nAI helped develop that system.\n\nThe vectorizer itself doesn't use AI.\n\nSo is Open Vectorizer AI-generated software?\n\nApparently, yes.\n\nBut that description tells you remarkably little about its quality.\n\nThis happened while preparing a visual comparison for the project.\n\nThe benchmark compares Open Vectorizer against Potrace and VTracer. One metric is the number of vector nodes required to represent the result.\n\nWhile regenerating the comparison, the coding agent discovered that our node-counting implementation was wrong.\n\nDifferent SVG generators close paths differently.\n\nOur benchmark accidentally gave Open Vectorizer one fewer node than it deserved on closed paths while charging Potrace an extra node.\n\nThat's quite an inconvenient bug when you're trying to demonstrate that your software produces simpler geometry.\n\nSo we fixed it.\n\nWe regenerated the tables.\n\nOpen Vectorizer's numbers got worse.\n\nVTracer went from beating it on node count in 2 of 17 cases to beating it in 5.\n\nWe documented why several of those cases occur and added the underlying inefficiency to the project's TODO list.\n\nThe accuracy results, incidentally, still reproduced exactly.\n\nThat's the development process I want from software, regardless of whether the person finding the bug contains carbon.\n\nMaybe the questions we should be asking about AI-assisted open-source projects are different.\n\nInstead of:\n\nDid AI write significant portions of this?\n\nAsk:\n\nThose questions tell me considerably more about whether I want to use or contribute to a project.\n\nAnd they work equally well for human-written software.\n\nHumans, inconveniently, have been producing terrible code since decades before ChatGPT arrived.\n\nThis isn't an argument that AI-generated code is automatically good.\n\nQuite the opposite.\n\nIf I use a coding agent and it introduces a vulnerability, that's my problem.\n\nIf it produces an algorithm I don't understand, I shouldn't ship it.\n\nIf it invents benchmark results, I am responsible for publishing false information.\n\nUsing AI shouldn't reduce the standard.\n\n**It should increase the burden on the maintainer to demonstrate that the result actually works.**\n\nThat's why reproducibility matters.\n\nThat's why tests matter.\n\nThat's why admitting where your competitor beats you matters.\n\n\"I used AI\" isn't a defense against bad engineering.\n\nBut neither should it automatically invalidate good engineering.\n\nThe strangest part of this experience is that I specifically want Open Vectorizer to become **less dependent on me and my coding agents**.\n\nI want someone who knows computational geometry to look at the curve fitting and tell me it's stupid.\n\nI want a Rust developer to make the coverage decomposition faster.\n\nI want someone who understands SVG internals better than I do to improve stroke reconstruction.\n\nI want someone to submit an algorithm I hadn't considered.\n\nIn other words:\n\n**I want human contributors.**\n\nBut to find them, I need to be able to show humans the project.\n\nRejecting AI-assisted projects categorically creates a strange loop where projects developed by individuals with AI assistance have fewer opportunities to evolve into genuinely collaborative open-source projects.\n\nThat seems counterproductive.\n\nI don't think developer communities should simply throw their doors open to unlimited AI-generated project spam.\n\nNobody wants that.\n\nModeration is necessary.\n\nBut perhaps the distinction shouldn't be:\n\n**Human-generated vs AI-generated.**\n\nMaybe it should increasingly be:\n\n**Maintained engineering vs generated slop.**\n\nDid somebody actually make decisions?\n\nDid they evaluate the output?\n\nDid they understand it?\n\nDid they test it?\n\nWill they maintain it?\n\nCan they defend its claims?\n\nAre they accountable for what they published?\n\nThose are harder questions to moderate.\n\nUnfortunately, they're also the questions that matter.\n\nBecause AI-assisted development isn't going away.\n\nAnd as the tools improve, determining whether a particular function was typed by a human, generated by Copilot, implemented by Claude from a specification, or refactored by an autonomous agent will become increasingly meaningless.\n\nThe software still has to work.\n\nSomeone still has to be responsible for it.\n\nAnd if it does something interesting, I'd still like to be allowed to tell other developers about it.", "url": "https://wpnews.pro/news/i-built-something-good-with-ai-now-some-developer-communities-don-t-want-to-see", "canonical_source": "https://dev.to/madsendev/i-built-something-good-with-ai-now-some-developer-communities-dont-want-to-see-it-20mo", "published_at": "2026-07-26 20:53:41+00:00", "updated_at": "2026-07-26 21:29:38.809142+00:00", "lang": "en", "topics": ["developer-tools", "ai-ethics"], "entities": ["Open Vectorizer", "Hacker News", "Reddit", "r/rust", "Potrace", "VTracer"], "alternates": {"html": "https://wpnews.pro/news/i-built-something-good-with-ai-now-some-developer-communities-don-t-want-to-see", "markdown": "https://wpnews.pro/news/i-built-something-good-with-ai-now-some-developer-communities-don-t-want-to-see.md", "text": "https://wpnews.pro/news/i-built-something-good-with-ai-now-some-developer-communities-don-t-want-to-see.txt", "jsonld": "https://wpnews.pro/news/i-built-something-good-with-ai-now-some-developer-communities-don-t-want-to-see.jsonld"}}