eLafdaExplore archive
OPEN SOURCECOMMUNITY GOVERNEDSOURCE BACKEDEARLY ARCHIVE PREVIEW

01 The public memory of Indian internet culture

Internet forgets.
Receipts shouldn’t.

Follow the conversation, inspect the evidence, and preserve what actually happened without confusing popularity for truth.

Browse the cases See how verification works
2 layersdiscussion + record
Every editpublicly traceable
Zero votestreated as proof

02 Case discovery

What’s in the record?

Browse representative case files from the early archive preview. Full editorial records will follow the review workflow.

Showing 4 of 4 preview cases

ELF-2026-0021Developing

Creator economy

Creator collective revenue-share dispute

A public disagreement over campaign terms, payment schedules, and what collaborators say was promised.

Sources
14
Updates
8
Last checked
2h ago
Evidence-linked
ELF-2026-0018Resolved

Open source

Open-source maintainer access dispute

A project handover sparked competing accounts about repository control and contributor attribution.

Sources
23
Updates
12
Last checked
Yesterday
Evidence-linked
ELF-2026-0013Dormant

Media

Conference sponsorship disclosure debate

Community questions about sponsor visibility led organizers to publish a revised disclosure policy.

Sources
9
Updates
6
Last checked
6d ago
Evidence-linked
ELF-2026-0009Resolved

AI

AI benchmark attribution controversy

Researchers and builders debated dataset provenance, credit, and the language used in a launch announcement.

Sources
31
Updates
15
Last checked
2w ago
Evidence-linked

03 One controversy, two layers

Conversation is loud.
The record is careful.

eLafda gives both a place to exist without pretending they are the same thing.

A

COMMUNITY DISCUSSION

People react, debate, question, and add context.

  • ↗ Opinions and analysis
  • ↗ Questions and firsthand accounts
  • ↗ Votes shape discovery, not truth

OPEN WITHIN POLICY

B

CANONICAL RECORD

Claims enter the timeline only after sources and wording pass review.

  • ✓ Neutral, attributed wording
  • ✓ Evidence attached to every claim
  • ✓ Corrections and revisions preserved

REVIEWED BEFORE PUBLISHING

04 Built in public

From “did you see this?”
to a durable record.

  1. 01

    Nominate

    Share a thread, source, or missing update through the web, or eventually tag the bot.

  2. 02

    Source

    Separate fact, allegation, opinion, and satire. Attach lawful primary evidence.

  3. 03

    Review

    Contributors check duplicates; archivists review wording, relevance, and support.

  4. 04

    Preserve

    Accepted events join a versioned timeline with attribution and a public change trail.

05 Receipts, responsibly

Built for memory.
Designed for restraint.

Archiving controversy carries real risk. Safety isn’t footer copy; it is part of the product model.

ATTRIBUTION

Allegations stay allegations.

We say who alleged what and never turn an investigation, complaint, or arrest into a declaration of guilt.

RIGHT TO REPLY

Responses get equal daylight.

Material responses, corrections, and contrary evidence appear with comparable prominence.

PRIVACY

Public interest has boundaries.

No doxxing, intimate media, private records, or attempts to identify private people from images.

TRANSPARENCY

Power leaves a paper trail.

Canonical edits and moderation decisions are versioned, attributed, and open to appeal.

06 The archive is opening

Help the internet
remember better.

eLafda is open source and in active development. The first archive will focus on Indian Tech Twitter while the review and moderation systems take shape.

Follow the build