Post #4403465
2026-08-06 03:02 UTC
Replies (2)
-
@pedersen@c.im 2026-08-06 04:08
@kerravonsen@mastodon.au Lots of respect for making that work. Last time I tried to write an obsidian plugin, it was painful and I never got far with it. You not only did it, you fought through a ton of technical challenges that, honestly, I don't know I'd have the patience to do myself. Well done!
-
@pedersen@c.im 2026-08-06 12:53
@kerravonsen@mastodon.au Now that's a genuine misread on my part. Thanks for the correction! You still did some heavy lifting to make it work though, and that's worth celebrating. A nice thing you could do if you're up for it would be to file your findings as a bug report on that plugin. I know I'd appreciate it if I got something that detailed. As for my own experience with obsidian plugins, there were two things that made me displeased with the experience, and only one of them was the fault of obsidian itself. The first was the lack of documentation. Even getting a simple "hello world" running was a challenge. I hope they've fixed that issue by now, but even at the time plugins were a big thing and the documentation wasn't. The second was on me: I couldn't fully describe what I wanted, so I couldn't map out how to accomplish it. That has changed, but an obsidian plugin is no longer the right vehicle to describe what I want. That description is much longer than I can toot though 🙂 So I'm writing my own app that also uses markdown. It'll therefore be compatible with obsidian. The lesson: if a plugin is the wrong shape, consider doing your own app that would be compatible. It might work better. And if you want some ideas on how to build and maintain that, I can offer those up as well.