gistfile1.txt

- Meta
    - I started writing this on Slack, and finally decided I'd write it on my Roam, that way I have these notes, and it's also easy for you to copy to your Roam if you so desire
- Communications
    - One Roam or back and forth
        - A manual approach would be just including the whole page in an email, I could paste it over my page, make edits, put it in an email to you, you paste it back into your Roam and make edits etc... 
        - But I'm happy to just go look at your Roam, easier for now)...
    - Notifications
        - Either way, for now you need to ping me when you've made an update, since there is no notification (for you, I'm assuming pinging your daily page is sufficient - hoping you don't miss any days :))
- Roam format
    - simplest - highlight comments (but only works once)
        - add some comments and highlight it (^^), and then tag me, and I can go look at it.
    - write on page, block reference
    -  A more advanced approach which is slightly more work is for you to add comments, and then block reference them in a daily page... 
        - You can even have a "Stian inbox page", and then tag that page with the block references (that way I'd see the daily page for chronology and the specific new comments, and I can click on them to go to where they've been added, to see the context). 
    - Tags and queries
        - Final idea is to use queries - so if you add new bullets anywhere, but tag them as [[Joel]] and /today, then we can have a query either on the same page or somewhere else with and: {[[Joel]] between [] [] }} (or if it was a multiplayer Roam, even {{not: [[Stian]]} to see everything written by others. 
- JSON export
    - Of course if we could query by date-created and create-email (all info which is in the JSON export) we could do this automatically... 
    - so one idea would be to do some processing in the JSON script, and generate some output. Disadvantage is that it's annoying to have to manually export JSON and process it. Also not sure what the output should look like or what kind of workflow (ideas?)
    - I was recently talking to [[Aengus McMillin]] about #Roamex and [[Gatsby]], and we have some ideas about [[digital garden]]s. I'll make it possible to use my [[roam-export]] script to generate output for his Gatsby script, 
        - looking for all pages marked #blog /date and automatically generate nice blog posts, with archive, RSS feed, convert Roam hierarchy to h1/h2/h3, automatically process citekeys with Pandoc to APA style, etc
        - pages marked #evergreen converted to Gatsby pages (not date stamped etc, but can be linked from blog posts)
        - pages marked #backlinks, the backlinks are exported in a bullet format (like my 90 Zettelkasten backlinks)
    - and he will improve the Gatsby side. 
        - better formatting etc
    - and then we talked about ways of interlinking these
        - technically
            - should they be hosted on the same system (for example one server which pulls from multiple Github repos containing the pages of several people collaborating)
            - or some very simple server which gets "pinged" by different blogs - similar to how blog backlinks used to work
                - advantage: other systems, like TiddlyWiki, can participate
        - what does it mean to interlink?
            - "planet" of new pages - but how to deal with changes
            - word cloud
            - linked references (and unlinked) across all posts
        - so there could be something around open collaboration here as well. I'd be excited to try out specific projects, small group of people and some guidelines, whether it's a distributed brainstorming on note taking, or a mini bookclub where we all read the same papers/books and take notes in a specific way that let's us integrate/build upon (would love to get [[Bodong Chen]] involved in thinking about how group thinking can go deeper/build upon etc)