[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fqcplvw823mq9":3},{"code":4,"message":5,"data":6,"timestamp":33},10000,"success",{"full_name":7,"position":8,"description":9,"language":10,"stars":11,"forks":12,"stars_gained":13,"age_days":14,"hn_threads":15,"one_liner":16,"summary_md":17,"topic":18,"github_topics":21,"license":29,"homepage":30,"updated_at":31,"history":32},"freeok\u002Fso-novel",9,"小说下载｜网文下载 | 网络小说","Java",8752,741,137,1615,[],"Turns serialized web fiction into clean EPUB, TXT or PDF ebooks for offline reading on any device.","## The problem\n\nReading long serialized web novels is painful: content lives across many pages with ads, navigation chrome and inconsistent markup, and there is no official way to get it onto an e-reader. Copy-pasting chapter by chapter into a text file loses formatting and ordering. So Novel crawls the book's index page, pulls each chapter, and assembles the result into a single EPUB, TXT or PDF file that opens in a normal reader like Calibre, Apple Books or a Kindle.\n\n## What's different\n\nThe usual approaches are browser extensions or one-off Python scripts that break as soon as a site changes its HTML. So Novel is a packaged Java application that ships a rule set for supported sites and has three front ends: a TUI, a CLI, and a web UI that runs as a Docker container on a NAS. That built-in web mode is the main thing that separates it from a spare script in a gist — it is meant to be run as an always-on service, not just from a terminal. The trade-off is that it is tied to its rule files; sites it does not yet cover need a rule written, which is a maintenance burden you inherit.\n\n## Who it's for\n\nPeople who read web novels in bulk and want them in a proper ebook library, especially those with a home server or NAS who would run the Docker image and use the web UI. It suits users willing to manage a JVM application and occasionally update rules when a site changes. Anyone expecting a polished, fully managed downloader for arbitrary sites should look elsewhere — the README is thin on how many sites are actually supported, and unsupported sites fall back to manual rule authoring.\n\n## Cost of adoption\n\nYou need a Java 21 runtime (the release bundles one, or Docker handles it) and the download and install commands are in the README. The AGPL-3.0 license matters if you plan to modify and redistribute it, or to run a modified version as a network service. There are legal and site-terms risks in scraping content, and the project places that responsibility on the user via a disclaimer. Maturity is the bigger question: the project is over four years old but the README gives few details on supported sources or update cadence.\n\n## Verdict\n\nThe project is not new — created in 2022 and now with roughly 8.7k stars — and it recently appeared on the Java weekly board with +137 stars, so interest is real but modest rather than a spike. It has stayed off the daily trending board and has no Hacker News discussion, which suggests a steady niche audience rather than broad developer buzz. Treat it as a working utility with a small active community, not an independently verified, actively benchmarked tool. If you need one book in EPUB form, it is worth an afternoon; if you need a dependable service across many sites, evaluate the rule coverage first.",{"slug":19,"name":20},"productivity","Productivity & Utilities",[22,23,24,25,26,27,28],"cli","content-export","document-parser","ebook","novel","offline-reader","tui","AGPL-3.0",null,"2026-10-25T00:36:54Z",[],1792901884]