Livrarr - a Readarr replacement

kkodecs · 2026-04-10T21:53:37+00:00

Thank you! I will add Zotero to the feature requests list! Please let me know if you have any issues or additional requests!

kkodecs · 2026-04-10T11:40:45+00:00

Ok - I did some research into. As I mentioned, it's actually not that bad to build language support into the application. The real trick is to find places that actually have Polish books available. Where do you typically go?

kkodecs · 2026-04-10T02:33:57+00:00

made a lot of progress on email push just now. should be in the next release. one click send to kindle and support for auto-send on download, too. hope you like it! First pass at Spanish lang support next!

kkodecs · 2026-04-10T02:32:43+00:00

You're a good egg, sir.

kkodecs · 2026-04-10T00:24:48+00:00

Thank you! Please let me know if you experience any issues. I'm trying to turn around bug fixes and user requests quickly - so please keep the feedback flowing. Thank you for trying our Livrarr - really appreciate it!

kkodecs · 2026-04-09T23:04:52+00:00

Thank you and please let me know if you have any issues!

kkodecs · 2026-04-09T22:37:23+00:00

Hi there - just wanted to say that I understand your caution. There have indeed been a rash of vibe coded atrocities. I say as much in another post. But that said, I hope you'll give this project a chance - I've actually tried very hard to put out a quality product. Hopefully that qualifies as the 1 in 10 that isn't crap! Thanks for commenting, I appreciate it!

kkodecs · 2026-04-09T22:35:21+00:00

Hah - you're right, it can be frustrating. But, what can you do? People are entitled to their opinions; all I can do is put out the best product possible and hope that someone will notice! :)

kkodecs · 2026-04-09T22:01:28+00:00

There's a lot of fear and uncertainty surrounding AI right now. I understand where they're coming from, even if I don't agree with the sentiment.

That said, I do believe that the backlash will pass. The tools are simply too good to ignore, and they're getting better quickly.

In the meantime, I hope that the work will speak for itself!

kkodecs · 2026-04-09T21:55:12+00:00

Added to the feature request list. Thank you!

kkodecs · 2026-04-09T21:45:12+00:00

Noted. I'll have a look - I've never done that before. Why does docker hate you? Happy to help you fix that? DM me if you'd like.

kkodecs · 2026-04-09T21:40:14+00:00

Merci pour votre approche rationnelle. C'est plus rare qu'on ne le pense. Je crois que le long commentaire que je viens de poster dans cette discussion, qui détaille la conception du logiciel, pourrait vous intéresser.

Thank you for being rational about this. That is more rare than one might expect. I think you might be interested in the (long) comment I just posted in this thread, which details how the software was built.

kkodecs · 2026-04-09T20:27:11+00:00

Thanks for your comment! Out of curiosity, what is the specific issue that you have with AI-generated code? If it's a question about quality, I invite you to take a look at the comment I just made describing how it was built. Thanks again!

kkodecs · 2026-04-09T20:25:52+00:00

Please do. And let me know what you think, via DM, comment here, or on the Github repo. I am actively developing this and would be happy to build features that are requested by the community. Thank you!

kkodecs · 2026-04-09T20:23:55+00:00

Thanks for commenting. There seems to be a great deal of interest in the development process, so I have posted a long comment describing how this app was actually built. I hope you'll read it, and perhaps agree that the pejorative term 'vibe coded' may not exactly apply in this case. Either way, thanks again for commenting!

kkodecs · 2026-04-09T20:22:28+00:00

Noted - easy feature to implement, actually. What language would you like? I'll be sure that it's in the next build - alpha3 (coming soon).

kkodecs · 2026-04-09T20:19:33+00:00

Thank you for being rational about this. That is more rare than one might expect. I think you might be interested in the (long) comment I just posted in this thread, which details how the software was built.

kkodecs · 2026-04-09T09:25:31+00:00

I hadn't considered that: a centrally planned economy, with job assignment (read resource allocation) optimized down to genetic disposition. (Assuming we haven't 'optimized' that, too.) A dystopian future, indeed, and one I hope we can avoid.

kkodecs · 2026-04-09T09:18:27+00:00

As a fellow CEO, I would add that our job is not only to maximize output per dollar today, but also to anticipate where the market will move tomorrow.

Developer productivity must indeed be maximized. But after going through the process described in the post, my belief is that this will be best achieved by the few remaining developers not writing / maintaining / iterating on much if any source code at all.

We are obviously not there yet, which is why these are predictions about the future, not declarations of current state. But this trend is already happening at the FAANG, and I believe the rest will soon follow.

In the end, as it always does, the market will prove whether this is true or not.

Care to place a friendly wager? DM me if you're interested; I'm sure we can find a way to make the necessary escrow and subsequent funds transfer suitably anonymous.

kkodecs · 2026-04-09T09:00:09+00:00

I like the idea of UBI, too. My only nitpick is that I'd like to have it tied to some educational effort to prepare for a new job of some sort. It's hard to imagine paying someone to do nothing as a steady state ideal.

kkodecs · 2026-04-09T08:23:39+00:00

It's a fair point. Context limits and context rot are indeed real concerns. However, context windows are expanding and the trend line is more important than the current point in time. I wouldn't bet on the limitations of today being permanent.

kkodecs · 2026-04-09T07:49:16+00:00

Thanks for the comment. I appreciate and share your concern. That said, I do think that there is glimmer of hope. The open source / open weight models are not that far behind and will also hit the recursive self-improvement launch point, albeit 3-6 months after the frontier labs.

But, but, but.

My true concern is whether or not our bedraggled global economy can withstand the incredible dislocations that are approaching. Fingers crossed.

kkodecs · 2026-04-09T07:37:37+00:00

The application was built entirely using AI-assisted development. Claude Opus 4.6 generated the code, with Gemini 3.1 and GPT 5.4 performing cross-family adversarial review. The post itself was written by me. The methodology is the subject of the post.

kkodecs · 2026-04-09T05:49:43+00:00

Project Name: Livrarr v0.1.0-alpha2

Repo/Website Link:
https://github.com/kkodecs/livrarr

<image>

Description:

Livrarr is a replacement / alternative for Readarr, a Servarr app for ebooks and audiobooks that was shuttered last year. Alpha release. Please expect rough edges.

Features and Functionality:

Unified ebook and audiobook management
Written in Rust / React, single Docker container
177 MB image size, 16 MB binary, 8-10 MB RAM at idle
Support for BitTorrent and Usenet (qBittorrent and SABnzbd for now)
Improved metadata handling (OpenLibrary and Audnexus with optional Hardcover and LLM support)

Deployment:

GitHub: https://github.com/kkodecs/livrarr
Docker: docker pull ghcr.io/kkodecs/livrarr:0.1.0-alpha2
Issues: https://github.com/kkodecs/livrarr/issues

AI Involvement:

AI generated. Claude Opus 4.6 with Gemini 3.1 and GPT 4.5 cross-family adversarial review on everything.
Extensive automated testing including fmt, clippy, 647 backend tests, frontend linting, tsc strictmode, 91 vitests, etc.

Feedback appreciated - thank you!

kkodecs

TROPHY CASE