Skip to content

Define evidence boundaries inside Reddit megathreads

Explore define evidence boundaries inside Reddit megathreads through public thread context, explicit exclusions and a useful evidence-linked research artifact.

Guides

Which questions within a megathread belong to the research topic?

A megathread can contain hundreds of unrelated mini-conversations under one title. The research unit should be the relevant question branch, not every comment attached to the submission. This is an editorial method rather than a live finding. A Reddit context badge does not guarantee access to every submission, reply branch or historical version.

Example research prompt
Which questions within a megathread belong to the research topic? Choose a public weekly purchase-advice thread about cameras. Include branches stating a travel-photography need; exclude unrelated equipment discussions and requests without an identifiable task. Create a branch-indexed needs brief with exact accepted question counts and source references. Retain exclusions so a reviewer can reproduce why a branch qualified. Preserve branch context, cite originals and report unavailable coverage. Do not contact participants or take native actions.
01 / Guides

Bound the thread selection

Choose a public weekly purchase-advice thread about cameras. Include branches stating a travel-photography need; exclude unrelated equipment discussions and requests without an identifiable task. Record community, original thread references and the intended publication interval before using research. Inspect actual coverage; neither a returned page nor a broad community name establishes a complete discussion population.

02 / Guides

Read the available conversation

Keep each question with its available answers and stated constraints. Distinguish several replies to one request from independent requests by different authors. Preserve source references and the branch context actually returned. A submission, a parent reply and an isolated excerpt carry different evidence; missing text should remain missing rather than being supplied by interpretation.

03 / Guides

Build the source-linked handoff

Create a branch-indexed needs brief with exact accepted question counts and source references. Retain exclusions so a reviewer can reproduce why a branch qualified. Keep quotations, author reports and analytical labels distinct. Report exact accepted counts alongside exclusions, preserve original community and author credit where available, and attach coverage limits to conclusions rather than hiding them in a separate claim.

04 / Guides

Stop at the evidence boundary

If pagination leaves branches incomplete, state the inspected scope. Do not claim to summarize the entire megathread or infer silence in unreturned branches. Stay within the agreed read-only scope. Researching public discussion does not authorize voting, joining, messaging, private-trait inference or posting; unavailable evidence is a limitation, not permission to seek private material.

Keep the boundaries clear.

  • If pagination leaves branches incomplete, state the inspected scope. Do not claim to summarize the entire megathread or infer silence in unreturned branches.
  • Example procedure only: no live findings or representative survey results are claimed. Public comments are not a subscriber or voter list.

Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.

Primary references

Documentation reviewed 2026-11-13. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.

Know what social media shows about you.
Start with a question.

Get started
montage