. Last tended to <ahref='https://code.incremental.social/thepaperpilot/pages/commit/91d19e942e7182239050288325e876bf7dd413ef'title='Fri Dec 20 06:15:01 2024 -0600'><timeclass='dt-updated'datetime='Fri Dec 20 06:15:01 2024 -0600'>2024-12-20</time></a>
.</span></p><hr><details><summary>Referenced by:</summary><ahref="/garden/digital-locality/index.md">Digital Locality</a><ahref="/now/index">/now</a></details><details><summary>Tags:</summary><ahref="/garden/my-projects/index.md">My Projects</a></details><p>This is an <ahref="/garden/fedi-v2/">Agentic Fediverse</a> app I'm designing and at least building a mock for. The purpose of the app is to organize and grow a <ahref="/garden/network-of-knowledge/">Network of Knowledge</a> (or <ahref="/garden/digital-gardens/">Digital Garden</a>) sorted by topic. It achieves this through a concept called message gardening, the process of converting casual conversations into formal, referenceable stores of knowledge. It would be an experiment in <ahref="/garden/digital-locality/">Digital Locality</a> and perhaps represent an alternative to traditional <ahref="/garden/social-media/">Social Media</a>.</p><p>The original problem I was trying to solve is having a lot of conversations about various topics stretching back far into the past and across many platforms. I often want to review something I said on a given topic and find it difficult to do so. This app would make it far easier to retrieve my notes on any topic, and collect those notes into a useful resource about that topic (a process called "message gardening"). It's different than a traditional note-taking app because it works with conversations directly, which is useful because discourse is typically what prompts me to collect my thoughts on a topic in the first place.</p><p>Core to this project is improving how conversations online are carried out. It's inspired by sort of mashing up <ahref="/garden/the-small-web/">The IndieWeb</a> and <ahref="/garden/commune/">Commune</a>, and would follow a lot of the recommendations in the <ahref="https://a9.io/glue-comic/"target="_blank"rel="noreferrer">chat glue</a> comic. Contrary to each person having to own a personal website, this platform should in theory be more accessible by allowing people to skip the step of finding a domain to semi-permanently attach their identity to, and not having to pay a subscription cost to maintain it. See the page on the <ahref="/garden/fedi-v2/">Agentic Fediverse</a> for details on how to run it sustainably and still offer free tiers to users.</p><h2id="implementing-chat-glue"tabindex="-1">Implementing Chat Glue <aclass="header-anchor"href="#implementing-chat-glue"aria-label="Permalink to "Implementing Chat Glue""></a></h2><p>As you converse in your group chats and DMs, you can specify topic changes. These will break the conversation up into pieces called notes, and each piece gets added to each of the topics it was about (with links to the convo from before and after that one).</p><p>Notes should also allow specific parts, up to the character level, to reply to, react to, otherwise annotate, or mark as a topic change. This is something to think about with regards to decentralized moderation and things like muting pages or gardens. Plus the matter of displaying the sync to the user.</p><p>Exactly where these DMs and group chats are coming from isn't super clear in my mind. I want <ahref="/garden/digital-locality/">Digital Locality</a>, which means avoiding large groups of users and limiting the influence of individual posts and posters. We don't want a federation of discrete independently moderated communities, as that will lead to centralizing power and influence. But, organizing communities this way is very common due to its convenience and appeal. If you make, say, an open source library and want people to know where they can go to discuss how to use the library, show off what they used it for, etc. then you're likely to create a discrete community for it.</p><p>In theory we could take the <ahref="/garden/chromatic-lattice/">Chromatic Lattice</a>'s initial approach and just have a chat room tied to each user, but I'm not confident that'll translate well to this project. I'm leaving this open ended, since I expect we&
