Prose reader, a modern reading system engine
Prose is a modern reading system engine designed for developers to create their own reading applications. It supports various formats like EPUB and comic archives, offering a modular architecture for flexibility. The author seeks feedback from developers interested in enhancing the reading experience and improving the SDK.
- ▪Prose is an MIT-licensed reading engine for building reading apps on the web and mobile.
- ▪It supports EPUB and archive formats, allowing developers to create both simple and complex reading applications.
- ▪The architecture includes a plugin mechanism called enhancers, enabling customization of reader capabilities.
2 outlets in our directory ran this story, first to last over 10 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/mbret/prose-reader-a-modern-reading-system-engine-499m |
| Publication time | Sat, 30 May 2026 09:12:56 +0000 |
| Retrieval time | 2026-05-30T09:42:09.036Z |
| Last seen | 2026-05-30T09:42:09.036Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 18wqCo6_X5Yy · 2 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 1088601) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Maxime Posted on May 30 Prose reader, a modern reading system engine #webdev #javascript #books #typescript Hi HN, I’m the author of Prose, an MIT-licensed reading engine / SDK for building reading apps on the web and mobile: https://prose-reader.com/ The project has been around for about 6 years, but I’ve never really promoted it much. I’ve mostly been working on the architecture, compatibility, examples, and developer experience.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).