I find the AI disclosure rules for this community to be well thought out and reasonable. Please follow them. It doesn’t take very long to put together the compliant tags and disclosure text.
Comment on JustDNS: a self-hosted DNS filter that shows which companies your devices phone home to
Bonderosa@lemmy.world 6 hours agoI’m the developer. The design, architecture and decisions are mine. I use AI as a tool (mostly OpenCode, sometimes Claude) for structure and the occasional code snippet, and most of all for the UI, since design isn’t my strength.
Placid@lemmy.world 4 hours ago
Your commit patterns suggest you use AI for more than you share here. A feature lands, then 15-60 minutes later a fix commit occurs. This is pretty typical when a second agent reviews the work of the first. I run the same pattern myself.
Here are some examples that I see just on Nov 14:
These are backend features (cluster sync, crypto, update worker). Nobody writes that much Rust by hand that fast.
Tons of comments like an AI would write. You’re certainly using AI to write tests, too.
It’s okay to use AI for hobby projects, but when you’re offering a product to the public, the public deserves to know the products provenance.
Bonderosa@lemmy.world 4 hours ago
Like I mentioned in the post, I do use AI to assist with testing, comments, code reviews, and coordinating parts of the project which is pretty standard these days to catch edge cases early. The crazy commit speed, though, is mostly because I build and test everything locally on my private Gitea server first and then push it step bystep to GitHub which makes the timestamps look way faster than they actually were.
To keep things completely transparent going forward I’m going to drop the Gitea middleman and push straight to a dev branch on GitHub so everyone can see the real time progress.
In the next days I will publish on the github the complete AI usage so its more transparent to everybody