📕 subnode [[@melanocarpa/agora]]
in 📚 node [[agora]]
img side { lapin 77 {My visual take}}
Agora is a ‘wiki like experimental social network and distributed knowledge graph’, so they said. I would say it's an aggregator of digital gardens and a community around it. Anagora is the first and biggest instance of it. [[Flancian]] was the one who created it and the software behind, but there were other good contributors. Thank you!
I'm part of it:. I also frequent the associated video conferences.
=> https://anagora.org/@melanocarpa | Melanocarpa in Agora => https://anagora.org/@bouncepaw-betula | My recent bookmarks in Agora
Agora makes a big emphasis on graphs and links. Their analogue of hyphae is called a node, nodes are generated from contents from multiple sites. There is also a cool notion of push/pull and go links!
//I was inspired by Agora's go links and implemented something very similar in [[Betula]].//
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. Furthermore, in 2023 proper support of [[Mycomarkup]] was added.
=> https://github.com/flancian/agora-server/commit/7783430aa33986186e9fd66ee858250b115e0d7e | Commit that adds Mycorrhiza support.
The Agorans also seem to be using [[git]]-based [[markdown]]-driven digital gardens mostly. It is the default choice for many, but luckily support for more formats was added. Mycorrhiza, for example, is supported! There is also [[Betula in Agora]].
= See also => Wiki => Social network => Digital garden => https://mycorrhiza.wiki/help/en/hypha => https://anagora.org/node => https://anagora.org/go => Flancia
You can't really talk about Agora without Flancia.
📄
pushed from garden/flancian/journal/2022-10-16.md by @flancian
-
#push [[agora]]
- #push [[agora writing]]
-
#push [[agora development]]
-
set up local dev environment in the train
- I like [[poetry]].
-
[[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
-
-> [[edit distance]]
- [[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.)
-
what's a quantum of better search? it's pretty bad right now; e.g. [[poetry install]] would not bring up [[install poetry]]
-
set up local dev environment in the train
📄
pushed from garden/flancian/journal/2022-10-16.md by @flancian
-
#push [[agora]]
- #push [[agora writing]]
-
#push [[agora development]]
-
set up local dev environment in the train
- I like [[poetry]].
-
[[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
-
-> [[edit distance]]
- [[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.)
-
what's a quantum of better search? it's pretty bad right now; e.g. [[poetry install]] would not bring up [[install poetry]]
-
set up local dev environment in the train
📄
pushed from garden/flancian/journal/2022-10-16.md by @flancian
-
#push [[agora]]
- #push [[agora writing]]
-
#push [[agora development]]
-
set up local dev environment in the train
- I like [[poetry]].
-
[[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
-
-> [[edit distance]]
- [[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.)
-
what's a quantum of better search? it's pretty bad right now; e.g. [[poetry install]] would not bring up [[install poetry]]
-
set up local dev environment in the train
📄
pushed from garden/flancian/journal/2022-12-12.md by @flancian
📄
pushed from garden/flancian/journal/2022-12-15.md by @flancian
📄
pushed from garden/flancian/journal/2023-01-11.md by @flancian
-
#push [[agora]]
-
#push [[agora development]]
- ship [[agora graph]] in some version?
-
[[dynamic subnodes]], sometimes also known as [[executable subnodes]]
- ship executable subnodes with allowlist?
- start on [[client side subnodes]], meaning [[javascript]] in gardens :)
- 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.
-
end of week as deadline for all, then we need to....
-
read George's email.
-
#push [[agora development]]
📄
pushed from garden/flancian/journal/2023-01-11.md by @flancian
-
#push [[agora]]
-
#push [[agora development]]
- ship [[agora graph]] in some version?
-
[[dynamic subnodes]], sometimes also known as [[executable subnodes]]
- ship executable subnodes with allowlist?
- start on [[client side subnodes]], meaning [[javascript]] in gardens :)
- 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.
-
end of week as deadline for all, then we need to....
-
read George's email.
-
#push [[agora development]]
📄
pushed from garden/flancian/journal/2023-01-11.md by @flancian
-
#push [[agora]]
-
#push [[agora development]]
- ship [[agora graph]] in some version?
-
[[dynamic subnodes]], sometimes also known as [[executable subnodes]]
- ship executable subnodes with allowlist?
- start on [[client side subnodes]], meaning [[javascript]] in gardens :)
- 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.
-
end of week as deadline for all, then we need to....
-
read George's email.
-
#push [[agora development]]
📄
pushed from garden/flancian/journal/2023-01-17.md by @flancian
📄
pushed from garden/flancian/journal/2023-07-31.md by @flancian
-
#push [[agora]]
- [[agora recipe]] for [[coop cloud is taking shape \o/
- https://link.agor.ai is live in basic form, tweaking upcoming
📄
pushed from garden/flancian/journal/2024-02-01.md by @flancian
-
#push [[agora]]
- [[agora nugget]]
- [[agora chapter]]
- [[an open letter to the agora]]
📄
pushed from garden/flancian/agora protocol.md by @flancian
-
#push [[agora]]
- an [[agora]] is a seed that wants to grow into a [[tree]], and from there into a [[distributed]] network.
- the [[seed]] of this agora is [[go/agora/git]], defining a [[commons]].
- [[flancia collective]] is the keeper of https://anagora.org.
- [[agora bridge]], [[agora server]] contain input (write) and output (read) code respectively.
📄
pushed from garden/flancian/agora protocol.md by @flancian
-
#push [[agora]]
- an [[agora]] is a seed that wants to grow into a [[tree]], and from there into a [[distributed]] network.
- the [[seed]] of this agora is [[go/agora/git]], defining a [[commons]].
- [[flancia collective]] is the keeper of https://anagora.org.
- [[agora bridge]], [[agora server]] contain input (write) and output (read) code respectively.
📄
pushed from garden/flancian/beyond knowledge graphs.md by @flancian
📄
pushed from garden/flancian/context.md by @flancian
-
#push [[agora]]
- An Agora is an engine for storing and retrieving [[mental contexts]].
- I make my mental contexts [[public by default]].
📄
pushed from garden/flancian/do.md by @flancian
-
[[push]] [[agora]]
- fix toggle switch for [[auto pull]]
- implement [[auto pull]]
-
implement [[auto push]]
- probably requires [[agora protocol parsing]] to make efficient/reasonable
-
client side pulling
- done for: mastodon, twitter, wikipedia
-
need to test general URL pulling, see how many sites allow iframes
- test with flancia.org
-
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
-
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
- [[agora server]]
-
parse agora protocol
- recognize (match) and style differently
📄
pushed from garden/flancian/do.md by @flancian
-
[[push]] [[agora]]
- fix toggle switch for [[auto pull]]
- implement [[auto pull]]
-
implement [[auto push]]
- probably requires [[agora protocol parsing]] to make efficient/reasonable
-
client side pulling
- done for: mastodon, twitter, wikipedia
-
need to test general URL pulling, see how many sites allow iframes
- test with flancia.org
-
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
-
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
- [[agora server]]
-
parse agora protocol
- recognize (match) and style differently
📄
pushed from garden/flancian/do.md by @flancian
-
[[push]] [[agora]]
- fix toggle switch for [[auto pull]]
- implement [[auto pull]]
-
implement [[auto push]]
- probably requires [[agora protocol parsing]] to make efficient/reasonable
-
client side pulling
- done for: mastodon, twitter, wikipedia
-
need to test general URL pulling, see how many sites allow iframes
- test with flancia.org
-
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
-
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
- [[agora server]]
-
parse agora protocol
- recognize (match) and style differently
📄
pushed from garden/flancian/flancia 2023.md by @flancian
-
#push [[agora]]
- [[Agora chapter]] delivered (finally!). It is what it is; I am glad it exists, for all its shortcomings.
- [[Agora development]] resumes (with more time to dedicate to it).
- [[agor.ai]] setup matures.
📄
pushed from garden/flancian/kindly.md by @flancian
-
Couldn't parse #push. See source for content.
📄
pushed from garden/flancian/knowledge federation.md by @flancian
-
Couldn't parse #push. See source for content.
📄
pushed from garden/flancian/next action.md by @flancian
-
#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
-
finish [[agora chapter]]
📄
pushed from garden/flancian/org mode.md by @flancian
📄
pushed from garden/flancian/tools for thinking.md by @flancian
📄
pushed from garden/flancian/tools for thinking.md by @flancian
📄
pushed from garden/flancian/tools for thinking.md by @flancian
📄
pushed from garden/flancian/tools for thinking.md by @flancian
📄
pushed from garden/flancian/tools for thinking.md by @flancian
📖 stoas
- public document at doc.anagora.org/agora
- video call at meet.jit.si/agora