From 1c2b8c7dfb369a0eeff0a73eaf2c7728c69cd588 Mon Sep 17 00:00:00 2001 From: saunders Date: Wed, 22 Jul 2026 08:16:13 +0100 Subject: [PATCH] Reinstate TODO file The content was previously deleted for an unknown reason. --- TODO.md | 105 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 105 insertions(+) diff --git a/TODO.md b/TODO.md index e69de29..ef1a456 100644 --- a/TODO.md +++ b/TODO.md @@ -0,0 +1,105 @@ +# TODO + +**N.B.** The terminology used herein is definitely a work in progress, ... +along with all other aspects. + +The aim for the initial phase(s) is to implement the following five functions, +referenced from: https://hamishcampbell.com/omn-projects-are-tools-for-you-to-change-and-challenge-the-world-we-live-and-die-in/ + +- Link / Subscribe + Plumb a new pipe into the network. A flow of content comes in or goes out. + Each pipe can connect to any other function. + +- Trust / Moderate + Flow passes through a sieve. Trusted content moves smoothly; noise gets + filtered. You can send flows straight through, into holding tanks, or + split them into new pipes. + +- Rollback + Empty the tank, rewind a flow, or remove specific objects. Essential for + correcting errors, spam, or bad data. + +- Edit Metadata + Add tags or notes to the “tail” of a data object. Metadata determines how + content gets sieved and aggregated. This is the backbone of news curation + in the OMN. + +- Publish + Add new content objects into the flow. Optionally editable. Publishing is + just another pipe into the system. At the core sits the storage tank: + a simple database holding all the flows. + +## Phase 1 + +The following terms are purely for differentiating between certain implementation details. + +Key: +``` +"PUBLIC": Viewable when not logged in +"USER": Viewable when logged in +"MOD": Viewable when logged in with sufficient permissions +``` + +> NOTE: There was no user in the original Indymedia, but there will be in this version. +> (Saunders) Meaning users who are or are not involved with the output of a given instance? + +### Behaviour + +- [ ] 'Events' + - A "federated flow" of events; an input feed of items related to the + theme/topics of the MakingHistory instance. UI/X name may differ but + this is short and useful for code. + - All visible tags can be a flow, we like nature metaphors so we use flow; + the only thing that would not flow is the mod (not trusted) items. + - _Emissary Template; based on 'inbox' ?_ + - PUBLIC: + - (syn. Newswire from Indymedia) + - View + - [ ] Curated (syn. Moderated for Indymedia) + - [ ] Most recent N items + - [ ] Dynamic load earlier items on request (e.g. scroll) + - MOD: + - (syn. Mod Flow from Indymedia) + - Flagged items could end up here? + - View + - [ ] Uncurated (syn. Unmoderated from Indymedia ?) + - (See PUBLIC) + - Edit: Mark item(s) as "public"/"private" + - Filters (hash tags, users, whole instances, ...) + - Individual items/objects +- [ ] 'Stories' + - (syn. Features from Indymedia) + - _Emissary Template(s)_ + - based on ? + - PUBLIC: + - View + - [ ] Filter by tag ? + - [ ] Search ? + - USER: + - View + - (See PUBLIC) + - Save filter(s) + - MOD: + - View + - (See USER) + - Create/Edit + - [ ] Interactive version of 'Federated Flow' to cite/reference + - Filters + - Checkboxes (or equivalent) per item +- [ ] 'Tagflow' + - _Emissary Template; based on ?_ + - USER: + - View + - [ ] Tweet-deck style dashboard of parallel tag/stream views + - Create/Edit + - [ ] Custom streams based on filter set + - [ ] Boolean logic + +### Structure + + - [ ] Groups: + - _Emissary groups_ + - Curators (syn. Moderators) + - other? + + Rest looks fine, more questions :)