0megion
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.
Bookhoarder: Open-Source, Self-Hosted ePub Library on Object Storage
AI and Infrastructure Engineering
I built a service to make custom rate limiting less painful
I built a service to make custom rate limiting less painful
Every time I’ve worked on an API, I ran into the same headache: rate limiting.The built-in stuff was either way too rigid (limit everything the same), too hacky, or it fell over under load. What I actually needed was something like:“Limit requests per user ID”“Limit per API key”Or even “limit based on custom fields like subscription plan”I ended up writing my own spaghetti code more than once…...
Testing a new rate-limiting service – feedback welcome
Hey all,I’m building a project called Rately. It’s a rate-limiting service that runs on Cloudflare Workers (so at the edge, close to your clients).The idea is simple: instead of only limiting by IP, you can set rules based on your own data — things like:- URL params (/users/:id/posts → limit per user ID)- Query params (?api_key=123 → limit per API key)- Headers (X-Org-ID, Authorization,...