πŸ“š node [[i should remember this]]
β₯… 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.
      • -> 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
        • 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]]
β₯… node [[later]] pulled by user

later

β₯… node [[plan]] pulled by user

So, yeah, I want to have that [Agora]. Flancia should have it, you know. It's a fictional place, like I said; this is a work of fiction. You got it? This is all hypothetical.

So MediaWiki could definitely be a serviceable Agora, right? People know how to use it. It's easy to set up; you can do a lot with "just a Wiki" because it's a framework, not only code but also conventions. A lot of things can be modeled with a Wiki. And it's so easy to set up -- I'm a geek. "In the old days, I could have set up a LAMP stack and a Wiki on top of it in 1h" is something that a less concerned with cringeness version of me could have uttered. I'm rusty but it shouldn't take long. And then what, you might say. Then you have an empty wiki that nobody uses.

Exactly! That's the beauty of it. It's there, it exists -- there is an Agora. People could use it -- they might not. But they could. So I posit that it exists as a place, here in the internet, where so much of our lives happen nowadays. We do spend time in other social networks -- a lot of people do, anyway. People could choose to spend their time in this other social network. Do you really need 2h of Facebook and Instagram in your lives?

Can't you do with 1h45m, really? You can't think about other stuff, the things that interest you, start a new hobby of sorts? Spend 15m here. You don't even have to post anything. Just think.

You are an entity that exists and is aware. You can think of anything, any time. You can decide to do stuff, just stuff in this place, whatever you want. The internet is this amazing place; never existed before. Our society will continue to be shaped by it; it must be; it is clearly powerful.

And we could do anything with it, if we put enough time on it.

What should we do next?

Next up: ?.

Plan

β₯… node [[read]] pulled by user

Read

https://twitter.com/flancian/status/1382742134802018304

β₯… node [[remember]] pulled by user
β₯… node [[todo]] pulled by user

Todo

After 2021 vacations

  • [v] August Timesheet
  • [v] MY TAX 2021
    • [v] fill in noikia
    • [v] US stocks:
      • [v] Collect all docs
      • submit it 2020 tax
    • PAY
  • [v] Review code Stefano Doumpoulakh (with Kyriakos)
  • [v] pay school
  • [v] cardano
  • solana
  • stake ETH
  • Astrobank review
    • [v] pay off accounting MarMay 2021
    • [v] Send reply
    • submit docs through "branch-it"
    • Follow up
  • [v] Talk to Lo3as
  • Talk to Babis
  • Prius polizza: https://mail.google.com/mail/u/0/#inbox/FMfcgzGljlnSpsgpFSKrzNrrDSxKBqCV
  • Cryptography:
    • week 2
    • week 3
    • week 4
    • week 5
    • week 6
  • [v] Google Play Dev account to be closed on Oct due to inactivity! OK, let it close

Mainly, things will just link here.

  • [recurring] Choose one idea of each category currently defined and transcribe it from the doc.
  • Move to post:
    • Write about the idea of the telo-republic. Perhaps change name to latin root.
  • About unicorns:
    • Add a note towards the end about how this is an optimistic look, and every step of the way can fail. Also, it can be used for evil.
    • Clarify a bit the Minsky mention for people who don't know who he is.
    • Consider removing "who am I and why does my opinion matter".
    • Consider paring down the ML examples section (supervised vs unsupervised).
  • A [[list]].
    • Of things I want/wanted to do.
    • To be strict, this is more of a [[graph]], but you get the idea ;)
    • See also: [[do]], for the alternate (maybe more regular) phrasing, and other nodes such as [[next action]], [[agora plan]].

This is one of those nodes that must begin with an introduction, or if the bullet list in nodes usually serves as introduction, then a pre-introduction :) I have so many todos that my todos often have their own todos. They are distributed around my computers, around my home, around the office.

As of [[2025-03]] I'm making a "fresh start" in the sense that I intend to come back here and actually clean up and order things, and try to keep this in roughly priority order so that the things I'm working on next are roughly towards the top. Let's see if it works!

[[2025-03]]

  • write in the [[zine]], I've been writing in my head for a while and it's time to do some actual writing?
  • test mastodon [[agora bot]] "fix"
  • fix [[betulagora]]
  • respond to the email from Mike Kupfer.
  • check out the link(s) that [[smurp]] sent to me
  • process his signup to the Agora! which I saw just before leaving for travel, looking forward :)
  • do some small FR for [[bull]]? which one?
  • fill the [[LabΓΆr]] survey

[[2023]] and earlier

Todo

You can create todos in Foam.

  • This is an example of a todo list item that's complete
  • This one is not completed yet
  • You can mark it completed by pressing Option+C (or Alt+C) when your cursor is on this line
    • You can also select multiple lines and mark them all at once!

Todo

  • This is an example of a todo list item that's complete
  • Todo lists are useful for keeping organised and focused
  • This one is not completed yet
  • You can mark it completed by pressing Option+C (or Alt+C) when your cursor is on this line
    • You can also select multiple lines and mark them all at once!
  • When you press enter at the end of a line, it adds a new todo item on the next line
  • This, and more is provided by the Markdown All in One plugin by Yu Zhang

Todo

  • This is an example of a todo list item that's complete
  • Todo lists are useful for keeping organised and focused
  • This one is not completed yet
  • You can mark it completed by pressing Option+C (or Alt+C) when your cursor is on this line
    • You can also select multiple lines and mark them all at once!
  • When you press enter at the end of a line, it adds a new todo item on the next line
  • This, and more is provided by the Markdown All in One plugin by Yu Zhang

Todo

  • Add this garden to the Agora
  • Write a [[Ghidra]] plugin to output procedures as individual [[MASM Assembly]] files
  • Finish my contribution of En_Tg to the [[Ocarina of Time]] [[decompilation]] project
  • Finish my addition of a HashMap to cats-collections.
  • Document how I accomplished the Lecture Transcriber written on [[2020-11-02]].
  • NOW Veronika, if you or anyone else has loads of time and nothing better to do, it would be handy if someone could go through the slides shared by Sassy in that orientation meeting and condense it into a checklist of actions and references. done:: 1626482875701 later:: 1626482876666 now:: 1626482963613

Inbox

Back burner

  • check out obsidian plugin api
  • move to proper [[ast]] instead of hacking around [[markdown]]
  • [[agora obsidian plugin]]
  • notion api
  • investigate [[kava]]
  • open web grant
  • make graph view look more like obsidian
  • add hypothesis integration into [[agora-server]] on a deeper level
  • autogen journal entry if non existent for nodes created on that day
  • "snapshot" feature to "freeze" a node at a specific time and archive
  • make graph on agora prettier
  • create chrome browser extension based on [[firefox]]
  • check out sections on ctznry
  • install [[mycroft]]
  • dinner with [[aphid]]
  • show actual journal entries in /journal route
    • can I use same codebase?
  • build [[notion]] integration
  • watch [[world at war]]

Done

Back burner

  • make graph view look more like obsidian
  • add hypothesis integration into [[agora-server]] on a deeper level
  • autogen journal entry if non existent for nodes created on that day
  • "snapshot" feature to "freeze" a node at a specific time and archive
  • make graph on [[agora]] prettier
  • create chrome browser extension based on [[firefox]]
  • check out sections on ctznry
  • install [[mycroft]]
  • dinner with [[aphid]]
  • show actual journal entries in /journal route
    • can I use same codebase?
  • build [[notion]] integration
  • watch [[world at war]]

Done

πŸ“– stoas
β₯± context