📚 node [[tasks]]
- #pull #do #todo [[next action]] #later
tasks
📄
pushed from garden/flancian/journal/2021-11-07.md by @flancian
⥅ node [[agora-plan]] pulled by user
Agora Plan
Introduction
The [[Agora]] is a project with a large [[scope]], so it takes a minute to explain what it's all about, and what the vision this plan tries to advance is.
If you'd like a quick introduction to the Agora as of mid 2021, please check out [[go/agora-slides]].
You can also refer to [[go/agora]], that is the documentation in the [[root repository]] currently hosted on [[github]].
What this node is for
This node is used as a project planning page for the [[Agora]] implementation you're likely reading this in now: https://anagora.org .
As you might know by now, an Agora is a beast with multiple legs:
- A [[knowledge graph]]. This is the heart of the [[Agora]]. It is kept in the [[go/agora]] repo, and includes pointers to other repositories.
- A web server and associated client code, which the [[flancia collective]] runs on https://anagora.org . It is kept in the [[go/agora-server]] repo.
- A set of bridges to connect other platforms to the [[agora]], and the Agora to to [[other platforms]]. These are kept in the [[go/agora-bridge]] repository.
This node might deal with development of any and all of them. We will try to list past major developments below, but this node will try to also be [[future focused]].
Next
-
[[agora]]
- new users are trickling into the community, although the signup process is still manual; need to ship the repo api in [[agora bridge]] to improve the sinup flow.
- considering [[logseq]] and [[tiddlywiki]] as recommended web clients.
-
[[agora server]]
- looking better than six months ago, but needs work
-
[[better parsing]]
-
blocks [[auto push]]?
- perhaps not for inline (same line) pushes
-
blocks [[auto push]]?
-
[[agora bridge]]
- need to have [[agora twitter bot]] call out to [[repo api]] to store nodes per-user
- need to have [[agora mastodon bot]] automatically respond to toots with [[patterns]] from followers
-
[[patterns everywhere]]
- new name for [[wikilinks everywhere]], [[vera]] leading
-
[[flancia]]
- need to work more on [[building bridges]]
-
[[flancia collective]]
- need to explore [[governance]]
- [[vera]] started [[flancia social impact]]
Previously
-
On [[2021-11-06]]:
- Lots have happened. I gave up trying to maintain this for a while, instead using my journals and a transitive subset of the [[Agora]] to document the development process.
- See [[flancia collective]], [[agora discuss]], [[journals]].
-
On [[2021-01-30]]
- onboarded [[enki]]
-
[[nodes]] are now color coded:
- [[dark violet]] for the [[primary node]], that is, any subnodes that match the wikilink you're at most precisely.
- [[dark grey]] for [[pulled]] and [[pushed]] nodes and subnodes.
-
On [[2020-01-02]] I implemented [[jump]]
- I said: "I'll implement the action and a 'jump'/ dialog always available in the Agora, perhaps replacing search in the [[toolbar]]."
- Done!
- Q: is 'go to' better than jump? I don't think so, and it could be confusing due to go links. But unsure.
- On [[2020-01-01]] I fixed node titles.
- On [[2020-12-29]] I pushed a quick patch that upranks all my subnodes, as some top subnodes in relatively popular nodes had formatting issues / were distracting. I intend this to be temporary; better ranking and formatting fixes are coming.
- On [[2020-12-27]] I released [[agora 0.5.6]] with [[pull]] support, better db code, caching... quite a bit :)
- On [[2020-12-20]] I worked [[agora 0.5.5]], which adds simple [[hypothes.is]] integration.
-
On [[2020-12-04]] I released [[agora 0.5.4]], with some improvements:
- New data model (digital gardens are not subtree'd in the main [[agora repository]] anymore, stay wholly independent)
- Index page is now just another node, subnodes can be contributed by users.
- On [[2020-11-29]] I integrated the first community contribution ever.
- On [[2020-11-27]] I fixed some bugs, like wikilinks with periods on their names not working.
-
On [[2020-11-22]] implemented count of subnodes in user pages.
- Added some amount of go links support: anagora.org/go/go now works :), points to the URL with [[go]] in anagora.org/node/go.
- On [[2020-11-17]] implemented [[latest]].
- On [[2020-11-16]] I implemented [[agora fuzzy matching]] and full text search, adopted a div based layout, improved the CSS, improved user pages.
- On [[2020-11-15]] I implemented dark mode (press on 'theme' on the top right corner to switch dark <-> light).
- On [[2020-11-14]] I released [[agora 0.5.1]].
Signups
- [[pen-coded]]: https://github.com/KGBicheno/KGB_Agora
- [[luciana]]: https://github.com/malfattti/garden
- [[arghzero]]
- [[dr_kvj]]: https://github.com/drkvj/agora
- [[jonathan-the-utopian]]
- [[enkiv2]]: http://www.lord-enki.net/medium-backup/
-
what about all of the ones licensed appropriately listed in [[kasper zutterman]]'s [[second brain]] list? https://github.com/KasperZutterman/Second-Brain
- Discussing with [[armengolaltayo]]
- See also [[digital gardeners]]
-
[[iplumb3r]]
- This seems to be in [[topincs]] format, investigate.
- [[houshuang]]
- [[joelchan86]]
- [[tilda]]
- [[binnyva]]
- [[jakeisnt]]
-
TomCassidy
- It's a public roam graph: https://roamresearch.com/#/app/Learn2020zettelkasten
-
[[metasj]] https://meta.wikimedia.org/wiki/User:Sj/!
- First user actually using a wiki!
Integrations
- [[agora-go-links-integration]]
- [[agora twitter integration]]
- [[agora-youtube-integration]]
- [[agora hypothesis integration]]
- [[roam2agora]]
- [[agora vscode]]
- [[wikilinks everywhere]]
Next
-
all http mentions should be auto linked, not only some: https://twitter.com/notverapetrova/status/1346258737204400128
- Worked around this, but I should probably send an upstream PR to [[bleach]]
- try rendering notes with [[marko]], see if it's a bit more forgiving with list indentation and other kinks that seem common.
-
add support for org mode gardens
- signup by [[jakeisnt]] is blocked on this: https://github.com/jakeisnt/wiki
- signup by [[karlicoss]] is blocked on this: https://github.com/karlicoss/exobrain.git
- this might be enough to unlock basic [[logseq]] support?
- [[orgparse]] might be useful
- [[pandoc]] supports org
- I should make node [[0.5.6]] work
- graph the whole Agora -- sounds fun!
- Implement pull and push.
-
Make more links default to node instead of subnode.
- For example those in latest, those in user pages.
- Might require 'upranking'.
- set up [[agora]] hot spare in [[dorcas]], this is an experiment but I already find it very useful so I don't want to not have it available for a while if there's a server failure
- add monitoring -- [[munin]] or something more modern? [[prometheus]]?
- Implement /node/foo/selector as more resilient/uniform alternative to /subnode.
-
Implement user upranking/pinning.
- Perhaps nodes visited from a user scope uprank subnodes by that user?
- https://twitter.com/s5bug/status/1334686375275163652 ?s=09
- Provide a link (GET) for the search for '[ ]', useful for [[do]].
- Add better backlinks, showing some context.
- Make the site header be marked as an actual header (div with a class, etc.); Google seems to think it's part of the site text (it's showing up in results).
- Fix markdown list formatting issue with different tab widths.
- add footer.
- Implement preview-on-hover?
- Implement "around the Agora".
- add /latest or some other chronological view
- User profiles: perhaps just note [[flancian]] as written by user [[flancian]]? Unsure.
- Make the index be just another note [[ding-levery]].
- Improve backlinks: show snippets as well as just the link.
- Improve pull loop to also support arbitrary hooks, like that needed to implement [[agora go links integration]].
-
Multi user improvements:
- Better sorting (right now all my notes show up at the top, doesn't make sense).
- Ability to "zoom into" a user, to navigate just their garden for a while.
- Perhaps ability to "uprank" users, pinning their notes to the top of any sorting order.
- Perhaps sort+uprank can be integrated?
- usernames could have a 'pin' emoji that upranks all their posts?
- Implement search (full text).
-
Add support for media serving (useful for pictures of [[ocell]]).
- assets/foo end up at node/assets/foo; just adding a handler for node/assets/ seems like it could be enough.
- It would conflict with a node named 'assets' though, so perhaps it's not ideal.
- Perhaps it'd be better to just serve images/media as subnodes?
- Add monitoring/alerting.
Some day:
- When you update a node on a [[person]], said person gets a notification (they can opt out).
- Support [[Roam]], [[Athens]], [[org-roam]] digital gardens.
-
Twitter integration -> [[agora twitter integration]]
- Ask [[ding levery]].
-
Automatic [[actions]] -> [[agora action]]s -> [[agora action]]
- [[tweet]] block tweets the block (exactly once, etc.).
-
[[go links]] integration -> [[agora go links integration]]
- If the first block of [[foo]] is a URL, anagora.org/go/foo just redirect there.
- Could also work as an action: [[go]] target URL.
Feature requests
- [[pull]] [[feature requests]]
History
- fix bug: backlinks should be shown even in yet non-existent nodes, such as [[deceased]].
- Clean up stale journal pages which don't follow [[iso 8601]].
- Add config.py file with things such as paths.
-
Add user handler: /u
- /u/flancian -> all nodes by flancian
- /node/flancia/u/flancian -> flancia by flancian
- Also added @flancian. Shorter is better, and it's a common convention.
- perhaps /g/ for groups later? or /s/ for stoa.
-
Add 'link to this note'.
- Now called subnode.
- Subnode rendering is ready, just need to add links.
- Perhaps I need to fix subnode paths; right now they are the actual filename. It'd be better if there was at least possible to specify the filename base (no extension) and have the right file be resolve, a la nodes.
-
add some search support -- a simple textbox + GET?
- Probably want to use [[flask-wtf]] for this: https://hackersandslackers.com/flask-wtforms-forms/
-
better css
- Add '[[dark mode]]' to the Agora, I like this kind of scheme: https://twitter.com/ablueaeshna/status/1323439284272222208 /photo/1
- added switching by button
- Make subnodes/notes look like notes instead of using clunky
<hr />
everywhere. Move to divs, etc.
- Improve the [[index]].
-
Implement [[agora fuzzy matching]].
- Done
- but backlinks don't work in some cases, like http://dev.anagora.org/node/abstract%20fairy .
- Probably not worth fixing that right now as it only triggers for nodes that are not canonical, perhaps better to just redirect to a canonical node.
- could help with disambiguation and acronym expansion
⥅ node [[chores]] pulled by user
chores
- Things that are [[maintenance]] and can't be automated.
- Pushing entropy back; [[cleaning]], although cleaning can be fun.
⥅ node [[do]] pulled by user
-
a [[list]].
- [[irregular]].
- [[meditate]] now.
- process inbox (pushes to this node).
-
configure [[probing]]
- I never get to this, can you tell it reminds me of work? :)
- I need to just set a pomodoro and do this, but I feel like running the agora at low slo is OK. It's supposed to rely on distribution later on for reliability gains.
- Doesn't really apply as an argument to [[moa]] though -- although for [[moa]] we have [[sentry]] set up so that seems reasonable.
-
[[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
-
[[push]] [[agora interlace]]
-
[[agora social media integration]]
- write [[agora bot]] for [[mastodon]]
-
write [[agora bot]] for [[twitter]]
-
fix auth
- restore context
- this could be a great workaround for the worse of the re-replying behaviour, and probably will be needed even if I want to support zero state best effort
-
fix deduping
- need to do this again
-
fix auth
-
test [[vera]]'s code for pulling tweets and toots
- only pulled some for some reason
- figure out what's up, try again and get the context back
-
[[agora bot]]
- fix twitter so it doesn't keep re-replying
-
the API doesn't feel great, I wonder if I'm missing something
- I thought I'd done this but it's still failing in some cases, [[s5bug]] gave me a test case, I think I put it in [[agora twitter bug]]
- refactor mastodon<->twitter so they share code? I don't want to implement everything twice, and I certainly don't want the mastodon version to suffer because I'm addicted to twitter (great people there as well, and there are more of them)
-
[[push]] [[agora bridge api]]
-
build/release [[agora bridge api]] for the storing posts in the agora.
- we want to create a git repository for each calling users, which the users could then [[claim]].
-
could be flask, included in [[agora bridge]] repo, copy/paste from [[agora server]] to begin with?
- nope, it is typescript thanks to [[vera]], looking forward to set this up :)
- but hopefully they can just communicate through yaml? or perhaps set up and write to sqlite to begin with
-
thought of consolidating everything into [[agora server]], but it feels cleaner to have writers and readers split. should scale better; if the write path goes down, the agora keeps serving just fine without having to do anything special.
- probably keeps it simple to run a read only agora (mirror).
- yes, going with [[read]] ([[agora server]]) and [[write]] ([[agora bridge]]) apis
- request new git integrations (e.g. mount git repo X in path Y)
- accept other inputs? like perhaps subnodes, which could go into a managed repo.
- configure sources from social media (from agora bot)
- in general this unlocks better [[signup]]
-
build/release [[agora bridge api]] for the storing posts in the agora.
-
[[agora social media integration]]
-
[[push]] [[moa]]
- review [[go/moa/bugs]]
-
[[slay moloch]]
- [[chase moloch]]
-
[[write]]
- [[flancia]]
-
[[book]]
- choose [[top 5]] nodes to expand on
- edit https://flancia.org
- [[iremos juntos hasta el final de la noche]]
-
[[slaying moloch]]
- [[building bridges]]
-
[[finding isomorphisms]]
- measuring distance to an isomorphism? there must be a term for this
- [[node club]]
-
[[book]]
-
[[patterns]]
- [[after the pandemic]], or [[an open letter to the agora]], or [[an open letter to an open nation]]
-
[[on cringe]] / [[agora polls]]
- about explicit rational (mathematical) modelling of group dynamics through social media discourse
- is [[hack the planet]] cringe? should it be?
- why is it cringe to talk about virtue?
-
[[read]]
-
what [[will walker]] told me about
- link it here
- this is past due
-
what [[will walker]] told me about
-
[[push]] [[weekly]]
- run [[weekly review]]
- it turns out I do a run through [[do]] weekly at best as of late, so this is my weekly. I'd love to make it daily though. perhaps I could auto-pull [[do]] from the journal page? just the subnode for the 'active' user.
- promote [[do]] to nav item?
- we could also have 'this week', 'this month', 'this year' in the agora, have it rank top nodes in time scope, allow users to pull specific nodes from each view
-
an [[agora action]]
- I try to automate recurrent [[actions]] in the [[agora]]. This node is the root of my [[getting things done]] graph, which I try to use to model my [[intents]].
- [[daily]], I try to check here for pending [[work]] in all known sources of truth.
- [[weekly]], I try to run [[weekly review]] and [[garbage collect]]
- [[monthly]], I try to check the context in more specific actions/nodes and push relevant items here or to [[next action]]:
- what should I [[read]] next?
-
what should I [[write]]?
-
[[flancia]]
- [[book]]
- [[an open letter for an open society]] (this has many titles)
-
to [[a. p.]] asking for a recommendation
- hmm, I don't know what this means :) as in, I don't know who I meant by [[a. p.]]
-
[[flancia]]
-
[[unblock]] people who are waiting for me
- this is not atomic. how do I know who is waiting for me?
-
[[research]]
- [[federated wiki]]
- [[indieweb]]
-
[[ipfs]]
- [[ipld]]
- [[fission]]
- [[hypercore proto]]
- [[launchlet]]
-
[[urbit]]
-
[[rosano]]
- Rosano is in Urbit or did I just fat finger an indent?
-
[[rosano]]
-
[[support]]
- [[effective altruism]]
- [[flancia collective]]
- [[open source]]
- [[friends]]
- [[public utility]]
-
[[code]]
-
[[agora server]]
- add particles to [[agora search]]
- [[browse as]]
- parse [[agora protocol]] (see below)
-
[[wikilinks everywhere]] / [[agora ext]]
- could [[d3]] replace [[jquery]]? it would make it easy to also include a graph tool directly in the library. it's 200kb though.
- but we could just add [[force graph]], in general have the client side code from [[agora server]] be also there and potentially work in every agora/every place with wikilnks or links (pulling could be useful on every site)
-
a more flexible [[actions]] system
- what does this mean? :)
- write something better or remove on next collect
-
[[project snapshot]]
- model my digital existence as a sequence of computational snapshots
- what complexity class is this in generally?
- what is the [[zero]]? as in, the starting state.
- probably [[browser tabs]]
-
then more generally programs running, including optionally their context
- could make it easier to actually dedicate one workspace for every project -- the dream of [[richard francis burton]] IIRC?
-
[[agora server]]
- Please tell me what you think I should [[do]] next (or instead of the things I'm doing or planning to do) below in the Stoa, via social media, or via any of the channels listed in [[flancian]]. All feedback is welcome!
-
[[push]] [[done]]
- implement [[ack]]
- [[agora yaml]]
- [[agora plan]]
-
[[rdf]]
- [[graphs]]
- [[agora search]]
-
implemented support for [[obsidian attachments]] in [[agora server]]
- basic but it does the job (tm)
- many items in [[agora plan]]
⥅ node [[later]] pulled by user
later
-
a [[list]].
-
[[irregular]]
- Thoughts that come up while I was doing [[pomodoro]].
- [[slay moloch]]
- [[sorting pushes]]
-
[[pull arbitrary urls]]
- pull wikipedia works
- fix duplicate [[go links]] behaviour
- [[write]] [[on building bridges]]
- [[read]] [[category theory]]
- Write about [[excursion]].
-
[[onkyo volume]]
- ? meh
-
Write about [[music mouse]].
- Write a post about my [[virtual desktop setup]].
- [[pull]] means [[uprank]]
-
implement [[autopull]] and [[autopush]]
- check out [[gtoolkit]]
- [[javascript subnodes]]. Think about how they interact with functionality like [[auto pull]], which I disabled by default due to performance issues and would prefer to make into an async call.
- see [[js util]] by [[vera]]
- [[push]] [[plurals auto pull]]
-
equals better treatment for [[lists]]
- [[force directed graph]] must auto pull [[force directed graphs]]
- that is, auto pull plurals
- fixes a common search case now broken (as we only do [[exact match]] plus resolution of user-specified, so explicit, [[pulls]])
- auto pull makes 'or' behaviour of search trivially implementable
- auto pulls are [[action code]] that implements a [[morphism]]
- any search policy/ranking can be expressed as a composition of morphisms
- [[push]] [[vscode]] [[foam]]
-
[[push]] [[project snapshot]]
- [[clipboard sync]]
- [[tweets]]
- [[wayland]]
- install [[maubot]] and [[maya]]'s matrix voice messages transcription service
-
[[irregular]]
- [[push]] [[done]]
-
[[push]] [[done]]
- that is, pushing to the node [[done]], should: elide from source, clean up, collapse/zip
⥅ node [[next-action]] pulled by user
-
A [[tree]].
- The general concept comes from [[Getting Things Done]].
- #pull [[do]] [[next actions]] I play hard and loose with plurals and in general with [[equivalence classes]]
- May fall in a number of distinct categories :)
-
#push [[personal]]
- let go of [[fear]]
- practice [[fractal altruism]] and [[loving kindness]]
- follow a constructive and meaningful [[eightfold path]]
- #push [[flancia]]
-
#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]]
-
#push [[google]]]
- plan for [[2023]], communicate
- iterate on presentations
-
#push [[social coop]]
- read technical documentation as per the blocks pushed
- follow up on [[missed registrations]] and opening up invites with the community
📖 stoas
- public document at doc.anagora.org/tasks
- video call at meet.jit.si/tasks
⥱ context
⥅ related node [[2004 04 26 tasks pro 1 1]]
⥅ related node [[moa tasks]]
🔎 full text search for 'tasks'