📕 subnode [[@s5bug/agora]] in 📚 node [[agora]]
📓 garden/s5bug/agora.md by @s5bug

Agora
📄 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
      • [[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.)
📄 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
      • [[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.)
📄 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
      • [[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.)
📄 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]]
      • 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.
📄 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]]
      • 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.
📄 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]]
      • 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.
📄 pushed from garden/flancian/journal/2023-01-17.md by @flancian
📄 pushed from garden/flancian/journal/2023-07-31.md by @flancian
📄 pushed from garden/flancian/journal/2024-02-01.md by @flancian
📄 pushed from garden/flancian/agora protocol.md by @flancian
📄 pushed from garden/flancian/agora protocol.md by @flancian
📄 pushed from garden/flancian/beyond knowledge graphs.md by @flancian
  • this is very much like the motivation for [[push]] in the [[agora]], or at least goes very well with it
📄 pushed from garden/flancian/context.md by @flancian
📄 pushed from garden/flancian/do.md by @flancian
  • [[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
📄 pushed from garden/flancian/do.md by @flancian
  • [[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
📄 pushed from garden/flancian/do.md by @flancian
  • [[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
📄 pushed from garden/flancian/flancia 2023.md by @flancian
📄 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
📄 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
⥱ context
To see links, go up to full node [[agora]].