User Story: #MakingHistory - Digital Family Archive & Activist Memory-Building
Goal: Digitize and share activist / family archives primary sources, stories, documents in a way that’s open, participatory, and rooted in real community, not just relic preservation. The archive becomes both memory and tool for social change.
Steps & flows
Setup infrastructure - Spin up a small hosted VPS or desktop instance. Install a #DAT / ActivityPub / peer-to-peer hybrid archive app (#makinghistory).
Upload & seed - Scan family / activist archival material: photos, videos, letters, flyers. Add basic metadata (date, place, people involved). Upload into the system.
Community building - Invite family, networks, activist groups to install the app. Form an affinity group around the archive.
Columns & filtering - Interface: columns like New, Recent, plus user-added ones (by theme / era / type). Users see flows of items (boolean filters, hashtag categories) they care about. Interaction & tagging - Users contribute: add metadata, tags, stories behind objects.
Swipe, browse, edit. Items shift columns/categories as metadata evolves.
Story feature / Narrative building - With categorized & metadata-tagged material, users can assemble “stories”, narrative essays, timelines, thematic presentations.
Sharing & impact - Publish these histories publicly: open & CC-licensed. These become grassroots counterhistories. Use stories to inspire activism, education, or community organizing - showing how history roots current struggles.
Exhibition mode (Extension) - In physical exhibitions, visitors can use the app (on tablets or provided devices) to browse and contribute live: tagging, adding memories, shaping the narrative in situ.
Why it matters, it opens up history: Moves memory out of centralized institutions (archives, museums) into the hands of communities who lived it.
Counter-narrative: Offers history from below, not only top-down or official versions.
Living archive: It’s participatory, not passive. People don’t just view; they shape meaning.
Grounded in #4opens: Open data, open process, open source, open access.
Potential challenges & what to compost (Lessons from past failures) What has gone wrong before, how we compost it in this story:
Burnout among core volunteers, people overload metadata tasks, get exhausted; later momentum fades. Spread workload through community; avoid “metadatabase queen/king” roles. Use columns & tagging that feel playful and meaningful, not tedious.
Power consolidation, with one person / small team becomes the de facto gatekeeper of what’s seen / what counts. Use shared governance: decisions about themes, display, moderation are open. Rotate roles. Use open process.
Tech falling out of maintenance with custom tools built, then abandoned. Use stable, simple tools with community-supported code. Make sure data formats are portable.
Exclusion in “participation” Some voices get left out, marginalized, younger, remote. Proactively invite diverse participants; ensure the interface / metadata vocab doesn’t force people to use jargon; make offline or low-bandwidth modes possible.