Updated content
All checks were successful
Build and Deploy / build-and-deploy (push) Successful in 1m15s
All checks were successful
Build and Deploy / build-and-deploy (push) Successful in 1m15s
This commit is contained in:
parent
a3502289ae
commit
99636bf2c2
8 changed files with 36 additions and 34 deletions
2
Garden
2
Garden
|
|
@ -1 +1 @@
|
|||
Subproject commit b76f4907c5cb27ec0369ef18864a36f2c105db72
|
||||
Subproject commit 16a2f6b7eb6358d30b278c6ced810ffa2dce956e
|
||||
|
|
@ -14,7 +14,7 @@ const pageData = useData();
|
|||
<p>205 words, ~1 minute read. <span v-html="data[`site/${pageData.page.value.relativePath}`]" /></p>
|
||||
<hr/>
|
||||
|
||||
<details><summary>Referenced by:</summary><a href="/garden/digital-locality/index.md">Digital Locality</a><a href="/garden/fedi-v2/index.md">Fedi v2</a><a href="/garden/incremental-social/index.md">Incremental Social</a><a href="/now/index">/now</a></details>
|
||||
<details><summary>Referenced by:</summary><a href="/garden/digital-locality/index.md">Digital Locality</a><a href="/garden/fedi-v2/index.md">Fedi v2</a><a href="/garden/incremental-social/index.md">Incremental Social</a><a href="/now/index">/now</a><a href="/garden/orchard/index.md">Orchard</a></details>
|
||||
|
||||
A multiplayer game I have in development. It'll be about optimizing a board of tiles to create certain patterns to improve resource gains. Players will work collaboratively to construct monuments. It will be built on the [Agentic Fediverse](/garden/fedi-v2/index.md) and experiment with [Digital Locality](/garden/digital-locality/index.md).
|
||||
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ const pageData = useData();
|
|||
<p>1818 words, ~10 minute read. <span v-html="data[`site/${pageData.page.value.relativePath}`]" /></p>
|
||||
<hr/>
|
||||
|
||||
<details><summary>Referenced by:</summary><a href="/garden/no-politics-rules/index.md">"No Politics" Rules</a><a href="/garden/chromatic-lattice/index.md">Chromatic Lattice</a><a href="/garden/decentralized-moderation/index.md">Decentralized Moderation</a><a href="/garden/filter-bubbles/index.md">Filter Bubbles</a><a href="/garden/orchard/index.md">Orchard</a><a href="/garden/social-media/index.md">Social Media</a><a href="/garden/virality/index.md">Virality</a></details>
|
||||
<details><summary>Referenced by:</summary><a href="/garden/no-politics-rules/index.md">"No Politics" Rules</a><a href="/garden/chromatic-lattice/index.md">Chromatic Lattice</a><a href="/garden/decentralized-moderation/index.md">Decentralized Moderation</a><a href="/garden/filter-bubbles/index.md">Filter Bubbles</a><a href="/now/index">/now</a><a href="/garden/orchard/index.md">Orchard</a><a href="/garden/social-media/index.md">Social Media</a><a href="/garden/virality/index.md">Virality</a></details>
|
||||
|
||||
A locality is a physical area or neighborhood where people live and regularly see each other. In the same way I believe strong [Local Communities](/garden/local-communities/index.md) are highly important in real life, I think [Social Media](/garden/social-media/index.md) would benefit from having _digital_ localities.
|
||||
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ const pageData = useData();
|
|||
<p>985 words, ~5 minute read. <span v-html="data[`site/${pageData.page.value.relativePath}`]" /></p>
|
||||
<hr/>
|
||||
|
||||
<details><summary>Referenced by:</summary><a href="/garden/incremental-social/index.md">Incremental Social</a><a href="/garden/kronos/index.md">Kronos</a><a href="/garden/orchard/index.md">Orchard</a></details>
|
||||
<details><summary>Referenced by:</summary><a href="/garden/incremental-social/index.md">Incremental Social</a><a href="/garden/kronos/index.md">Kronos</a></details>
|
||||
|
||||
Communities - be they discord servers, forums, message boards, etc. - tend to have rules, and you'll likely see the same rules come up often. One of these common rules is the "no politics" rule. These rules may vary slightly in wording, but all share in being highly contentious. These are easily the rules most often broken and most often fought over - for _and_ against.
|
||||
|
||||
|
|
|
|||
|
|
@ -12,32 +12,34 @@ import { useData } from 'vitepress';
|
|||
const pageData = useData();
|
||||
</script>
|
||||
<h1 class="p-name">Orchard</h1>
|
||||
<p>743 words, ~4 minute read. <span v-html="data[`site/${pageData.page.value.relativePath}`]" /></p>
|
||||
<p>1026 words, ~6 minute read. <span v-html="data[`site/${pageData.page.value.relativePath}`]" /></p>
|
||||
<hr/>
|
||||
|
||||
<details><summary>Referenced by:</summary><a href="/garden/digital-locality/index.md">Digital Locality</a><a href="/now/index">/now</a></details>
|
||||
|
||||
<details><summary>Tags:</summary><a href="/garden/my-projects/index.md">My Projects</a></details>
|
||||
|
||||
This is an [Agentic fediverse](undefined) app I'm designing and at least building a mock for. The purpose of the app is to organize and grow a [Network of Knowledge](/garden/network-of-knowledge/index.md) (or [Digital Garden](/garden/digital-gardens/index.md)) 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 [Digital Locality](/garden/digital-locality/index.md) and perhaps represent an alternative to traditional [Social Media](/garden/social-media/index.md).
|
||||
This is an [Agentic Fediverse](/garden/fedi-v2/index.md) app I'm designing and at least building a mock for. The purpose of the app is to organize and grow a [Network of Knowledge](/garden/network-of-knowledge/index.md) (or [Digital Garden](/garden/digital-gardens/index.md)) 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 [Digital Locality](/garden/digital-locality/index.md) and perhaps represent an alternative to traditional [Social Media](/garden/social-media/index.md).
|
||||
|
||||
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. It's different than a traditional note-taking app because it works with conversations directly, which is how my "notes" on a topic initially start out.
|
||||
|
||||
Core to this project is improving how conversations online are carried out. It's inspired by [Commune](/garden/commune/index.md), and would follow a lot of the recommendations in the [chat glue](https://a9.io/glue-comic/) comic.
|
||||
Core to this project is improving how conversations online are carried out. It's inspired by sort of mashing up [The IndieWeb](/garden/the-small-web/index.md) and [Commune](/garden/commune/index.md), and would follow a lot of the recommendations in the [chat glue](https://a9.io/glue-comic/) 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 [Agentic Fediverse](/garden/fedi-v2/index.md) for details on how to run it sustainably and still offer free tiers to users.
|
||||
|
||||
## Implementing Chat Glue
|
||||
|
||||
As you converse in your group chats and DMs, you can specify topic changes. These will break the conversation up into pieces, and each piece gets added to each of the topics it was about (with links to the convo from before and after that one).
|
||||
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).
|
||||
|
||||
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.
|
||||
|
||||
Exactly where these DMs and group chats are coming from isn't super clear in my mind. I want [Digital Locality](/garden/digital-locality/index.md), 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.
|
||||
|
||||
In theory we could take the [Chromatic Lattice](/garden/chromatic-lattice/index.md)'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'll learn from Chromatic Lattice anyways and find a better solution to this problem.
|
||||
|
||||
## Non-conversation Notes
|
||||
|
||||
In addition to including conversations, I want to support freeform notes that also discuss one or more topics. Through leaf's compositional structure, in theory any entity should be able to be added to the network.
|
||||
In addition to including conversations, I want to support freeform notes that also discuss one or more topics. Another type of non-conversation note could be excerpts from online articles, which could be automatically cited. Through leaf's compositional structure, in theory any entity should be able to be added to the network.
|
||||
|
||||
Another type of non-conversation note could be excerpts from online articles, which could be automatically cited.
|
||||
|
||||
When allowing these kinds of notes, users should be encouraged to split notes as small as possible. This allows us to avoid needing something like [Garden-RSS](/garden/garden-rss/index.md) by just showing that a note has updated, and showing the new content.
|
||||
When allowing these kinds of notes, users should be encouraged to split notes small if possible. This could potentially allow us to avoid or delay the need for something like [Garden-RSS](/garden/garden-rss/index.md), and instead allow us to just mark entire notes as changed.
|
||||
|
||||
## The Topic Graph
|
||||
|
||||
|
|
@ -45,13 +47,13 @@ If a note was about multiple topics it forms a link between those topics and con
|
|||
|
||||
Links can also be manually created, and all links can be labeled to display a relationship between two topics, like "x is a y" or "x is similar to y" or "x contains y". These would be stored as specially marked notes and can be made public like any other. Selecting an edge will show all relationships that edge has been labeled with, along with any other notes that contain both topics.
|
||||
|
||||
## Sharing
|
||||
## Sharing Notes
|
||||
|
||||
You can jump to other people's gardens and see their public notes. You should be able to take any of those notes or the whole graph and include it in your own, so they are part of your searches etc. There'll need to be a good way of displaying changes, aliasing topics, and proposing edits to other peoples' pages. A way to "fork" someone's page so you can have a locally modified version. Overall, this should be very reminiscent of the [IndieWeb](/garden/the-small-web/index.md).
|
||||
You can jump to other people's gardens and see their public notes (via a friends list or via a mutual chat room). You should be able to take any of those notes or the whole graph and include it in your own, so they are part of your graph and queries. There'll need to be a good way of displaying changes, aliasing topics, and proposing edits to other peoples' pages. A user should also be able to "fork" someone's notes so they can modify them, and maintain a link to the original note but no longer auto-update them.
|
||||
|
||||
This would help spread corrections to articles by amending people's notes on the event and spreading them further.
|
||||
I think a conversation should show a sidebar of notes from both the user's network as well as any public notes from any other active participants' networks that relate to the set of topics being discussed. I think this would help encourage message gardening and assist with distributing information. We could go a step further and notify participants when those notes get added to or edited, which could help with corrections to articles getting spread to those who saw the original incorrect information (something that traditional media doesn't do well).
|
||||
|
||||
We'll need to be careful this doesn't lead to centralizing power, though. We don't want a federation of hubs, it should be fully decentralized. I'm not sure how the chat part should be. Community driven simplifies things and is appealing for people who make something and want a place where people can seek and provide guidance on using the thing. But its against the spirit of decentralization.
|
||||
We'll need to be careful sharing notes doesn't lead to centralizing power. I think if you subscribe/follow someone's graph, it shouldn't include the pages they've followed (although forks would be fine). This would lead to [Digital Locality](/garden/digital-locality/index.md) and all the benefits it entails. However, this might make it harder for movements to spread, because it means it spreading requires people to write new content rather than sharing existing content. I believe (perhaps optimistically) that movements can succeed in this environment, but perhaps instead there's a happy medium we can strike, so high quality notes can be spread without leading to issues like non-consensual [Virality](/garden/virality/index.md).
|
||||
|
||||
## LLMs
|
||||
|
||||
|
|
@ -61,10 +63,4 @@ LLMs could also be given the topics as context and be able to query the network
|
|||
|
||||
## Tech Stack
|
||||
|
||||
It'll use the [Agentic Fediverse](/garden/fedi-v2/index.md) to store the messages and other data, making the whole app [Local-First Software](/garden/local-first-software/index.md). The rest of the app will be a web-based UI, using [Neutralino.js](https://neutralino.js.org/) or an alternative.
|
||||
|
||||
Actually, [tauri](https://v2.tauri.app/) apparently doesn't require rust per-say, and has things like mobile support and a better dev experience.
|
||||
|
||||
It'll use [Incremental Social](/garden/incremental-social/index.md) as the default iroh node and handle any other (optional) server side features.
|
||||
|
||||
Consider using [Animata](https://animata.design/) components
|
||||
It'll use the [Agentic Fediverse](/garden/fedi-v2/index.md) to store the messages and other data, making the whole app [Local-First Software](/garden/local-first-software/index.md). The frontend of the app will be built in [tauri](https://v2.tauri.app/). It'll use [Incremental Social](/garden/incremental-social/index.md) as the default iroh node and handle any other (optional) server side features.
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ const pageData = useData();
|
|||
<p>27 words, ~0 minute read. <span v-html="data[`site/${pageData.page.value.relativePath}`]" /></p>
|
||||
<hr/>
|
||||
|
||||
<details><summary>Referenced by:</summary><a href="/garden/advent-incremental/index.md">Advent Incremental</a><a href="/garden/planar-pioneers/index.md">Planar Pioneers</a></details>
|
||||
<details><summary>Referenced by:</summary><a href="/garden/advent-incremental/index.md">Advent Incremental</a><a href="/now/index">/now</a><a href="/garden/planar-pioneers/index.md">Planar Pioneers</a></details>
|
||||
|
||||
<details><summary>Tagged by:</summary><a href="/garden/advent-incremental/index.md">Advent Incremental</a><a href="/garden/kronos/index.md">Kronos</a><a href="/garden/planar-pioneers/index.md">Planar Pioneers</a></details>
|
||||
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ const pageData = useData();
|
|||
<p>396 words, ~2 minute read. <span v-html="data[`site/${pageData.page.value.relativePath}`]" /></p>
|
||||
<hr/>
|
||||
|
||||
<details><summary>Referenced by:</summary><a href="/garden/digital-locality/index.md">Digital Locality</a></details>
|
||||
<details><summary>Referenced by:</summary><a href="/garden/digital-locality/index.md">Digital Locality</a><a href="/garden/orchard/index.md">Orchard</a></details>
|
||||
|
||||
Virality is the ability of something to "go viral" on a network - spread far and wide throughout the network. On traditional social media, this refers to how influencers and advertisers will have their content spread, but also specific posts from smaller posters can get picked up by the algorithm and spread as well.
|
||||
|
||||
|
|
|
|||
|
|
@ -11,26 +11,32 @@ import { useData } from 'vitepress';
|
|||
const pageData = useData();
|
||||
</script>
|
||||
<h1 class="p-name">/now</h1>
|
||||
<p>186 words, ~1 minute read. <span v-html="data[`site/${pageData.page.value.relativePath}`]" /></p>
|
||||
<p>304 words, ~2 minute read. <span v-html="data[`site/${pageData.page.value.relativePath}`]" /></p>
|
||||
<hr/>
|
||||
|
||||
This "now page" offers a big picture glimpse into what I’m focused on at this point in my life. [What is a now page](https://nownownow.com/about)?
|
||||
|
||||
## Digital Gardens
|
||||
## Profectus
|
||||
|
||||
I'm building (at least) a mockup for [Orchard](/garden/orchard/index.md), an app for message gardening into a [Network of Knowledge](/garden/network-of-knowledge/index.md).
|
||||
I'm currently working on wrapping up a large update to [Profectus](/garden/profectus/index.md), which simplifies how features are made and makes parts of them more modular and composable. This update also includes a rewrite to how boards work that will make them far more robust and usable in a variety of situations.
|
||||
|
||||
Ultimately, I think this project could have some implications on how _this_ digital garden operates, so I've decided to stop further indieweb integrations like webmentions for now. I'd like to see a server be able to bridge indieweb and agentic fediverse posts, and start using the agentic fediverse posts as my new source of truth.
|
||||
## Timeline on this website
|
||||
|
||||
## Incremental Social
|
||||
I'm working on a large update to this website that'll include a new global feed of my activity across many websites going back an entire decade. It also replaces Vitepress with Nuxt.JS and no longer using a (heavily) modified template, instead just having the whole thing implemented by me. It'll also include features like better search and a graph of garden pages.
|
||||
|
||||
I'm running and improving the social media site [Incremental Social](/garden/incremental-social/index.md), along with CardboardEmpress.
|
||||
## Digital locality
|
||||
|
||||
I'd like to make it host an iroh node for hosting agentic fediverse content, managing a keypair for each account (with options for migration).
|
||||
I've been thinking a lot about social media design and how it could be improved, which has distilled into my writeup on what I call [Digital Locality](/garden/digital-locality/index.md), which I believe is the solution to decentralized moderation that combats hate and misinformation.
|
||||
|
||||
## Chromatic Lattice
|
||||
I have plans for two experiments into digital locality:
|
||||
|
||||
I'm working on a multiplayer incremental game called [Chromatic Lattice](/garden/chromatic-lattice/index.md) . It's still largely in the concept phase, and may even be built on the [Agentic Fediverse](/garden/fedi-v2/index.md).
|
||||
### [Chromatic Lattice](/garden/chromatic-lattice/index.md)
|
||||
|
||||
A multiplayer co-operative incremental game on the [Agentic Fediverse](/garden/fedi-v2/index.md). This will come alongside various improvements to [Incremental Social](/garden/incremental-social/index.md), such as making it operate as an iroh node.
|
||||
|
||||
### [Orchard](/garden/orchard/index.md)
|
||||
|
||||
An app for message gardening into a [Network of Knowledge](/garden/network-of-knowledge/index.md) and represents my vision for an alternative approach to social media that is better at not making people angry or doomscroll, combat misinformation, and encourage stronger relationships with those you meet online, rather than just wading through an ocean of strangers.
|
||||
|
||||
## Kronos
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue