Skip to content

Commit ad53433

Browse files
authored
[post] Edits to Daily Journaling Report 3 (#238)
1 parent 3680e8e commit ad53433

File tree

1 file changed

+144
-0
lines changed

1 file changed

+144
-0
lines changed
Lines changed: 144 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,144 @@
1+
---
2+
title: "[Daily Journaling] Report 3"
3+
slug: daily-journaling-report-3
4+
published: 2025-08-12
5+
description: >
6+
The third report in the series on "daily journaling" with my second-brain setup.
7+
8+
---
9+
10+
It has been just under 7 months since my last overhaul of my daily journaling system and how I use
11+
it. In that time, I have had some significant life changes that have led me to a different usage
12+
pattern of my devices. My needs have changed with respect to my "second brain".
13+
14+
Last year, every morning would start with me making a cup of coffee (a pourover) and sitting down to
15+
turn on my computer. As soon as I was logged in, I would pop open my second-brain and write all of
16+
my morning subconcious/shower thoughts, review the previous day, set an intention for that day, and
17+
then make a todo list. It quickly became my mornning ritual, cultivating my digital home where I
18+
track of my tasks and any thoughts that pop into my head.
19+
20+
However, this year has brought on a more nomadic lifestyle. The months of April and May barely saw
21+
me turn on my computer more than once a week. During this time, I still needed some-what daily todo
22+
lists and reverted to using the ever-present Obsidian on my phone. As this muscle memory was
23+
defined, I found myself duplicating my todo list between devices on the days where I would use both,
24+
depending on the context and what I needed. And every pragmatic software engineer bristles at
25+
breaking DRY principles.
26+
27+
28+
## Updates - Goodbye Apple (Set up Note Syncing)
29+
30+
How do you solve a duplication error when data in needed in more than one place? You've probably
31+
already guessed. I needed to sync my notes between my mobile device and my laptop. So, as any
32+
engineering leader worth their salt, I sat down and did a return on investment analysis:
33+
34+
<details>
35+
<summary>Journal Excerpt - Investment ROI</summary>
36+
37+
> ## Notes Syncing
38+
> ### Problem
39+
> I keep running into the issue where I want my `~/second-brain` and my phone
40+
> notes app to sync so that I don't have to manually copy my list between devices.
41+
> ### Solution Requirements
42+
> 1. Full Neovim use while on laptop (unopinionated markdown files)
43+
> 2. Mobile App markdown editor
44+
> 3. Note syncing (could be manual)
45+
> 4. Optimize for laptop power usage and only an extension with the phone
46+
>
47+
> | ID | Solution | Cost |
48+
> | -- | -------- | ---- |
49+
> | 1 | Pay for Obsidian Sync | $4/mo |
50+
> | 2 | SyncThing + Android | $400 |
51+
> | 3 | Custom Mobile App | $400+ |
52+
> | 4 | Mobile Git Editor | $35/yr |
53+
>
54+
> #### Obsidian Sync
55+
>
56+
> This incurs an ongoing cost forever. I also believe that I would have to open
57+
> Obsidian on my laptop to make sure that it syncs before opening my second brain.
58+
> This workflow feels pretty clunky and I don't think it solves my issue with
59+
> syncing.
60+
>
61+
> #### Syncthing + Android
62+
>
63+
> SyncThing doesn't work on iOS because of folder "security" measures.
64+
>
65+
> This could be free if I use the current Pixel that I have. However, I really
66+
> dislike the bulky camera on the back. I think if I went this route, I'd like to
67+
> get a new phone.
68+
>
69+
> #### Custom Mobile App
70+
>
71+
> This is the most interesting, but also most complicated. I would love a PWA that
72+
> has an offline mode that I built myself. However, this would take quite a bit of
73+
> time to build the mobile/web app portion and then the backend portion.
74+
>
75+
> Even with a PWA, iOS makes it completely frustrating...I would probably switch
76+
> to Android anyway.
77+
>
78+
> #### Mobile Git Editor
79+
>
80+
> Since `~/second-brain` already uses git to sync, I could just figure out how to
81+
> use Git on the phone. However, this doesn't come with automations built-in to do
82+
> things like Daily Notes and the like.
83+
>
84+
>
85+
> ### Selected Solution
86+
>
87+
> Set up Obsidian and SyncThing on the current Pixel. If it works, buy the 9a with
88+
> the smaller camera. I have until 8/15 for the current $400 deal.
89+
90+
</details>
91+
92+
**TL;DR:**
93+
> I will be experimenting with Obsidian and SyncThing on my current Pixel tomorrow
94+
> evening. If it works, I'll buy the 9a because of the smaller camera. I have
95+
> until 8/15 for the current $400 deal.
96+
97+
In the end, I decided not to purchase a new Pixel since my Pixel 7 works just fine and seems a lot
98+
thinner with a the needed protective case.
99+
100+
101+
### Solution Implementation
102+
103+
SyncThing is designed to be a distributed file syncing system. This means that you can share a local
104+
folder with many other devices. While my phone is almost never off, it might lose internet access
105+
through a connection issue or airplane mode. While syncing dirctly between my laptop and phone would
106+
probably work for the majority of the time, I decided on a more complex syncing architecture through
107+
my NAS.
108+
109+
I have a somewhat extensive homelab setup that includes a Synology NAS. Installing SyncThing from
110+
the third-party registry was easy. Adding SyncThing to my NixOS laptop was a little more interesting
111+
with the general lack of user friendly documentation for most NixOS packages, but it quickly fit
112+
into the declarative nature of its configuration.
113+
114+
Choosing this solution required switching to an Android-based phone over an iPhone. iPhones have
115+
pretty locked down security features which do not allow applications to share files, which is needed
116+
in this case.
117+
118+
I took this time to finally switch to GrapheneOS since I have been meaning to switch for the last
119+
few years (and even had a Pixel 7 from a few years ago when I was trying to get ready to switch).
120+
The setup of SyncThing and Obsidian was straight forward and the Storage Space feature was a great
121+
use to allow both both Obsidian and SyncThing to access the same files.
122+
123+
### Gotchas
124+
I did run into a few issues that needed resolving while testing the end-to-end system. The first is
125+
that reusing folder labels and folder IDs after deletion leads to weird global sync states. During
126+
any future testing, I would recommend rotating at least the folder ID with every additional folder
127+
test, if not both. I ended up wiping the NAS SyncThing index DB multiple times to fix the global
128+
issue because I had been testing with the `second-brain` label with the same static folderID from
129+
the NixOS declarative configuration.
130+
131+
Additionally, the `.stignore` file is different on every device and should be created before syncing
132+
anything off the local device. I wanted to ignore the `.obsidian` directory on my phone because it
133+
is different than the one on my laptop (on the rare occasion that I use Obsidian on my laptop). I
134+
also didn't want the updates to the obsidian workspace files to constantly sync. I made a similar
135+
choice with the laptops's `.zk/notebook.db` file which constantly changes with every edit. However,
136+
care must be taken if the file was previously synced. In such a case, the file should be added to
137+
the remote device's `.stignore` file before deleting to make sure that the deletion is not synced
138+
across all devices as well.
139+
140+
## Conclusion
141+
142+
In the short few days since getting this set up, it has been great to be able to drop in on my
143+
laptop's daily note from my phone, and make updates on the move as needed. It has been well worth
144+
the pain of switching phones.

0 commit comments

Comments
 (0)