Page types

Home, search and profile timelines; individual status pages and their currently loaded replies. Available long-form status content can also be extracted when rendered.

What can be retained

Post text, available author name and handle, status links, dates, reply/repost/like metrics, media URLs and relation context where recognized.

All fields depend on what is present in the current page markup. Media is represented by source URLs, not downloaded image or video files.

A practical capture workflow

  1. Open a specific status for a focused discussion, or use a search/profile timeline for a bounded set of posts.
  2. Browse manually. The timeline runtime can accumulate seen items across DOM changes, up to 500 per page on a best-effort basis.
  3. Check preview counts and the focused post. Export Markdown for reading or JSON for retained fields.

Read the limits with the file

This is not an account archive or a complete timeline download. Items missed before extraction, unloaded replies and virtualized content may be absent. X markup is especially changeable. Video URLs may be temporary or point to a poster rather than a downloadable movie.

Exports reflect loaded page content. The ordinary exporter does not scroll, paginate, expand replies, crawl links or fetch hidden data. Check the preview and extraction warnings before relying on a file.

Site redesigns can change extraction quality. Preview output and extraction warnings are more useful than assuming every live route has passed current manual QA.