X Articles

eReader Relay attempts public X Articles only. An X Article has a dedicated Article title and body in the public page. A normal post does not become an Article because it is long or has replies.

What is supported

• A public X status page whose exact status contains X's Article body.
• The Article title supplied by X, rather than the generic browser title.
• The Article body and readable images that can be safely packaged into the EPUB.

What is not supported

• Normal posts and long posts.
• Threads, including a post followed by author replies.
• Profiles, timelines, search results, and bookmarks.
• Private, deleted, login-only, or otherwise unavailable Articles.

The backend verifies the exact status ID. An Article linked in a reply cannot make the original post eligible.

x-article-required

Status: Not attempted

The page is on X, but the exact status is not an X Article. This includes posts, long posts, threads, profiles, and other X pages.

Open the dedicated public X Article status page and try again. eReader Relay will not combine a thread into an EPUB.

x-article-unavailable

Status: Not attempted

The page looks like an X Article URL, but the public Article could not be verified. It may be private, deleted, login-only, restricted, temporarily unavailable, or blocked from public retrieval.

Confirm the URL works in a signed-out private browser window, then retry later.

x-article-invalid

Status: Not attempted

X marked the exact status as an Article, but the returned Article title or readable body was missing or incomplete.

Retry once. If the result is unchanged, report this reason code and the public URL to eReader Relay support so the parser can be investigated.

Privacy and diagnostics

Expected policy refusals are recorded as not attempted, not as application crashes. Telemetry records the reason code and operation outcome without recording the Article body, account token, or private browser data.