I read every single day. At home it's on my Kobo running KOReader (yes, I'm that open-source guy), and I love it. The problem: I don't always have the e-reader on me. On the train, at work, waiting somewhere — I just have my phone.
I tried Kobo's own Android app to bridge the gap and... I really didn't like it. Promos everywhere, adding your own books is a pain, the reader itself feels clunky, and the Wi-Fi handling is annoying.
So I built my own thing: Varbook, a small self-hosted EPUB library.
You drop EPUBs into it in one click. From there:
- They're readable on your phone through a simple but well-made PWA. Books are cached locally, so you can read offline; when you're back online your reading position syncs to the server.
- The server exposes everything over OPDS, so any compatible app works (KOReader, Moon+ Reader, etc.).
- I also wrote a KOReader plugin that pushes/pulls your reading position to the server in a single gesture.
My actual daily workflow:
- Evening, at home: I wake up my Kobo in KOReader, tap the top-right corner → Wi-Fi turns on, my current book jumps to the right position, Wi-Fi turns back off to save battery.
- I read.
- Done reading: tap the top-right corner again → Wi-Fi on, my reading time + position sync to the server.
- Next day, at work: I open the PWA on my phone. It drops me exactly where I left off, and syncs my position on every page turn.
- Evening: back to the Kobo, which picks up my position from the phone.
All of this with fully open-source software, no commercial service in the loop, my books staying on my own server.
The trickiest part was cross-device position sync — every reader engine (epub.js in the browser, KOReader's CREngine, Moon+) tracks position differently. Varbook uses a "pivot" format based on EPUB spine items (chapter index + percentage) so your position survives the jump from one device to another without throwing you 30 pages off.
It's open source (MIT), built with Laravel + React, and ships as a single Docker container (SQLite by default, no external DB needed). The entire UI is translated in English, French, and Spanish.
Honest disclaimer: a good chunk of this is vibe-coded. That said, I've been a developer for 20 years, so it's opinionated vibe-coding — I know what I'm looking at. It's been used daily and intensively by about 5 people for the last 3 months, and I keep improving it regularly. It's not bug-free, but I'd call it reasonably stable. I'm being upfront so you know what you're getting into.
There's a free public instance if you just want to try it without installing anything: https://varbook.hophop.be/
- Full write-up on my blog: https://trucs.hophop.be/en/blog/varbook-bibliotheque-epub-self-hosted
- Code: https://github.com/ndieschburg/varbook
- KOReader plugin: https://github.com/ndieschburg/varbook.koplugin
Happy to answer questions or hear what's missing — it scratches my own itch, but I'd love to know if it's useful to anyone else.
"A lot" is doing some Olympic level, Gold medal performance lifting there lol.
Lemmy is loud in its AI hate, nuance be damned. I've seen drivebys on !LocalLLama (notably on a project about AI infinite radio).
Apparantly, everyone is now an expert on ML and AI (I sure hope they didn't use Gboard or Apple to glide type their message or any sort of STT), just like everyone was an expert on epidemiology, politics, trans rights, ethics, pop culture etc 5 mins ago. You don't need to be an expert to have a position but at the same time, empty cans make the most rattle.
What's up with arr stack tho? I've been pulling direct from 1337 of late (and even more recently, just using CloudStream). Are we "no one is gay for molemen" on the arr stack?
I have no qualms with the software itself. In fact, from what I've read, it's pretty amazing as to how it all fits together. Some good software engineering there. However, my problem arises in what most people use the 'arr stack for. I don't police your usage, and I don't preach at those who use the 'arr stack to pirate content, I don't leave castigating comments and down votes. I figure you are all autonomous adults capable of making your own decisions and living with them. I've heard all the pros and all the cons and everything in between, so no need to rehash all of that. Nothing I could possibly post would convince anyone to disband their 'arr stack, so why bother? What would I gain except some faux sense of superiority? I don't know what people get out of slamming others for using AI. What does it do for you? Does it make you feel better to trash someone's project? Let the end user decide if the project is worthy of them running on their server, not a consensus of AI haters.
It all gets down to how you interpret Rule 1: 'Be civil: we’re here to support and learn from one another. Insults won’t be tolerated.' Everybody was all chatty about Rule 3, but Rule 1 seems to be a hit or miss. Like I said, it's 2026 and AI isn't going away. It is probably a good assumption that any project within the last 5 years is going to be using AI in some form or fashion.
Ah, I thought you meant there was some technical issue that I wasn't aware of / it had been superseded by a superior method.
Ethical issues aside, the arr stack is a good gateway drug for self hosting. It's fiddly but probably in a useful way. JF/Radarr/Sonarr/Sabnzdb set up genuinely introduces a variety of branching skills.
Arr leads to self hosting, self hosting leads to home assistant, home assistant leads to ... suffering :)
One of these days I'm going to have to spin up HA and see what it's all about.
Pain. Suffering. Death.
(I'm kidding...or am I?).
I always think of home assistant like that scene in V for Vendetta, where he set up an elaborate circle of dominoes, and everything is working perfectly right up until he gets to the last domino.