The repo owner has taken some very minor steps to not reveal their LLM usage, but it appears the software is being developed (at least in part) using that tool:
https://github.com/SoFriendly/mayberry-branch/blob/80a625bdece2efb72c514b4a5f8bbf0bf21920cc/internal/config/config.go#L25
https://github.com/SoFriendly/mayberry-branch/blob/80a625bdece2efb72c514b4a5f8bbf0bf21920cc/.gitignore#L11I normally wouldn’t post about this, but I feel compelled given the emphasis on security and encryption. I personally wouldn’t use it without understanding the author’s level of competence w.r.t. cryptography and designing secure systems, or without hard forking and maintaining it myself after performing a thorough audit. I don’t think the repo owner is intentionally hiding their LLM usage habits (just look at their other projects), but the vibe coding obviously extends further than the (clearly LLM generated) web page and docs. Just stay safe out there folks.
Additionally, this project probably needs to be tagged as
[]in the title.I would have preferred a regular and modern self hosted opds server, not whatever this is.
How is this not going to get taken down? What am I missing here?
Who knows, when it’s so easy to vibe code slop, and LLMs don’t validate your idea is good before building it?
I mean, the project on its own isn’t piracy, but any useful instance of it can’t be treated like a normal public library.
This is exactly what I’ve been looking for to manage my growing eBook collection!
Definitely going to be trying it out.



