πŸ“š node [[agora]]

Agora

Agora

This looks like a really cool way of aggregating digital gardens into one place. To produce a community garden (or, an agora). Interesting to contrast with how a solely P2P way of connecting gardens might work, no central aggregator.

An Agora is a distributed, goal-oriented social network centered around a cooperatively built and maintained [[knowledge graph]]. The implementation you are currently looking at tries to assemble such a graph out of a collection of digital gardens.

– GitHub - flancian/agora

See also [[sister sites]].

See: [[What do I think about the Agora?]]

Welcome to [[boris mann]]'s section of the agora!

We're experimenting with [[Connecting to the Agora]], and what some of the configurations and conventions are. The [[Anagora]] page has my notes and feature requests.

Status

  • This document was mostly written in 2018. The Agora was then just a thought experiment. It has since grown to be a living project.
  • As late as 2020-10-17, the Agora barely existed as a concrete implementation -- it was not a single tool but rather many which you could use in tandem following a convention, which I provisionally named Agora Protocol.
  • As of 2022-01-02, a reference Agora is online on https://anagora.org . Using terminology gained and derived in the last three years (with the help of the Agora community!), I can now describe it as a [[knowledge commons]].

Regardless of implementation details, an Agora can be assembled out of off-the-shelf parts available on the internet, mostly for free:

  • Knowledge management tools used for the purpose of building a distributed knowledge graph, following the aforementioned convention based on lazily evaluated [[wikilinks]]. See https://anagora.org/agora-editor for a review of some of the tools in this space, or Roam Likes for an older take.
  • Social networks and the constructive bits of the internet as we have them, annotated and enriched using open tools and standards.
  • An explicit constructive social contract. For reference you can consult the anagora.org default.

If you are interested in collaborating on building Agoras or similar constructive spaces, please reach out or peruse the Git repository.

See also: https://flancia.org/go/agora-howto , https://threadreaderapp.com/thread/1322619094563258370.html.

Head

You can think of the Agora as a convention based social network; an optional, user-controlled annotation layer that can be applied over any internet platform which supports user-generated content.

I think one of the best possible uses for such a network would be to use it to pro-socially maintain a distributed knowledge graph tailored specifically to the goal of solving problems: those of its users and society at large.

Its users, as a cooperative group, could by default take a naive but rational approach to problem solving:

  • For each problem in the set P of all problems:
    • Describe it as thoroughly as possible.
    • Maintain a set of known or argued possible solutions, S(P).
  • For each solution in S(P):
    • Describe it as thoroughly as possible.
    • Maintain a set of resources (people, time, attention, money) needed to implement it, R(S).

Individual users could also declare their views on the state of the world explicitly: they define which subsets of P, S and R they agree with, in the sense that they believe they are feasible, true, interesting.

Users that agree on their defined subsets can then efficiently collaborate on solutions as they become available by pooling of resources.

We apply some good old recursivity and seed the Agora with the problem of how to build itself. That is, how to build a system that allows participating users and entities to collaborate optimally in the face of adversity (such as biases, irrationality and even actual ill intent)1.

The Agora should be built on a federated protocol to limit the harmfulness of diasporas. Groups might temporarily diverge in their views enough to want to run separate Agoras, but different Agoras should be able to cooperate on problems and solutions for which there is enough ideological alignment, and eventually merge.

Tail

I have a more focused and detailed unpublished document which will probably replace or complement this chapter soon.

I know the premise sounds almost like a joke: what the world needs is a new social network. The internet and social networks are technologies we are just barely learning to live with, and the recent cause of a lot of polarization and political escalation and Trump Being President2. It doesn't sound at first like we should add another stick to that particular dumpster fire. But hear me out.

We need a designated place in the internet where we can discuss ideas in a constructive way. In particular, where we can discuss possible strategies to face the problems that humanity is facing. This is already happening, for sure; but is it happening somewhere on the internet where everybody can contribute? I don't think so. If the Agora exists already, please point the way -- I'd like to get there, and building it from scratch would be hard. The network of universities and institutes are the closest we have and I love them, but the Agora should be fully open and available to all over the internet, so every participating individual can contribute work and thought. Of course the whole internet could be an Agora; but the internet as a whole is chaotic and disorganized and thus its implicit Agora is entangled with places that are not constructive and not safe. There must be a better way.

Nick Bostrom has a paper on existential risk where he talks about a kind of lottery of ideas; humanity is constantly playing this game, the metaphor goes, and drawing ideas out of big lottery wheels of Science and Technology and Culture. Some of the balls in this wheel are colored white; these are good ideas. They contribute to human good, and we're glad we found them.

There are also black balls, though. These are bad3. They are things that, on the whole, produce enough bad to be existential risks to humanity. Nuclear power seemed to be this for a while; perhaps mutually assured destruction could have resulted in an apocalypse. But it didn't! Aren't we lucky? If (and it's a big if) things stay this way, we got away with playing with something dangerous. Perhaps we can use the idea for whatever good it holds (cheap and relatively safe energy), or perhaps we decide to bury it underground in a big vault of ideas (this one doesn't have to ever spin again) that says Do Not Go There, Trust Us. For now, though, the idea might still turn out to be black; we could, perhaps, represent this situation as a grey ball of whatever shade we deem most likely.

We need a social network for discussing ideas. For talking about Bostrom's lottery urn, and what it has in it for us. In the Agora, we discuss ideas and their shades and merit; we discuss, first and foremost, ethics. We talk openly and clearly about how to best move forward as a society of humans, with the knowledge we've gotten and the resources we have.

What if social networks are grey? How dark is their shade? The high modernist in me wants to believe that the structured flow of information is more of a good thing than a bad thing. But we need to be cautious, and this is why I wrote this and you are reading it now.

I need your help.

In Flancia there is no poverty.

  1. To start with, discussion in the Agora should follow the tried and tested Principle of Charity.↩

  2. what if Twitter is already a decent Agora, and Trump just woke up to the fact that it's a superior meme transfer device sooner than others?↩

  3. White = good and black = bad is in the original paper. Now, an apology: I don't like the fact that our culture encodes bad things as black, it's associated with death, etc. I think associating black with badness is a bit trite in a world that puts so much stock on being a particular kind of yellow.↩

An agora, in its broadest sense, is a conceptual space where people attempt to bring an increased level of intentionality, explicitness, and mutual agreement to the principles and protocols for interacting in that space. A further aspect of the idea of an Agora is that it is a space which enables collaboration. In particular, it is a space that allows for collaboration guided by specific shared interests, without requiring the co-consitutients of the agora to be aligned more fully or generally in terms of their intentions, values, etc.

Some topics that the idea of an Agora is related to: [[transparency]] [[decentralized structures]] [[egalitarian principles]] [[judgement]] [[algorithms of interaction]] [[communication]] [[collaboration]] [[knowledge sharing]]

There are (infinitely) many possible variants of how this idea might be implemented in concrete, real-world situations. For example, an agora could be a space that is opened up inside a conversation between two people. Or it could be a collaborative project that is accompanied by specified rules. Or it could be a collective agreement about how to handle certain types of situations.

One variant of the idea of an Agora is a place where personal notes are shared, with the common goal of pooling information and sharing knowledge. One implementation of this idea is https://anagora.org . See also https://flancia.org/go/agora .

The term "Agora" and the basic idea come from [[Flancia]].

img side { lapin 77 {My visual take}}

Agora is a β€˜[[wiki]] like experimental [[social network]] and distributed knowledge graph’, so they said. Anagora is the only known public instance of it.

=> https://anagora.org/index

As far as I understand, it is some form of federation/aggregation of [[digital garden]]s with a big emphasis on graph-ity. Their analogue of [[pull" title="[[https://mycorrhiza.wiki/help/en/hypha | hyphae]]" class="wikilink">hyphae]] is called a [[pull" title="[[https://anagora.org/node | node]]" class="wikilink">node]], nodes are generated from contents from multiple sites.

The project is interesting. [[2022-01-18]] I wrote the author an email about the possibilities of making Agora and [[Mycorrhiza]] compatible. [[2022-03-06]] Melanocarpa was added to Anagora, along with [[Mycorrhiza support]].

The Agora network has an interesting idea of [[pull" title="[[https://anagora.org/go | go]]" class="wikilink">go]]ing.

The Agorans also seem to all be using [[git]]-based [[markdown]]-driven digital gardens. That's a poor choice of technology, in my opinion, but whatever works for them. Most digital gardens use markdown anyway.

What do you think about the Agora?

Feel free to use this open space to tell us! We'd love to improve it for you; in general, to make it more useful and inclusive for others.

-- [[flancian]]


Your opinion could be here :)

  • #push [[agora]]
    • #push [[agora writing]]
    • #push [[agora development]]
      • set up local dev environment in the train
      • [[better search]]?
        • what's a quantum of better search? it's pretty bad right now; e.g. [[poetry install]] would not bring up [[install poetry]]
          • would re-adding fuzzy matching fix this?
          • should I implement a simple search algorithm myself for the purpose of understanding how to solve this?
            • tokenization -> compute combinations is trivial but expensive
            • -> [[bag of words]] is cheap
              • this actually requires defining what is the source of truth for [[equivalence class]] and for [[proximity]] between nodes
              • I've always wanted to think of Agora search as as an exploration within a certain [[radius]] of an inferred center of gravity; maybe this is distance in some embedding?
                • -> [[edit distance]]
                  • seems like an interesting approach to explore next
        • [[auto pull wikipedia]] sort of also tackles this in a totally different direction, in particular if we extend it to [[wikidata integration]]: if wikidata surfaces an entity for us, volunteer its type; if the entity is far from the current node in an interesting way, maybe [[auto pull]] it as well after some time.
        • if I'm adding auto pull maybe it's time to make [[settings]] clearer, in particular have an easy toggle for auto pull to trigger or not (leads to [[agora autopilot]] maybe, which I've always thought could be very fun.)
  • #push [[agora]]
    • #push [[agora writing]]
    • #push [[agora development]]
      • set up local dev environment in the train
      • [[better search]]?
        • what's a quantum of better search? it's pretty bad right now; e.g. [[poetry install]] would not bring up [[install poetry]]
          • would re-adding fuzzy matching fix this?
          • should I implement a simple search algorithm myself for the purpose of understanding how to solve this?
            • tokenization -> compute combinations is trivial but expensive
            • -> [[bag of words]] is cheap
              • this actually requires defining what is the source of truth for [[equivalence class]] and for [[proximity]] between nodes
              • I've always wanted to think of Agora search as as an exploration within a certain [[radius]] of an inferred center of gravity; maybe this is distance in some embedding?
                • -> [[edit distance]]
                  • seems like an interesting approach to explore next
        • [[auto pull wikipedia]] sort of also tackles this in a totally different direction, in particular if we extend it to [[wikidata integration]]: if wikidata surfaces an entity for us, volunteer its type; if the entity is far from the current node in an interesting way, maybe [[auto pull]] it as well after some time.
        • if I'm adding auto pull maybe it's time to make [[settings]] clearer, in particular have an easy toggle for auto pull to trigger or not (leads to [[agora autopilot]] maybe, which I've always thought could be very fun.)
  • #push [[agora]]
    • #push [[agora writing]]
    • #push [[agora development]]
      • set up local dev environment in the train
      • [[better search]]?
        • what's a quantum of better search? it's pretty bad right now; e.g. [[poetry install]] would not bring up [[install poetry]]
          • would re-adding fuzzy matching fix this?
          • should I implement a simple search algorithm myself for the purpose of understanding how to solve this?
            • tokenization -> compute combinations is trivial but expensive
            • -> [[bag of words]] is cheap
              • this actually requires defining what is the source of truth for [[equivalence class]] and for [[proximity]] between nodes
              • I've always wanted to think of Agora search as as an exploration within a certain [[radius]] of an inferred center of gravity; maybe this is distance in some embedding?
                • -> [[edit distance]]
                  • seems like an interesting approach to explore next
        • [[auto pull wikipedia]] sort of also tackles this in a totally different direction, in particular if we extend it to [[wikidata integration]]: if wikidata surfaces an entity for us, volunteer its type; if the entity is far from the current node in an interesting way, maybe [[auto pull]] it as well after some time.
        • if I'm adding auto pull maybe it's time to make [[settings]] clearer, in particular have an easy toggle for auto pull to trigger or not (leads to [[agora autopilot]] maybe, which I've always thought could be very fun.)
  • #push [[agora]]
    • #push [[agora development]]
      • ship [[agora graph]] in some version?
      • [[dynamic subnodes]], sometimes also known as [[executable subnodes]]
      • easy improvement: I want to adjust the node/subnode icons back to what they were one or two months ago; a stack for a node made sense, whereas the current red book for node is puzzling.
    • #push [[agora chapter]] next steps
      • read George's email.
        • end of week as deadline for all, then we need to....
          • work on updated abstracts and...
          • start on the Markdown port.
  • #push [[agora]]
    • #push [[agora development]]
      • ship [[agora graph]] in some version?
      • [[dynamic subnodes]], sometimes also known as [[executable subnodes]]
      • easy improvement: I want to adjust the node/subnode icons back to what they were one or two months ago; a stack for a node made sense, whereas the current red book for node is puzzling.
    • #push [[agora chapter]] next steps
      • read George's email.
        • end of week as deadline for all, then we need to....
          • work on updated abstracts and...
          • start on the Markdown port.
  • #push [[agora]]
    • #push [[agora development]]
      • ship [[agora graph]] in some version?
      • [[dynamic subnodes]], sometimes also known as [[executable subnodes]]
      • easy improvement: I want to adjust the node/subnode icons back to what they were one or two months ago; a stack for a node made sense, whereas the current red book for node is puzzling.
    • #push [[agora chapter]] next steps
      • read George's email.
        • end of week as deadline for all, then we need to....
          • work on updated abstracts and...
          • start on the Markdown port.
  • this is very much like the motivation for [[push]] in the [[agora]], or at least goes very well with it
  • [[push]] [[agora]]
    • fix toggle switch for [[auto pull]]
    • implement [[auto pull]]
    • implement [[auto push]]
    • client side pulling
      • done for: mastodon, twitter, wikipedia
      • need to test general URL pulling, see how many sites allow iframes
    • improve [[agora graphs]]
      • I like what logseq does: show link direction as particles. push/pull could be different particles. hmm. particle diagrams. check out [[feynman]] for inspiration?
      • could get inspiration from some diagrams in [[a rosetta stone]]
    • [[wikilinks everywhere]] -> [[agora ext]]
      • I really want to move wikilinking to on-demand (push button/ctrl-shift-l) or cronjob-like behaviour but right now it just wikilinks everything every time you click, and some sites break
        • this is already better after a quick PR to linkify on click instead of mouse movement
        • twitter still sort of breaks though
        • [[vera]] is on this though
    • [[agora server]]
    • parse agora protocol
      • recognize (match) and style differently
  • [[push]] [[agora]]
    • fix toggle switch for [[auto pull]]
    • implement [[auto pull]]
    • implement [[auto push]]
    • client side pulling
      • done for: mastodon, twitter, wikipedia
      • need to test general URL pulling, see how many sites allow iframes
    • improve [[agora graphs]]
      • I like what logseq does: show link direction as particles. push/pull could be different particles. hmm. particle diagrams. check out [[feynman]] for inspiration?
      • could get inspiration from some diagrams in [[a rosetta stone]]
    • [[wikilinks everywhere]] -> [[agora ext]]
      • I really want to move wikilinking to on-demand (push button/ctrl-shift-l) or cronjob-like behaviour but right now it just wikilinks everything every time you click, and some sites break
        • this is already better after a quick PR to linkify on click instead of mouse movement
        • twitter still sort of breaks though
        • [[vera]] is on this though
    • [[agora server]]
    • parse agora protocol
      • recognize (match) and style differently
  • [[push]] [[agora]]
    • fix toggle switch for [[auto pull]]
    • implement [[auto pull]]
    • implement [[auto push]]
    • client side pulling
      • done for: mastodon, twitter, wikipedia
      • need to test general URL pulling, see how many sites allow iframes
    • improve [[agora graphs]]
      • I like what logseq does: show link direction as particles. push/pull could be different particles. hmm. particle diagrams. check out [[feynman]] for inspiration?
      • could get inspiration from some diagrams in [[a rosetta stone]]
    • [[wikilinks everywhere]] -> [[agora ext]]
      • I really want to move wikilinking to on-demand (push button/ctrl-shift-l) or cronjob-like behaviour but right now it just wikilinks everything every time you click, and some sites break
        • this is already better after a quick PR to linkify on click instead of mouse movement
        • twitter still sort of breaks though
        • [[vera]] is on this though
    • [[agora server]]
    • parse agora protocol
      • recognize (match) and style differently
    Couldn't parse #push. See source for content.
    Couldn't parse #push. See source for content.
  • #push [[agora]]
    • finish [[agora chapter]]
      • may require rewriting in parts :) but it's alright, I think I have enough time thankfully
    • move to containers based setup
β₯… node [[agora-doc]] pulled by user
β₯… node [[agora-graph]] pulled by user
β₯… node [[agora-howto]] pulled by user

Agora Howto

β₯… node [[agora-platform]] pulled by user
β₯… node [[agora-protocol]] pulled by user

What follows is Agora Protocol in a nutshell: https://twitter.com/flancian/status/1437079533253976066 .

Self: flancia.org/go/agora-protocol

See also: flancia.org/agora (motivation and TLDR), flancia.org/go/agora (early stage implementation), flancia.org/go/agora-roadmap (roadmap)

By: [[D. W.]], [[Flancian]], your name here!

[[Meta, and a note to contributors]] 1

[[Background]] 1

[[Wikilinks]] 2

[[Backlinks]] 2

[[Block references]] 2

[[Multi-user experience]] 2

[[Proposal]] 2

[[Concepts]] 3

[[Multinodes, or constructive conflict handling]] 3

[[Other clients]] 3

[[Data format]] 3

[[Go links]] 4

[[Contexts]] 4

[[Open questions]] 4

[[Possible Applications]] 4

Meta, and a note to contributors

  • Agora is just a working code name; it is a recurrent label that one of the authors has been using as a placeholder for a set of concurrent, only occasionally convergent ideas. Please feel free to propose a different name, or indeed to ignore the name overall.
  • This document will probably make use of unresolved [[wikilinks]] both for the purpose of demonstrating the concept and labelling entities. Eventually this text is expected to move into a reference Agora, and such links will resolve.
  • I tried keeping Background to about one page and Proposal to about one page. Unsure if this is the right proportion/format at all. Open to any and all feedback :)

Background

The Agora is an annotation layer for the internet based on a loosely coupled socially maintained [[distributed knowledge graph]] based on [[wikilinks]] and back references.

Some conventions may be emerging in a new batch of personal knowledge management tools

1

, or amenable to them; for the duration of this document, we'll refer to these tools as Roam-like. These systems have caught on over more legacy apps such as Evernote, because associations can be created in a mesh or graph style between concepts and notes instead of relying on folders and more traditionally hierarchical organizational approaches.

This document seeks to explore common ground and propose a way towards a protocol for cross-tool distributed collaboration including aspects like interop, federation, etc.

Wikilinks

The ubiquity of [[wikilinks]] is a notable innovation over the previous batch of Personal Knowledge Management tools. The [[wikilink]] convention is in wide use not only in wikis proper, but also in all Roam-likes.

At their core, they allow a user to quickly make a relative "wiki-style link" between a note in one place and a note or concept in another. Typically the user will employ a wiki-like convention to begin-- for instance, typing "[["-- at which point an increasingly constrained set of options will be offered in real time as the user continues typing, against a set of notes or concepts that have already been created in their personal knowledge graph.

As of the time of writing, all Roam-likes support [[wikilinks]] with optimistic resolution

2

; following a non-existent [[wikilink]] triggers a new note creation. This encourages link-driven writing and enables users to easily create stub pointers to entries to be filled in later.

Backlinks

Backlinks are core to the note taking and navigation experience in Roam-likes. They are the main innovation over most common Wiki tools previously in widespread use.

Backlinks are usually implemented as a list of incoming edges to the currently focused node.

Block references

Block references are critical to some, but not all, of Roam-likes; notably Roam Research and Athens Research support them. Block references are an instance of block-level transclusion.

Obsidian, Foam and other players either don't support References at all or support only limited forms (e.g. Obsidian can transclude sections only). It is unclear whether this should be a core feature of a protocol aiming to federate between tools.

Multi-user experience

At the time of writing Roam is the only tool with an established multi-user (a.k.a. "multiplayer") experience being developed.

Proposal

We propose to develop Agora, a protocol that

  1. Enables interop between Roam-likes and the rest of the participating internet, in particular the [[fediverse]] and the [[semantic web]].
  2. Offers a common interface for tools targeting Roam-like databases as knowledge graph backends.

Concepts

An Agora hostsa collection of interlinked gardens # 3. Each garden is an instance of a personal knowledge graph such as that produced by any Roam-like targeting a database. For the purpose of this document, assume that distinct users A, B and C all publish their digital gardens in an Agora.

Multinodes, or constructive conflict handling

Whereas in a Garden each node id is expected to be unique, in an Agora conflicts are desired and enable multinoding # 4_._Assume users A and B have nodes in their gardens with a given id, for example Stoa.

Multinoding results in the following behaviour:

  • When a user of the Agora (not necessarily A or B) visits a [[Stoa]], both A and B's nodes will resolve, and be shown one after the other.
  • When user C creates a new node in [[Stoa]], they are made aware of A and B's node (it is shown as related context).

Other clients

One of the most common uses of tools such as Hypothesis is for users to create annotations which are then imported into a wiki-note application for other purposes.

An obvious affordance would be for folks to directly reference their or other's knowledge graphs in their own annotation bodies. Both the Hypothesis app and others in this category are often using a flavor of markdown as the editor syntax, so the applications are already conceptually similar to each other.

Annotation tools could connect to an Agora of the user's choosing so that while an annotation was being created, a direct reference to a concept node could be created inline. The editor would need to be able to query the remote knowledge graph in real time such that candidate concepts could be presented as the user types, just like in a native client. One could imagine this kind of capability becoming social, if some knowledge graphs were exposed publicly and one could query across them and choose amongst them. In this way, if the Hypothesis note were to be exported to another systemβ€” including the remote knowledge app itselfβ€” the direct reference to the graph would automatically work.

Data format

Most Roam-likes, with the notable exception of Roam, store their data as plain Markdown files. This makes their databases amenable to being hosted in common version control systems.

With the exception of block references, Roam notes can be exported to this format in a lossless way.

The Agora v0.5 reference implementation makes use of this data format and is based on git subtrees. This makes it so that each participating user can host their gardens independently, and rely on the Agora exclusively for Agora-enabled flows (such as multinoding and publishing).

Contexts

To be written. See [[distributed knowledge graph]].

Open questions

  • Should [[wikilink]] resolution collapse or maintain plurals and other common variations? Same for go links.

Possible Applications

Go links

Note [[go links]] and [[wikilinks]] have synergies. Go links can be seen as HTTP 302 as a service; they can provide both simple social bookmarking (letting users easily claim "URL space") and be seen as a social knowledge graph client. Making clients resolve also resolve [[wikilinks]] to [[go links]] as published by participating domains (perhaps those in a list controlled by the user, or those of their "friends") would allow users to crowdsource interesting targets.

Wikilinks everywhere

See: anagora.org/go/wikilinks-everywhere.

[[1]]Roam Research; Athens Research; Obsidian; Foam; Notion.

[[2]] Or as Ward Cunningham said: "When you reach the edge of your knowledge, create a new Wiki Page" (h/t Gyuri Lajos for the quotation).

[[3]] The term comes from digital garden, as exposed in https://joelhooks.com/digital-garden.

[[4]] Noding is borrowed from everything2.com, which successfully explored a similar setup.

β₯… node [[an-agora]] pulled by user

An Agora

πŸ“– stoas
β₯± context
β₯… related node [[agora repository]]
β₯… related node [[agora2]]
β₯… related node [[roam2agora]]
β₯… related node [[agora faq]]
β₯… related node [[anagora]]
β₯… related node [[connecting to the agora]]
β₯… related node [[anagora coop]]
β₯… related node [[towards the agora]]
β₯… related node [[3 agora]]
β₯… related node [[a view of the agora at a node is a comonad]]
β₯… related node [[agora 0 5 1]]
β₯… related node [[agora 2022]]
β₯… related node [[agora 3]]
β₯… related node [[agora abstract]]
β₯… related node [[agora action]]
β₯… related node [[agora actions]]
β₯… related node [[agora activitypub integration]]
β₯… related node [[agora algorithm]]
β₯… related node [[agora architecture]]
β₯… related node [[agora bootstrap]]
β₯… related node [[agora bot bugs]]
β₯… related node [[agora bot matrix]]
β₯… related node [[agora bot]]
β₯… related node [[agora bridge api]]
β₯… related node [[agora bridge js]]
β₯… related node [[agora bridge]]
β₯… related node [[agora channels]]
β₯… related node [[agora chapter 2]]
β₯… related node [[agora chapter appendix]]
β₯… related node [[agora chapter final]]
β₯… related node [[agora chapter unlinked]]
β₯… related node [[agora chapter]]
β₯… related node [[agora chat]]
β₯… related node [[agora cli]]
β₯… related node [[agora client]]
β₯… related node [[agora clients]]
β₯… related node [[agora code]]
β₯… related node [[agora comments]]
β₯… related node [[agora commons]]
β₯… related node [[agora contract]]
β₯… related node [[agora convention]]
β₯… related node [[agora copyright]]
β₯… related node [[agora ctzn]]
β₯… related node [[agora dashboard]]
β₯… related node [[agora design]]
β₯… related node [[agora development]]
β₯… related node [[agora diagram]]
β₯… related node [[agora diagrams]]
β₯… related node [[agora discord]]
β₯… related node [[agora discus]]
β₯… related node [[agora discuss]]
β₯… related node [[agora doc]]
β₯… related node [[agora docs import]]
β₯… related node [[agora editor]]
β₯… related node [[agora editors]]
β₯… related node [[agora elinor ostrom]]
β₯… related node [[agora embed]]
β₯… related node [[agora es]]
β₯… related node [[agora exchange format]]
β₯… related node [[agora ext]]
β₯… related node [[agora faqs]]
β₯… related node [[agora feature requests]]
β₯… related node [[agora fediverse integration]]
β₯… related node [[agora feeds]]
β₯… related node [[agora for ea]]
β₯… related node [[agora forum]]
β₯… related node [[agora fuzzy matching]]
β₯… related node [[agora fw]]
β₯… related node [[agora go links integration]]
β₯… related node [[agora graph]]
β₯… related node [[agora graphs]]
β₯… related node [[agora help]]
β₯… related node [[agora hn]]
β₯… related node [[agora howto]]
β₯… related node [[agora hub]]
β₯… related node [[agora hypothesis integration]]
β₯… related node [[agora hypothesis]]
β₯… related node [[agora install]]
β₯… related node [[agora instances]]
β₯… related node [[agora integration]]
β₯… related node [[agora js]]
β₯… related node [[agora like]]
β₯… related node [[agora links]]
β₯… related node [[agora mastodon bot]]
β₯… related node [[agora mastodon integration]]
β₯… related node [[agora matrix bot]]
β₯… related node [[agora mediawiki integration]]
β₯… related node [[agora meet]]
β₯… related node [[agora music]]
β₯… related node [[agora nodes]]
β₯… related node [[agora of flancia]]
β₯… related node [[agora open questions]]
β₯… related node [[agora osm]]
β₯… related node [[agora outage]]
β₯… related node [[agora paper]]
β₯… related node [[agora participation]]
β₯… related node [[agora pkg book chapter]]
β₯… related node [[agora pkg book]]
β₯… related node [[agora pkg chapter]]
β₯… related node [[agora pkm chapter]]
β₯… related node [[agora pkmchat]]
β₯… related node [[agora plan]]
β₯… related node [[agora playlist edit]]
β₯… related node [[agora playlist]]
β₯… related node [[agora polls]]
β₯… related node [[agora project]]
β₯… related node [[agora promnesia]]
β₯… related node [[agora protocol]]
β₯… related node [[agora prs]]
β₯… related node [[agora publishing]]
β₯… related node [[agora push]]
β₯… related node [[agora ranking]]
β₯… related node [[agora reader]]
β₯… related node [[agora reading club]]
β₯… related node [[agora recipe]]
β₯… related node [[agora recipes]]
β₯… related node [[agora resources]]
β₯… related node [[agora rfc]]
β₯… related node [[agora rfcs]]
β₯… related node [[agora roadmap 2020]]
β₯… related node [[agora seach]]
β₯… related node [[agora search]]
β₯… related node [[agora server]]
β₯… related node [[agora service]]
β₯… related node [[agora settings]]
β₯… related node [[agora setup]]
β₯… related node [[agora shaped]]
β₯… related node [[agora signup]]
β₯… related node [[agora slides]]
β₯… related node [[agora social bridge]]
β₯… related node [[agora social media integration]]
β₯… related node [[agora space]]
β₯… related node [[agora speed]]
β₯… related node [[agora sync]]
β₯… related node [[agora talk 2021 06 04]]
β₯… related node [[agora talk]]
β₯… related node [[agora talks]]
β₯… related node [[agora tree example]]
β₯… related node [[agora trees]]
β₯… related node [[agora twitter bug]]
β₯… related node [[agora twitter integration]]
β₯… related node [[agora ui]]
β₯… related node [[agora v0 5]]
β₯… related node [[agora v1]]
β₯… related node [[agora version]]
β₯… related node [[agora versioning]]
β₯… related node [[agora vscode]]
β₯… related node [[agora walkthrough]]
β₯… related node [[agora wiki]]
β₯… related node [[agora yaml]]
β₯… related node [[agora youtube integration]]
β₯… related node [[agora4g]]
β₯… related node [[agorabot]]
β₯… related node [[agorai]]
β₯… related node [[agoras]]
β₯… related node [[an agora]]
β₯… related node [[an open letter to an agora]]
β₯… related node [[an open letter to the agora]]
β₯… related node [[any agora]]
β₯… related node [[at json agora]]
β₯… related node [[building an agora]]
β₯… related node [[editar el agora]]
β₯… related node [[en flancia hay un agora]]
β₯… related node [[entities can be looked up in an agora]]
β₯… related node [[features of the agora]]
β₯… related node [[flanciagora]]
β₯… related node [[fork the agora]]
β₯… related node [[historical agora]]
β₯… related node [[i could node in the agora all day and all night]]
β₯… related node [[if i had the means i d build an agora]]
β₯… related node [[in flancia there is an agora]]
β₯… related node [[infragora]]
β₯… related node [[it was in antiflancia that i saw the agora]]
β₯… related node [[join the agora]]
β₯… related node [[twitter agora bot]]
β₯… related node [[known agoras]]
β₯… related node [[laiki agora]]
β₯… related node [[matrix agora]]
β₯… related node [[onboarding to the agora]]
β₯… related node [[open agora questions]]
β₯… related node [[open letter to the agora]]
β₯… related node [[open letters to the agora]]
β₯… related node [[other agoras]]
β₯… related node [[ox agora]]
β₯… related node [[podagora]]
β₯… related node [[promnesia agora]]
β₯… related node [[publish agora el]]
β₯… related node [[reference agora]]
β₯… related node [[roaman agora]]
β₯… related node [[run your own agora]]
β₯… related node [[sensagora]]
β₯… related node [[shamanic agora]]
β₯… related node [[smart agora]]
β₯… related node [[the agora already existed]]
β₯… related node [[the agora as a social knowledge graph]]
β₯… related node [[the agora is a garden of forking paths]]
β₯… related node [[the agora is a liminal entity]]
β₯… related node [[the agora is a markdown convention]]
β₯… related node [[the agora is a markdown extension]]
β₯… related node [[the agora is a markup convention]]
β₯… related node [[the agora is a platform for studying convergence]]
β₯… related node [[the agora is a social knowledge graph]]
β₯… related node [[the agora is a social network built by the people for the people]]
β₯… related node [[the agora is a technology]]
β₯… related node [[the agora is a twitter app]]
β₯… related node [[the agora is an old kind of social network]]
β₯… related node [[the agora or building bridges]]
β₯… related node [[the agora]]
β₯… related node [[the agora a knowledge commons]]
β₯… related node [[things to do after agora chapter]]
β₯… related node [[this agora]]
β₯… related node [[tools of the agora]]
β₯… related node [[towards an agora]]
β₯… related node [[twitter agora integration]]
β₯… related node [[twitter could be an agora]]
β₯… related node [[using the agora]]
β₯… related node [[when the agora just works]]
β₯… related node [[you can run an agora in your laptop]]
β₯… related node [[agora node aliasing]]
β₯… related node [[agora user perspective]]
β₯… related node [[benedictine agora]]
β₯… related node [[indieweb agora]]
β₯… related node [[betula_in_agora]]
β₯… related node [[interwiki_for_agora]]
β₯… related node [[automatic commonplace to agora]]
β₯… related node [[comparing fedwiki and agora]]
β₯… related node [[content moderation in the agora]]
β₯… related node [[how would you link indieweb and agora]]
β₯… related node [[the electronic agora]]
β₯… related node [[what are the similarities and differences between agora and fedwiki]]
β₯… related node [[what do i think about the agora]]
β₯… related node [[20200721212226 anaxagoras]]
β₯… related node [[20200721224050 protagoras]]
β₯… related node [[agora todo]]
β₯… related node [[comparing zettelkasten and agora]]
β₯… related node [[fedwiki to agora markdown converter]]
β₯… related node [[agora containers]]
β₯… related node [[agora conventions]]
β₯… related node [[agora ctzn docs]]
β₯… related node [[agora ext feature ideas]]
β₯… related node [[agora git mapping]]
β₯… related node [[agora governance system]]
β₯… related node [[agora governance]]
β₯… related node [[agora groups]]
β₯… related node [[agora interlay graph]]
β₯… related node [[agora interlay howto]]
β₯… related node [[agora issues]]
β₯… related node [[agora obsidian plugin]]
β₯… related node [[agora proposal 1]]
β₯… related node [[agora proposal platform]]
β₯… related node [[agora proposal]]
β₯… related node [[agora proposals]]
β₯… related node [[agora server build docs]]
β₯… related node [[agorans]]
β₯… related node [[integration of the agora]]
β₯… related node [[wtf is the agora]]
β₯… related node [[run an agora]]
β₯… related node [[agora 2023]]
β₯… related node [[agora bot test]]
β₯… related node [[agora digital garden]]
β₯… related node [[agora platform]]
β₯… related node [[anagora bot treat]]
β₯… related node [[anagora bot]]
β₯… related node [[anagora vision]]
β₯… related node [[many agoras]]
β₯… related node [[sorry anagora bot]]
β₯… related node [[sorry anagora]]
β₯… related node [[thank you anagora bot]]