https://mindscape.pub is an open source, nested graph forum.
The owner of a post can "open" the post, so that it contains its own subgraph of posts.
The owner is then the moderator of that subgraph, able to modify its overall layout (including removal of posts).
When a user posts into someone else's subgraph, they can modify the layout (including post removal) only for their own posts.
Posts that are removed from a local subgraph remain in the global graph.
Posts can be linked to one another, as well as pasted into subgraphs.
Mindscape is a client-server architecture that implements the Arrow Protocol.
The Arrow Protocol seeks to enable the composition of posts (a post, i.e. any piece of data that has its own URI) into modular trees, called subgraphs, that are local views of a global graph.
For instance, suppose two people each write an article in the form of a subgraph. The two subgraphs could quote the same post. The intersection of these subgraphs on this post would connect readers of one subgraph to the other, and vice versa.
In online writing, modularity is powerful because each module has its own linkage, i.e. context, associated with it.
Each subgraph is a curated view. Posts are resusable across subgraphs. Use subgraphs to organize subgraphs.
The key innovation of the Arrow Protocol is the usage of Arrows instead of embedded URIs as the main way to link information together.
An Arrow is essentially a row or object with the structure (id_URI, source_URI, target_URI, data).
source_URI and target_URI can be set to NULL or to id_URI to implement a post.
otherwise, source_URI !== target_URI, and the Arrow functions as a link.
Using Arrows as links has a few advantages over using embedded URIs, aka hyperlinks, to structure a graph.
- Modularity. We can update the linkage between posts without modifying the posts.
- Bidrectional travel. If we index the Arrows by source_URI and target_URI, we can query for links in either direction.
- Intra-arrow metadata. Since each arrow is its own row/object, the schema can be extended with additional data, e.g. authorID, upVotes, etc.
- Extra-arrow metadata. Since each arrow is has its own URI, we can attach Arrows to it to attach arbitrary metadata to it.
Furthermore, Arrows are compatible with the continued usage of hyperlinks.
Twigs are an additional data type used to define the layout of a subgraph.
They enable a single Arrow to take part in multiple subgraphs.
They define the tree structure of nesting of subgraphs.
They also define the tree layout of posts within a subgraph.
- Mobile app. So you can receive notifications and make calls on you mobile device.
- Arweave. So that each arrow/subgraph is saved into the permaweb.