flancian/garden
0
0
Fork 0
mirror of https://github.com/flancian/garden.git synced 2026-08-01 03:56:19 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
master
garden/do.md
T
flancian 421c064380 autopushed
2024-10-26 18:43:05 +02:00

9.5 KiB
Raw Permalink Blame History

  • 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.
      • -> As of 2024 moa is no longer supported, we shut it down when Musk closed down the API. I intend to bring it back, maybe for Fediverse <-> Bluesky -- but Ryan Barrett solved that with Bridgy Fed. So now I'm back to trying to make it work for Twitter again, even if it means paying, and running an instance for a closely knit community.
      • Hmm, I should still do this :)
      • I also need to do something similar for social coop ideally, so maybe I could try to solve both at a time.
    • push agora
      • implement auto pull
      • fix toggle switch for auto pull
        • this refers to /settings which has a toggle
        • hmm, maybe I should just embed the settings page in the burger. that also frees up /settings for the actual node about settings :)
        • I already have the burger menu working in a branch, which is nice
        • implement a toggle in the burger menu :)
        • implement auto push
      • ...I wrote at some point in time. Now it's implemented, both when you say #push example and when you use a colon.
      • So I'll think about it but maybe this is done-for-now.
        • client side pulling
          • done for: mastodon, twitter, wikipedia
          • need to test general URL pulling, see how many sites allow iframes
            • test with flancia.org
        • This is done :)
        • 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?
      • this is still a good idea honestly, and I always want to work on graphs - 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
    • 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
    • push moa
    • slay moloch
    • write - flancia
    • patterns
    • read
      • what will walker told me about
        • link it here
        • this is past due
    • 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
  • research
  • 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
Reference in New Issue View Git Blame Copy Permalink