Show HN: I built my own second brain software tool(joeldare.com)
joeldare.com
Show HN: I built my own second brain software tool
https://joeldare.com/i-built-my-own-second-brain-software-tool.html
20 comments
Have you tried Obsidian? https://obsidian.md/
I use Obsidian for that exact reason of the notebook being "just" a collection of raw markdown files and owning my own data as well.
I'm pretty happy with it so far.
I still use Sublime to edit the files quickly and when I don't need features provided by Obsidian plugins.
A minor gripe is that the iCloud sync is really really bad. Perhaps that's more on Apple than Obsidian, but frequently editing of the same files across multiple devices is a pain point today. To their credit, they have acknowledged this and now offer their own first-party sync service, but I think $96/year to sync a folder of Markdown files from my laptop to my phone is excessive.
I'm pretty happy with it so far.
I still use Sublime to edit the files quickly and when I don't need features provided by Obsidian plugins.
A minor gripe is that the iCloud sync is really really bad. Perhaps that's more on Apple than Obsidian, but frequently editing of the same files across multiple devices is a pain point today. To their credit, they have acknowledged this and now offer their own first-party sync service, but I think $96/year to sync a folder of Markdown files from my laptop to my phone is excessive.
Question; So i'm also designing a "second brain" for myself/foss, and i've often had the debate of how much i should go with plaintext.
On one hand it is nice for basic tools like grep, custom editors, easy backup, etc. However "lockin" is something i keep pausing on.. because for any advanced features you include, say spaced repetition over items in the document, becomes a unique DSL for your application most likely. Yea, it could be made from "just markdown" or w/e, but the functionality still only works in that one app.
Eg i used some other Space Rep tool which advertised using just markdown, cool! But i can't port it anywhere, so yay it's plain text but the functionality still need to be refactored to work with other tools.
This problem becomes more apparent when you add more complex features. Each unique/novel feature creates unique DSL to store state in "plaintext", which to me starts feeling like it destroys the core premise of plaintext.
Thoughts on this issue?
On one hand it is nice for basic tools like grep, custom editors, easy backup, etc. However "lockin" is something i keep pausing on.. because for any advanced features you include, say spaced repetition over items in the document, becomes a unique DSL for your application most likely. Yea, it could be made from "just markdown" or w/e, but the functionality still only works in that one app.
Eg i used some other Space Rep tool which advertised using just markdown, cool! But i can't port it anywhere, so yay it's plain text but the functionality still need to be refactored to work with other tools.
This problem becomes more apparent when you add more complex features. Each unique/novel feature creates unique DSL to store state in "plaintext", which to me starts feeling like it destroys the core premise of plaintext.
Thoughts on this issue?
There’s quite a few plain text apps. I am hovering between four right now. Markdown format but still plain text. Obsidian would be the most known of these. Then also Noteplan 3, Keep It, and Devonthink
I like foam as well, it’s markdown, open source
https://github.com/foambubble/foam
Though admittedly I rarely use backlinking.
https://github.com/foambubble/foam
Though admittedly I rarely use backlinking.
Zim desktop wiki is worth a look
Interesting. I use Dokuwiki but with a couple of MD extensions, so it stores and I write in MD. Works well.
I loved Dokuwiki for a time and it suited me well. These days I have a few specific pains with it though.
* Even though it’s just plain text files, I’ve been unable to move it to another server (you can’t just copy the folder because of its indexing system). There’s more to it.
* It’s somewhat difficult to update and requires frequent security updates
* It’s design, and all the available templates I’ve found look pretty old
* It’s native format is not MD
* Even though it’s just plain text files, I’ve been unable to move it to another server (you can’t just copy the folder because of its indexing system). There’s more to it.
* It’s somewhat difficult to update and requires frequent security updates
* It’s design, and all the available templates I’ve found look pretty old
* It’s native format is not MD
Even though it’s just plain text files, I’ve been unable to move it to another server (you can’t just copy the folder because of its indexing system). There’s more to it.
Not true. Being portable from server to server (even across different file and operating systems) is one of DokuWiki's main goals. All you may have to do is clear the cache. See https://www.dokuwiki.org/faq:servermove
It’s somewhat difficult to update and requires frequent security updates
DokuWiki releases come out like every 1 to 2 years. Security hotfixes are rare but always easy to apply (usually you just replace one or two files). Upgrading is more or less a couple of clicks when using the upgrade plugin: https://www.dokuwiki.org/plugin:upgrade
It’s design, and all the available templates I’ve found look pretty old
I guess that's up to personal preference. Personally I'm still happy with the default template but people seem to like the bootstrap3 and argon templates
It’s native format is not MD
True. There are plugins that add MD support, but I agree, native DokuWiki syntax is much better supported. If you're familiar with Markdown, it won't be hard to pick up DokuWiki syntax, but yeah it's different. DokuWiki is about as old as Markdown, when it was invented markdown was just another unknown formatting language...
Not true. Being portable from server to server (even across different file and operating systems) is one of DokuWiki's main goals. All you may have to do is clear the cache. See https://www.dokuwiki.org/faq:servermove
It’s somewhat difficult to update and requires frequent security updates
DokuWiki releases come out like every 1 to 2 years. Security hotfixes are rare but always easy to apply (usually you just replace one or two files). Upgrading is more or less a couple of clicks when using the upgrade plugin: https://www.dokuwiki.org/plugin:upgrade
It’s design, and all the available templates I’ve found look pretty old
I guess that's up to personal preference. Personally I'm still happy with the default template but people seem to like the bootstrap3 and argon templates
It’s native format is not MD
True. There are plugins that add MD support, but I agree, native DokuWiki syntax is much better supported. If you're familiar with Markdown, it won't be hard to pick up DokuWiki syntax, but yeah it's different. DokuWiki is about as old as Markdown, when it was invented markdown was just another unknown formatting language...
Based on your response, I'll try again, but as the developer, you might be a little too close. Clearly you understand the system completely while I'm just a user.
Not true. Being portable from server to server (even across different file and operating systems) is one of DokuWiki's main goals.
I've been using DokuWiki for more than 20 years (it's still live on my website though I haven't written new notes in it for more than 10 years). I wonder if the fact that I started with a version 20 years old is a factor. I have done a lot of upgrades over the years, but I started with a much older version. I've tried following your directions for moving the server and clearing the cache. For whatever reason this hasn't worked for me, yet.
Security hotfixes are rare but always easy to apply (usually you just replace one or two files).
One of my most popular pages is a set of instructions I wrote on how to apply DokuWiki upgrades. Not all of your users find it as easy as you do or I suspect my page wouldn't be very popular. If it's true that you can just replace a file or two, I'm certainly doing it the hard way. My instructions include copying all of its files over the old installation.
https://www.joeldare.com/wiki/upgrading_dokuwiki
Anyway, I'm not trying to beat up DokuWiki. It's a free tool that worked very well for me for a long time and I appreciate you for it. It's just no longer the tool of choice for me for the reasons I outlined above.
Not true. Being portable from server to server (even across different file and operating systems) is one of DokuWiki's main goals.
I've been using DokuWiki for more than 20 years (it's still live on my website though I haven't written new notes in it for more than 10 years). I wonder if the fact that I started with a version 20 years old is a factor. I have done a lot of upgrades over the years, but I started with a much older version. I've tried following your directions for moving the server and clearing the cache. For whatever reason this hasn't worked for me, yet.
Security hotfixes are rare but always easy to apply (usually you just replace one or two files).
One of my most popular pages is a set of instructions I wrote on how to apply DokuWiki upgrades. Not all of your users find it as easy as you do or I suspect my page wouldn't be very popular. If it's true that you can just replace a file or two, I'm certainly doing it the hard way. My instructions include copying all of its files over the old installation.
https://www.joeldare.com/wiki/upgrading_dokuwiki
Anyway, I'm not trying to beat up DokuWiki. It's a free tool that worked very well for me for a long time and I appreciate you for it. It's just no longer the tool of choice for me for the reasons I outlined above.
You're definitely doing updates the hard way. DokuWiki's file layout is designed in a way that makes it safe to simply overwrite it with new releases. Anyway, I just wanted to chime in to correct a few facts. I'm happy you found something that works for you.
As an aside, I'd love to hear about how you monitor HN (and probably other resources) for mention of DokuWiki.
I've spent the last two years building Syften for that purpose. What would you like to know?
I use F5Bot https://f5bot.com/
I've not had any trouble moving it - in fact the folder system works perfectly. I can even point MD editing software like Obsidian at the network share I use for Dokuwiki and edit directly. Dokuwiki is clever enough to show when a file has been edited outside of the system, too.
Look and feel: agree, the default does it no favours (and I wish they'd update their website too, the 1990's look really runs behind the capabilities of the system) - but I've installed bootstrap and then modified to make it cleaner, which was again very easy, just some CSS.
Look and feel: agree, the default does it no favours (and I wish they'd update their website too, the 1990's look really runs behind the capabilities of the system) - but I've installed bootstrap and then modified to make it cleaner, which was again very easy, just some CSS.
I have progressed from Dokuwiki -> Tiddlywiki -> Gollum.
I can now write everything in asciidoc.
Still in love with Tiddlywiki!
My biggest gripe with pretty much everything (Roam, Dendron, etc) is that nothing is plaintext. I love the lack of lockin when everything is based upon plaintext. Furthermore you can use whatever editor you like.