HOW THIS ARCHIVE WORKS
Build the record.
Build the case.
This archive documents violence against protesters in Delhi, police conduct, and the response from those in power. It brings together posts and case files that protesters, journalists, civil society, and lawyers can use to pursue accountability.
Public contributions, reviewed publication
Anyone can submit a direct X/Twitter post link. Duplicate tweet IDs are detected. Submissions stay in a private review queue. A reviewer checks scope, attribution, event details, source context and potential duplication before publishing a case or attaching the post to an existing one.
Categorization from tweet text
The app first tries authenticated X post lookup when configured, then public oEmbed. If both fail, a submitter can paste the text. English and Hindi keyword rules suggest conduct categories and show the matching phrases. Named organisations and police mentions are cues, not verified affiliations or proof of involvement. Negation, sarcasm and ambiguous wording require human review.
Sources with different evidentiary weight
Text retrieved through X, public oEmbed text, text read from the visible official browser embed, and a submitter’s pasted copy have distinct provenance labels. A browser embed may show only an excerpt; truncated snapshots are labelled. The first five case files were compiled from reporting and are explicitly editor-categorized. The public post collection also includes links supplied by the archive editor. Each link has an embed and reference page; posts whose text cannot be retrieved remain uncategorized. Links and case files are separate counts. Reposts of one recording do not become independent corroboration.
Live embeds versus preserved evidence
Official X widgets display posts and their media where permitted. Posts may change, become restricted or be deleted. Embeds are not an archive. Text snapshots have collection timestamps and SHA-256 hashes. A hash shows consistency of captured bytes and does not prove authenticity, location, timing or legal admissibility.
Private originals and review history
Reviewers can preserve original files in a private Vercel Blob store when configured. Uploads include source URLs, UTC upload times, collector notes and server-calculated hashes. Review decisions and case revisions create audit entries. Original files and full review notes are not published to anonymous visitors.
Prepare the record for legal review
Each case has a stable ID and URL, a copyable citation, a printable record, and JSON/CSV exports. Counsel should evaluate original media, witness accounts, metadata, chain of custody and any certification requirements. Keep independent backups. This app does not certify evidence or determine guilt.
Protect affected people
Use role descriptions in public summaries. Avoid private addresses, witness contact information, identifying details about children and unredacted medical records. Seek consent and apply an appropriate access plan before collecting sensitive statements.
Methodology reference
OHCHR / Berkeley Protocol on Digital Open Source Investigations ↗
This application uses selected documentation practices. It has not been audited against the complete protocol.