An overview of projects
#Indymedia Classic
Most of the data is a common. Core flows:
- Newswire (public, chronological): Anyone can post – and it will appear if they are trusted. It goes to moderation if they are not. This is mostly populated by editorial collective chosen trusted flows into the instance
- Features (curated): Promoted stories written by the editorial collective from the newswire resources.
- Hidden (private): Moderated view, not visible publicly unless let through by collective to newswire.
View Structure: Mostly fixed: Three flows, with some tag-based navigation as optional/secondary, so can think of this as a “fixed” news landing page with flows. A button to consume and create tag flows, the #makinghistory #UX
Editorial model: Collective moderation, through affinity group consensus.
Metaphor: Like a river (Newswire) feeding into a reservoir (Features), with a dam (Hidden) filtering out toxic waste.
#MakingHistory
Most of the data is a common. Core Structure:
- Media object (any format) fragments?
- Stories: Everything starts as a crafted piece (linked original fragments).
- Tag-based flows: Rich tagging creates multiple dynamic timelines/streams of stories and fragments?
- Moderation (private): Curators can review, prioritise, or archive
- Interface: Inspired by Tweet Deck-style dashboards: multiple parallel tag/stream views.
Emphasis: Encourages narrative threading, historical context, and thematic clustering over time.
Metaphor: A garden of stories with paths (tags) between plots – some bloom, others get composted behind the scenes.
Shared DNA (and how #OMN fits)
Both: Are people-powered publishing systems. Use a public/private split for moderation and trust-building. Emphasize non-corporate, grassroots communication.
The #OMN acts as a bridge: letting projects like Indymedia and MakingHistory interoperate, share flows, and build trust networks across platforms – all within the ethos of the #4opens.
To be thought about:
The codebase/ActivityPub/OMN all have assumptions that likely need bridging.
Do we use groups to implement collective data – commons – we give admin rights over data by group membership? Then we keep legacy admin roles, but try and push them into the background and plan for them to fade away in the end.
Trusted/untrusted is this based on groups/instances/individuals/tag flow from source or general?
We need to add metadata to objects…
We need every object to be a wiki… This includes the articles – we end up with the Wikipedia of news based on organic trust groups and grassroots street news views rebuilding what it is to be #mainstreaming
More questions…