3 ms·
Here's how I understand this project at this time. 1. There exists a set of files, or nodes, contained in GIT repositories, that sum up to a personal wiki, of
by mikewarot 6y ago
Here's how I understand this project at this time.
1. There exists a set of files, or nodes, contained in GIT repositories, that sum up to a personal wiki, of sorts. These files, in the case of http://anagora.org http://anagora.org, are copied from https://github.com/flancian/agora https://github.com/flancian/agora
2. In those files are links in a specified format to other such wikis.
3. A server (Agora Server) renders a the files in a manner far more useful for interaction. http://anagora.org http://anagora.org is running said server. The actual data being served is (for performance reasons, I assume) a copy of the reference wiki it can them push changes back up to.
4. The server also has a daemon that is polling other such sites (presumably the source, not the other servers) looking for more content to add to its repository.
Question: Do those other sources get added back to the primary repository?
5. If we want to add our own, we clone a starter kit, and host our own server. It could be local, or on the internet. The data needs to be public, the server itself doesn't. If this is true, this makes hosting things much easier, as there is no need to maintain a server on the internet, just have a valid GITHUB or other such account in good standing, and valid email for the signup process.
Do I have that right?
- flancian 6y agoThank you for the great TLDR :) Some slight corrections and comments below. 1. https://github.com/flancian/agora https://github.com/flancian/agora does not contain actual user content currently (see 4. for historical context), but rather serves as a "root node": it contains a base [[CONTRACT]] (for now just a document stating a code of conduct that all users must follow; might be expanded into something fancier using a <buzzword>blockchain</buzzword>) and pointers to repositories (currently one per user) that contain the actual content. You might laugh at how simple this currently is :) https://github.com/flancian/agora/blob/master/util/reset https://github.com/flancian/agora/blob/master/util/reset 2. Yes; the format is currently precisely Markdown plus [[wikilinks]] as an extension. [[wikilinks]] are "dead" by default in Markdown, being non standard; the [[agora server]] makes them go live by anchoring them to a context (an [[agora]] [[node]]). 3. Yes -- although [[agora server]] is currently unable to push changes upstream to user repositories, this is planned. For now it's just a renderer. Users use tools of their choice ([[roam]], [[foam]], [[obsidian]], etc.) to create and maintain their repositories. I use [[foam]] on VS Code. 4. Right now the Agora only pulls from user repositories as per 1.; eventually it will indeed pull from other Agoras, forming a federated network. Agoras will probably interact as long as their contracts are compatible. A: as per 1., currently no content is actually stored in the primary repository. Note that initially the repository did contain the pulled content, as it was included with 'git subtree'; but on second thought I thought it was simpler and cleaner to have the root repository only contain pointers. 5. Yes, although note that the data does not need to be public either; you can run a graph from any source as long as you make files in the right format available to [[agora server]]. https://anagora.org/node/CONTRACT https://anagora.org/node/CONTRACT https://anagora.org/node/wikilinks https://anagora.org/node/wikilinks https://anagora.org/node/roam https://anagora.org/node/roam https://anagora.org/node/foam https://anagora.org/node/foam https://anagora.org/node/obsidian https://anagora.org/node/obsidian https://anagora.org/node/agora-server https://anagora.org/node/agora-server https://anagora.org/node/agora https://anagora.org/node/agora https://anagora.org/node/node https://anagora.org/node/node