📕 subnode [[@flancian/agora interlace]] in 📚 node [[agora-interlace]]
📄 pushed from garden/flancian/do.md by @flancian
  • [[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
      • 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]]
📖 stoas
⥱ context
To see links, go up to full node [[agora-interlace]].