From f057ec7bcf39a484beb05b07fc4bbf42b066a7db Mon Sep 17 00:00:00 2001 From: Admin Date: Thu, 29 Feb 2024 18:22:47 +0000 Subject: [PATCH] Add #makeinghistory roadmap for #dat test: --- ...akeinghistory-roadmap-for-%23dat-test%3A.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 %23makeinghistory-roadmap-for-%23dat-test%3A.md diff --git a/%23makeinghistory-roadmap-for-%23dat-test%3A.md b/%23makeinghistory-roadmap-for-%23dat-test%3A.md new file mode 100644 index 0000000..17986e2 --- /dev/null +++ b/%23makeinghistory-roadmap-for-%23dat-test%3A.md @@ -0,0 +1,18 @@ +#makeinghistory roadmap for #dat test: + +1) Single column listing objects - two instances that can post to each other - objects (text, image, links). Listing objects by last posted. Very basic. + +2) then hashtag columns - mastodon has this, can mostly copy existing implementation. + +3) add stories, simply another object that uses existing objects and links with context text. Think of this as a human story index. (a collective community account publishes this - how does this work) +hamish campbell + +4) We need to think about flows between instances, federating etc. + +The desktop interface is tweetdeack like, think copying mastodon implementation. + +The mobile interface is single column scroll to next object, or click on object for full screen then sideswipe to next object. Think "Tusky" mastodon android app + +Every object has an edit (if you have a login), and editable hashtag and a comment option. + +The edits are then passed across federation/trust flows, option 4) \ No newline at end of file