(re)discover | notes | kipras melnikovas

(re)discover

words:	82 + 1085 = 1167
last update:

#public
[[January 6th, 2022]]
- not in a bad way that you're re-inventing the wheel / doing something just for the sake of it. rather -- discovering something, that you might or might not knew existed before, with some individual mental model / independently, i.e. you might be doing something that at first glance doesn't seem related, but then when you get to the bottom of it, you find a connection to something that "already has a name" (finding a connection? [[cc]]: [[roam]])

Linked Mentions (1 in 1 page)

January 6th, 2022 (1)

wait probably not even an `Error` - we can throw anything we want! the main benefit is that we can throw however deep in the call stack we want, and then catch it however high. wait. this is epic actually. [[(hidden) DY6wPnICE]] is this how you [[(re)discover]] [[algebraic effects]]?
- [[export-html-pages]]
  - {{[[TODO]]}} would be interesting to explore connected relationships, even if the pages do not directly reference themselves, but e.g. like here w/ (re)discover & algebraic effects - they're in the same block
    - re:: ((crag_e60m))
      - haha i guess fair, but don't worry much - [[roam-traverse-graph]] is first and foremost a low-level utility/library that one can use to build tools such as [[export-html-pages]]. and if we take our own shot at it - it's how we want it to be, and if we have some [[unique]] (?) [[(hidden) jOMmlCP4S]]s & are able to explore them - the better it is for all!
        
        cc:: [[(hidden) zJw7j5jxr]]? or at least [[(hidden) EPYV31rY-]]
  - re:: coloring public blocks' lines
    - {{[[TODO]]}} another #[[(hidden) jOMmlCP4S]] -- instead of having every single line to recursively, why not follow in a $$45\degree$$ or whatever angle and highlight only the right-most lines?
      - ok some blocks are obv. longer than others so maybe wouldn't look good the diagonal part (the vertical part -- all good regardless), and a completely horizontal line to go from one level to another would be fine?
        
        or maybe it's fine actually. would have to test it out & [[see what feels better]]
    - {{[[TODO]]}} yet another #[[(hidden) jOMmlCP4S]] - being able to copy a link to a page, or rather - to a specific block which will end up in that page
      - use case e.g. - creating a git commit, and instead of inlining stuff that you already wrote down, instead linking to it.
        
        [[philosophical question]] (because [[bus factor (tbd)]]) if this is a good #[[(hidden) jOMmlCP4S]] or not.
        
        as long as it's static html w/ everything inlined, so that if anything goes down, you're still good - then maybe not too bad?
        
        cc:: [[the question of using a custom domain vs github pages]]
        
        re:: [[(hidden) _d7I12UTL]]
        
        oh fuck another #[[(hidden) jOMmlCP4S]] while thinking about this -- if we setup roam for further automations, e.g. [[creating jira issues / sub-tasks from roam's TODOs]]
        
        WAIT i thought you'd have like a custom server and use [[roam-traverse-graph]] to parse the graph, and then have like a frontend dashboard SPA or whatever to confirm stuff. BUT hold up, we have [[roam/js]]. we can get rid of literally all of the #bs, and do everything directly in [[roam]] 🤯 for API calls to some endpoints, sure could use a server, or e.g. lambda functions. but perhaps roam directly is also fine, if we can securely keep secrets stored?
        
        [[(hidden) DY6wPnICE]]
        
        [[roam]] as the personal "[[(hidden) pCdH3SJhT]]" / no-code / automations platform???
        
        re:: "no-code" - lol, ofc you'd have to code up the [[(hidden) AqlNqCYG6]]s, but then you can share them and use them and everything's directly in roam. fuuuuuuuck this is [[(hidden) -MiVLWUzx]]
        
        (hidden) D1lY0CG5e:: {{[[TODO]]}} ideally you'd be able to [[self-host]] [[roam]] because at this point you'd be [[running critical infrastructure]]
        
        cc:: [[roam "enterprise"]]
        
        thought beware -- remain user-focused, never [[(hidden) 6jcY_WnAD]], [[you gotta zuck'em]], stay [[(hidden) EJItNRkJG]], do not give power to the [[professional managerial class]]
        
        {{[[TODO]]}} okay more [[(hidden) jOMmlCP4S]]s coming in from thinking about this:
        
        re:: `publicRecursive` tag @ [[export-html-pages]]
        
        maybe instead of `publicRecursive`, we need to make it a point that the purpose of this is to have everything in daily notes, and under that tag, blocks become public and end up in the page as a linked mention.
        
        so that it'd be made clear that this is the purpose of it, and not a general `publicRecursive` meta-tag. then, we'd be able to very easily detect if something is a "page collector" or whatever better name we come up with, and then e.g. the coloring stuff becomes way more precise
        
        {{[[TODO]]}} might even be useful for [[roam's multiplayer mode]] and the #[[(hidden) jOMmlCP4S]] of [["putting" things into multiple graphs]], or, rather, giving other, shared-graphs e.g. read access to some of your notes, if they're under that tag (while still being able to own them?)
        
        cc:: [[roam "enterprise"]]
        
        re:: ((wiW41Si-y))
        
        #[[(hidden) jOMmlCP4S]] / #[[(hidden) D1lY0CG5e]] for [[roam]] - would having a central place for settings, provided by the [[(hidden) AqlNqCYG6]]s / extensions, be useful?
        
        something similar to [[vscode]] i suppose
        
        thought about it because it'd likely save time / less http requests to do -- even if you have [[meta tags]], you don't need to 1. fetch your custom settings page, 2. fetch the linked references of the tags - you'd be ensured that 1. is always done & up-to-date (it's easier for roam if it itself tracks what's updated & when it is - just updates, otherwise caches)
        
        but, maybe inconvenience if you're using some other languages for the [[(hidden) AqlNqCYG6]]s (if even possible?), and in general feels less [[wild west]]-like / less [[(hidden) NWcsO1fe0]]. will see.
        
        {{[[TODO]]}} is [[re]] an [[anti-pattern]]? i.e. it becomes unclear if what you are "referring to" is from the content above, or some other page (if it's not a linked ref (of a page or a block) and just text) - you might start looking at the previous content but not find the thing that i meant to refer to, or even worse - could find something that is actually not the thing, and then get further confused. idk idk
        
        re:: [[creating jira issues / sub-tasks from roam's TODOs]]
        
        {{[[TODO]]}} must avoid cluttering the raw UI of [[roam]].
        
        {{[[TODO]]}} as a minimum, could have an option to `onlyEnableUnderFollowingTags: []`, but this shouldn't be used an excuse to allow trashing the UI when the option matches and we are inside a specified tag
      - extra stuff to work out though because depends on where you want the link to end up at -- the daily notes page, or within some page as a linked mention.
        
        {{[[TODO]]}} could have a selection to choose from, given that we'd already be parsing the other linked references to find out publicity & to do the coloring
      - {{[[TODO]]}} would need to have a predefined base url for the notes in the [[roam-traverse-graph-settings]] page.
        
        observation:: hmm, a reason why you wouldn't want to have meta-tags (e.g. tags that make other tags have [[magic]])
    - {{[[TODO]]}}
  - re:: custom domain - ((UUaQUFGpI))
    - hmmm hmm. now again i think non-breakage / longevity are higher prio than the possibility of losing control.
      - simply because who can be blamed if it goes wrong
      - & overall value(ability) of having it available vs controlling it
      - though, URLs are less [[/comfy/]] for sure. idk