forgive me, publishing flow, it’s been 12 days since my last post. that’s if you’re monitoring word count and post categories. (are confessions allowed to add context?)
my changelog tells a different story. code is a language, too. and in that dimension, I’ve written and committed—not to mention fixed a helluva lot of issues 😵💫—letters and numbers to the nth degree. the changelog talking about my site, however, is but half the story. I’ve been working on my website all year, and I’m at the point now where there’s not much to add or change except incrementally.
thanks to the brainwave letting its electric insight waves ripple through my brain right this second, I’ll also start maintaining an Obsidian changelog. after all, it’s been my happy space for the past weeks, and it’s only right that I start keeping a record of the hyperfocus tunnels I disappear into.
as anyone who knows me can attest (often painfully, because man can I hyper fixate), I’m a (rather obsessive) die-hard fan. I live in Obsidian. it’s been my closest digital companion for the past six years. I publish my website from inside the app. it’s the interface I use to post to my social stream.
yet, not until I accidentally ended up creating my first Obsidian plugin recently while bringing to life my interstitial reading tracker did third-party plugins stop being a mystery to me. and bam! like a floodgate, the possibilities started opening up.
I was never much concerned with the security around external plugins until Claude started bringing the masses. suddenly, everyone had a second brain, and their LLMs were all over the ecosystem, with new plugins being released at tremendous speed (so much so that Obsidian, the company, had to overhaul its plugin review process1 refer to The future of Obsidian plugins for more details , introducing automated security scans for every plugin version).
inevitably, it wasn’t long before the vultures showed up. back in April, I got wind of the Elastic Security Labs report2 see Phantom in the vault: Obsidian abused to deliver PhantomPulse RAT for the TL;DR, PHANTOMPULSE: anatomy of a hijackable blockchain-C2 RAT for the technical breakdown that nefarious social engineers were using Obsidian’s community plugin ecosystem to deliver malware to targets in the financial and crypto industries. as a blockchain industry professional, I’m a very frequent target, and am consequently well-schooled in keeping myself safe. however, Obsidian had for years been so niche that I felt myself to be confident enough to install community plugins as I saw fit.
immediately, I uninstalled most all of my third-party plugins, hoping that, as time passes, more and more of my plugins of choice would be incorporated into the core plugin ecosystem.
once I built the reading tracker, it was as if an entirely new world had opened up to me. suddenly, I understood the backend, the machinery that makes it all go. and I wanted more. be careful what you wish for I guess lol 😂
next came a fairly simple solution. I wanted to house a meta index for my handwritten notebooks, but Obsidian Bases had a limitation in exactly the area I needed; Bases’ default table view only allows one row per note, whereas I needed each notebook entry to have its own row. the solution was either, you guessed it, a community plugin, or I’d have to put together my own local version. naturally, that’s just what I did.
at the moment, I’m working on two plugins simultaneously. learning a TON. happy as can be, even when trying to fix weird bugs, so I’m writing this not because I wanted to drag myself away from being under the hood, but because I don’t want to lose my active weeks meteorology badge streak 😅
one plugin—my music tracker—is already live. ambitiously as it began, it continues to morph into something more substantial still. the next step is integrating it with Roon and Tidal. watch this space!
the other one’s more complex. I’m putting together a Daily Note Dashboard plugin that pulls from various templates, headers, and properties in my daily notes template and visually displays my stats, data, tasks, and updates. it’s a lot less straightforward, because I’ve had to start with an ongoing audit over the past half a month, constantly tweaking templates to ensure I’ll be able to pull the right data in the right way.
and now I’m on a mission to completely eliminate my reliance on plugins that aren’t my own. can I build my own replacement to the Linter plugin, since the community plugin version introduced such performance issues that I had to remove it?
I’m excited to find out!
footnotes
-
refer to The future of Obsidian plugins for more details ↩
-
see Phantom in the vault: Obsidian abused to deliver PhantomPulse RAT for the TL;DR, PHANTOMPULSE: anatomy of a hijackable blockchain-C2 RAT for the technical breakdown ↩