ManYue Ubooquity feeds: verify page streaming from the comic catalogue

English translation of the Chinese original, translated on 2026-10-27. Original publication dates, attribution, code and version notes are retained.

A Ubooquity browser reader and its catalogue service are different entry points. Start with the comic feed confirmed by its maintainer, then inspect catalogue identity, streaming capability and actual images. Ordinary acquisition links and OPDS-PSE page streams are distinct.

Confirm the comic feed with the maintainer

Record service version, reader-account scope and the intended comic feed. Do not use a specific web-reader page or substitute the ebook feed. Paths and ports depend on deployment, so obtain the correct endpoint from your setup or maintainer and keep it private. Establish that before configuring OPDS.

Use the provided OPDS connection type

Configure the offered OPDS/Ubooquity path and confirm expected comics and folders before bulk actions. Record authentication, document-format and empty-catalogue failures separately. Server rights and current app feature conditions remain independent. A browser login alone does not validate the feed response.

Verify a comic entry and its edition

Choose one known comic and compare title, cover, available page information and a representative scene. Extensions alone do not establish delivery capability. Use the same account and item throughout; broader administrator catalogues are not evidence for a reader’s expected count.

Distinguish acquisition from page streaming

OPDS-PSE supplies information for individual-page requests, while an ordinary feed may expose whole-file acquisition only. A missing-stream result calls for capability/type checks, not repeated password changes. Authorised file acquisition followed by local import is a separate route and identity, not proof that the original entry gained streaming.

Test actual image requests after catalogue access

Inspect early, middle and final images, distinguishing them from login or error pages. Catalogue and cover success are only partial. Compare the same account’s server reading result and report the image stage. Do not relabel HTML as an image or bypass security checks as a routine troubleshooting step.

Check re-entry and position

Exit and reopen the same entry, checking both access and scene. Authentication-session changes and saved position are different issues. Distinguish chapter-start navigation from resume. Keep the archive and catalogue stable and state the tested service version rather than claiming universal historical-version compatibility.

Verify any offline route independently

Verify a supported download offline separately, or retain an authorised file-import alternative where applicable. Browsed pages do not establish a complete local archive. Record the relationship between local and server identities, keeping a verified travel copy until any replacement is understood.

Acceptance and failure layers

Finish with the correct comic feed, verified identity, understood streaming boundary and explainable image/re-entry results. Browser, feed and image routes can differ. Report version, redacted path structure, item type and failure stage without credentials or a supposed universal endpoint.

ManYue OPDS connections: why a catalogue may not support page streaming; ManYue HTTPS and proxy subpaths: what to check after a browser opens.

Checked on October 27, 2026: ManYue public version 2.0.3 requires iOS / iPadOS 15.0 or later. Based on the official App Store description and Apple public version lookup. Reader options depend on the installed version and current context. This article describes a checking workflow without claiming step-by-step physical-device or private-server testing, or treating development features as released capabilities.

For page streaming, also consult the OPDS-PSE project definition, checking the actual deployment and permissions separately.