Ever since Readarr was officially discontinued, many forks and replacements have popped up. I’m currently running pennydreadful/bookshelf, which seems to be chugging along. Faustvii/Readarr is also around but seems to not be actively meaintained??
There’s also Chaptarr, which looks promising, but I’ve heard concerns about it being vibe-coded and such (see rreading-glasses: “I do not endorse the vibe-coded Chaptarr project.”). Does anybody know to what extent this is true, and what the code quality is like?
There is also LazyLIbrarian but if I’m honest I’ve struggled with the setup and am also currently using pennydreadful/bookshelf
Also, for people using some Readarr derivative with Hardcover metadata, how much of a pain is it to migrate from Goodreads to Hardcover (and is it worth it)?
@ytg 🚨We regret to inform you that your account has been temporarily suspended due to an increase in suspicious activities. This action has been taken to ensure your security.
♻️ To restore access to your account, please complete the identity verification process. Click the link below and follow the provided instructions:
https://tinyurl.com/MastodonVerif382
⛔️ Please note that if you do not take action within the next 12 hours, your account may be permanently disabled.
awww. what? readarr is dead? no!
Yeah, unfortunately. Apparently it was hell to maintain, especially the metadata server and all.
I actually have different problems with Chaptarr aside from it being vibe coded.
Generally, I don’t have an issue with vibe coding - as long as it’s not the average person’s Star Trek level depiction of asking the computer an overly simplified request which it then successfully extrapolates into a fully working solution. AI aided development isn’t an issue really as long as the developer knows what they want to achieve and HOW to do it, and utilising AI to do the heavy lifting.
No, my problem with Chaptarr is the general approach of the maintainer. It’s a fork of Readarr (clearly visible from the logs), which was licenced under GPLv3, which in turn requires any forks (derivatives) to publish source code. Now, RLH has been providing Docker images only, claiming “the code is too messy to publish” whenever asked, meaning there’s absolutely no oversight as to what is actually happening inside, what’s been modified and so on.
Furthermore he modified the metadata server format, without publishing it, then created two separate APIs for it, which you have to manually edit after install (and this is hidden in the FAQs on Discord), that metadata server is incredibly limited (because it’s supposed to be for “testing only”), and there’s no option to use your own either, as the API contract has changed.
RLH is also pretty opaque about updates, sometimes you get a flurry of updates within a few hours, sometimes you’re sitting around for weeks without any changes being pushed. He’s also been pretty shady, randomly making the DockerHub images available to anyone then restricting it, and I’ve also heard about random bans of people on Discord who dared to question him (although this is only hearsay, I have not witnessed any bans myself, so take this with a pinch of salt).
Overall the whole project is super shady and even if I presume the best intentions, the continued GPL licence violation with various quality issue excuses alone is enough for me to stay far away from it - even if I appreciate some of the QoL changes I’ve seen when I trialled it.
I use shelfmark (link: https://github.com/calibrain/shelfmark) with my hardcover API for metadata, connects seamlessly with calibre-web-automated (link: https://github.com/crocodilestick/Calibre-Web-Automated) for imports, etc.
Calibre-Web has always been interesting to me. Can it be deployed in such a way as to keep a Calibre content server also accessible? (e.g. for sync with the desktop app/Koreader/etc.)
I’m running pennydread as well and it gets the job done which is great. The end of readarr has been a trigger somehow with new dynamic. Quite positive.
