-
{{[[TODO]]}} (hidden) nbTbMG1vy
-
{{[[TODO]]}} (hidden) m5P_yarOS
-
(hidden) PyTARW-IK
-
(hidden) ItbmGzpJY
-
(hidden) g_EmvhT99
-
(hidden) NGjUNI-s- [[(hidden) 2bbM29Hpx]]
-
(hidden) 7HEXnOjhs
-
(hidden) uiKairHZ3 #[[(hidden) WNCAo37xy]]
-
(hidden) AoV3Q6M4U
-
{{[[TODO]]}} (hidden) unL4OhItK #watch
-
(hidden) wqJZRy_L9
-
{{[[TODO]]}} (hidden) GcVTbIoaf #read
-
(hidden) JRn5jvvpL
-
(hidden) NsjOadANA [[the innovator's dilemma (TBD)]] [[(hidden) 3XVIQovjW]]
-
(hidden) bcU3nm18N
-
(hidden) MsZBiU3XO
-
(hidden) XVPF-tCry
-
{{[[TODO]]}} (hidden) AGY1jSE2n [[(hidden) AjsidmZk0]] #[[(hidden) -VnoIOF8r]]
-
(hidden) tATtp6hbD
-
(hidden) co04CZ7Rg [[(hidden) 8QdwtiNL-]] [[(hidden) EPYV31rY-]] #[[(hidden) S-ygYfi0j]] #[[(hidden) gJ0JPQHL7]] #[[(hidden) VZrbM9KJQ]]
-
(hidden) yreBPknBs
-
{{[[TODO]]}} (hidden) _GI4xffwn [[(hidden) JJEYAPdym]]
-
(hidden) e-N6FAaKm
-
(hidden) eGHXmgvKb [[(hidden) EPYV31rY-]]
-
(hidden) 4fpChflgb [[(hidden) 3y7aOR6Ar]] [[(hidden) pPmx61yhs]]
-
{{[[TODO]]}} (hidden) WXXvGCSWJ [[roam]] #[[(hidden) D1lY0CG5e]]
-
{{[[DONE]]}} (hidden) PVKcPNQo-
-
{{[[DONE]]}} (hidden) lP3MDS6zp
-
(hidden) pQE2C0JXH
-
(hidden) 3GkE-4nOo
-
(hidden) 6jkNuo4e9
-
{{[[TODO]]}} #observation from previous - okay so i was thinking about wanting such a thing recently & now it came out, & the guy was working on it for 4-6 months. nice! makes me realize that the ideas of (what i think of as #roam-traverse-graph ) aren't being considered by me only - i shouldn't hold it in private for too long, gotta make it public! ofc [[balance between launching fast & launching a well-enough product that your users actually stay & don't get bad expectations / set it off forever]] still applies, but gotta try.
-
{{[[DONE]]}} visit slack, see wassup
-
re: > mobile experience of [[roam]] is meh
-
https://roamresearch.slack.com/archives/CNC4881EU/p1640315470419600?thread_ts=1640166267.412200&cid=CNC4881EU
-
idk, using roam on mobile has always been just fine. first you open roam on chrome/similar & save the SPA to the desktop as an app shortcut (at least on android) thus no need to open the brower, no need for the url bar, etc., its becomes like an app. and then instead of the default simplified version of roam for mobile, you click some button like "full app" or smthn similar, and then it has shortcuts to do common things:
-
-
maybe my phone isn't small either (poco f3, highly recommend) - that surely helps as well. but even w/ a smaller one, with this setup, should be better.
-
-
-
-
-
(hidden) s3AsGsvtX
-
-
(hidden) 122c0Pxs7
-
-
(hidden) qBD2uTEwu
-
-
(hidden) LOXFPq1ic
-
{{[[TODO]]}} (hidden) UXblvTnBt [[(hidden) X7oZG5qJs]] #[[(hidden) jOMmlCP4S]]
-
(hidden) sb80H_Eqt
-
(hidden) pslsGkDVc
-
(hidden) NbGdCoMzy
-
-
(hidden) QWD1c3hap
-
-
(hidden) ty90FRFQZ
-
(hidden) ViICkJXNK [[(hidden) IX1JV8fxQ]]
-
(hidden) NyBvSYSOw
-
{{[[TODO]]}} (hidden) j187HFiFE [[(hidden) roASD9JXi]]
-
[[software i hate]]
-
"interactive" CLIs with stupid prompts.
-
examples (too many already)
-
they throw away the best parts of the command line
-
they take in the worst parts of a UI
-
imagine not having using something like `pacman`, and `git` enough (e.g. add --patch) that you don't have good ideas for
-
1. __not__ having to have a prompt in the first place, and having commands/sub-commands and, or just, arguments (either boolean - exists or not, or whatever option)
-
2. if a prompt must, __not__ having to navigate it with shitty little arrow keys, and instead providing good defaults (pacman's `question? [Y/n] `), or even selecting from multiple by using intuitive names for the operations you'll do (git add --patch's `(1/n) Stage this hunk [y,n,q,a,d,e,?]? ` - most of these out of the bat don't need much explaining do they? they're intuitive).
-
though, the 2nd one has nuance. it works well for git because the `add` operation is extremely common to do (so as is using git itself). if your tool is not on the same level, it'll likely be harder to achieve this intuitiveness without having to do something like `do foo? (Y)es, (n)o, (a)lways, neve(r), (s)kip, (j)ump` etc., and if the amount of things to select from (esp. if there's a selection, especially if a one w/ dynamic (~ arbitrary) amount of items to select from), then __maybe__ the arrows __might__ be better fit, but i haven't seen such a scenario yet, - rather, people over-use the arrow selections because it's the easy option to go with. fuck [[mediocrity]].
-
-
3. avoiding both in the first place, if possible, w/ good defaults (__not__ "too" good that they are no longer intuitive though)
-
-
-
-
(hidden) mFpEAAveQ
-
(hidden) qSyPx83e6
-
{{[[TODO]]}} (hidden) meGw92qsb
-
(hidden) mfb71Z6jn
-
-
(hidden) -GfMj5nvI
-
[[git-stacked-rebase]]
-
re: ((i5tnEKxMP))
-
yeah would be nice, because just found out that e.g. the `git parent` (& all others that depend on it), when in the latest branch/diff of the stacked rebase, it shows parent as the initial branch (which in this case makes sense - we rebase on top of it, and partial branches are not "technically" our parent ones, at least how the current implementation of "parent" works (hacky alias btw), so would be nice to change & improe)
-
-
{{[[TODO]]}} Exitable - could have `succ` & `fail` return length 3 array - 1st item would be exit code, 2nd message (stdout or stderr figured out by the exit code), and return if succ. solves most problems lol
-
{{[[TODO]]}} branch-sequencer - somehow specifying whether to include or exclude the first & last branches (by default (already there) excludes first (initial), includes last -- all because it's how --apply and --push worked even before extracting into branchSequencer, and then afterwards as well)
-
-
(hidden) 9ZufZuYIZ
-
(hidden) G9td_xiuY #[[(hidden) Py4a4fa73]]
-
(hidden) b0Z9f0Vad
-
(hidden) Gs6DBYbBh [[(hidden) zJw7j5jxr]]
-
(hidden) YEmdCA6wA
-
(hidden) TN1K5DAbr
-
(hidden) ifKT5ntGZ [[(hidden) EPYV31rY-]] #[[(hidden) D1lY0CG5e]]
-
(hidden) QIX8AlMbl
-
(hidden) rL84VgAnU [[roam-traverse-graph-settings]]
-
[[roam-traverse-graph]] [[export-html-pages]]
-
{{[[TODO]]}} new #[[(hidden) jOMmlCP4S]] - public recursive tag, but only if the page that is made public recursive, is mentioned in root level of a page (1st lvl child block) & has nothing else inside it (just like i often do in daily notes when referencing other pages & "writing into them" via linked references).
-
{{[[TODO]]}} oh snap, inspired straight from the [previous one](((HW3tg57Ww))) - having a `roam/js` or whatever "extension" to add the simplest of indicators if something will be public -- would be great!
-
{{[[TODO]]}} maybe on hover, could even explain why
-
{{[[TODO]]}} but, for this to work smoothly, we kinda would need to double down on the "having most things in [[roam-traverse-graph-settings]]" that we want configured, instead of configuring things there such as "tag-that-makes-other-pages-public-recursive", whom would in turn be used in pages directly - this would mean it's easier for the [[roam]] user to use (probably? + info via linked references), but harder for tools to parse, because instead of parsing just the 1 single settings page, you have to parse it, and then parse all the related pages as well.
-
-
{{[[TODO]]}} another one re: the total global word count as a number in the landing page
-
we could have it be a button (well, a tag with href) that navigates to a page that has a graph (chart) of (top secret what it shows)
-
{{[[TODO]]}} oo even more ideas - something like [[(hidden) btHMgS_i0]] has w/ "cool" statistics (normies represent, am i right?)
-
{{[[TODO]]}} #[[(hidden) D1lY0CG5e]] [[roam]] lmao just noticed - let me scroll to the very bottom of the page, even though there's no content there (i.e. like vim) - would be useful when i have some block opened & editing & want to scroll the current text higher into the view w/o creating a bunch of empty blocks below it.
-
-
-
-
-
(hidden) etq9XMnlS
-
-
(hidden) NM-YPacGd
-
-
(hidden) 1VR5JNB3s
-
-
(hidden) _MLDhXS90
-
(hidden) ELxSvkJwz [[(hidden) 12-23-2021]] [[(hidden) j-eCgnBmv]] [[(hidden) D1lY0CG5e]]
-
(hidden) m_4fyRoTs
-
(hidden) OUstq4IPB
-
(hidden) 6UDetkN6L
-
(hidden) H2gfO6F_R