0megion

Hi, developer of Bookhoarder here.

I am a big fan of e-readers, specifically Kindle. However, I would like to own my books rather than just having a digital copy on a provider, not knowing if they will allow me to read them in the future.

I started my EPUB collection 9 years ago and have quite an archive. The problem I faced was finding a way to browse them easily and send them to my e-reader. There are many self-hosted options out there, but none of them were modern, easy to use, and backed by object storage that I could point at my S3 bucket where I store my EPUB archive.

That's why I created Bookhoarder to solve this problem: an object-storage-backed EPUB library. Please check it out: https://bookhoarder.dev/, https://github.com/bookhoard/bookhoarder

Of course, I made it open source so that anyone can contribute and improve it the way they want to use the library.

Maybe I should have added this part. As a non-native English speaker, using AI to write RFCs, ADRs, and internal documentation, my own writing style shifted so much to the direction that my writing seems like AI.

If requests are already hitting your servers, it’s too late — you’re burning CPU and bandwidth before rejecting. I built Rately to solve this at the edge: set limits by user, IP, or plan (e.g. free = 1k/day, pro = 1M/month) and return 429s before traffic reaches your infra. Keeps apps simple and protects backend capacity.

Interesting, but still your Rail app needs to apply the rate limit logic working with Redis, maybe your DB will be protected, but you will still receive the traffic through your network, meaning more ingress cost, along with CPU to process all the incoming requests.

It's already too late if requests are hitting your service. What happens when a customer sends x100 traffic all of a sudden, your Rails backend needs to scale or crash to handle the rate limiting.

Correct, pricing would be based on the traffic volume.

That is fair. Maybe Proxy mode would be a way to go in this case? Instead of calling another API, you can pass through your requests, and only a small amount can reach your origin.