OP did not make it and canât do a disclosure, its not required.
Natanox@discuss.tchncs.de âš3â© âšweeksâ© ago
If this project is closely based on Calibre it requires the [AIP] prefix.
curbstickle@anarchist.nexus âš3â© âšweeksâ© ago
ohulancutash@feddit.uk âš3â© âšweeksâ© ago
Its a fork of Calibre-Web not Calibre
9point6@lemmy.world âš3â© âšweeksâ© ago
FWIW Claude seems to be involved in 9 commits
The maintainer has made nearly 900 and there are about 50 other contributories
This isnât a vibe coded project
CWA is the example I always point to as to why vibe coded software doesnât make sense for broad use. CWA updates are slow (but detailed) which inspires many folks to âforkâ it with vibe coded apps, but since CWAs last update in Feb, several vibe coded âcompetitorâ projects have risen and fallen.
Iâm starting to say vibe code is write only.
Like they used to say about Perl, indistinguishable from line noise.
Basically unmaintainable without super strict coding conventions, submitters taking personal responsibility, a strong, well thought out overarching architecture, and most importantly, someone with a great knowledge of the project to approve merges. Vibe coded forks to add one or two features have none of that.
This is why GitHub is littered with slop projects that havenât been touched since they were made. This is why an ungodly amount of technical debt is accruing as managers with a hard on for lines of code or âfeaturesâ force devs to unwisely use AI coding tools all the time. There will be a reckoning, and itâs not far off.
Thatâs a great way of putting it. I think in the future it will be helpful for when folks have some personal specific need. But for anything approaching even the simplest infrastructure it just doesnât work.