πŸ“• Node [[do]]
↳ πŸ““ Resource @anonymous@doc.anagora.org/do
πŸ“„ do.md by @anonymous@doc.anagora.org ✍️

I think I’m going to start using the stoa in [[do]] to keep my top level todo list — or at least my [[inbox]]. Unfortunately [[do]] the node is overloaded, and this is very convenient as I can just edit it in any browser :) Feel free to do the same if it helps! (I’ll likely soon add one doc per user in the Agora.)

[[flancian]]

  • #push [[done]]
    • I don’t finish a lot of things, but when I do, sometimes I push them to [[done]] :)
  • #push [[agora plan]]
  • code [[agora server]] / default UI
    • [[recursive]] experiment
      • I shipped this and I’m happy :) It did away with a lot of bugs!
  • code [[agora bridge]] / bots
  • code [[auto pull]]
    • perhaps base it on inline transclusion like wikipedia/url pulls
      • update (2023): yes, this is the default approach to all integrations nowadays.
    • this is partially implemented now, finally
      • I think I added this as ‘node X pulled by Agora’
        • I don’t remember where the code is :) I think there are currently two different paths that pull things?
        • It should be easy to find though.
  • code [[auto push]]
    • [[foo]]
      • foo gets this line auto pushed because it’s a wikilinked parent of a block (as defined by indentation or user set syntax)
      • this is still not done surprisingly! I’m not sure it’s actually blocking on getting a proper [[agora protocol]] [[ast]]; we could extend the current [[lxml]]-based hack.
      • honestly parsing the DOM of a site sounds like an OK approach? that is, when it doesn’t include microformats, etc.
  • see also: all pulled and my [[journals]].

Loading pushes...

Rendering context...

πŸ“• Node [[did]] pulled by user
πŸ“• Node [[done]] pulled by user
πŸ“• Node [[later]] pulled by user
πŸ“• Node [[next action]] pulled by user
πŸ“• Node [[now]] pulled by user
πŸ“• Node [[plan]] pulled by user
πŸ“• Node [[todo]] pulled by user