Anyone out in #nostr land use a PKM (personal knowledge management) app. I found one called logseq. and i'm wondering what the advantages would be over the system that I have kind of working on nextcloud and my notes. Also found one called NB thats cli based.
#asknostr
Not seeing much you couldn’t do in Obsidian, et al. with plugins, but perhaps the value is in having it all set by default.
Personally, this is very close to how I use Obsidian. The only thing I’ve never done is flash cards, as I’m an auditory learner.
I've been using Obsidian and plain text. Obsidian isn't open source but I was already using markdown for most of what I was writing so Obsidian just added quality of life to what I was already doing.
Im working on an app called #mindstr (click the hashtag)
I'd like to see a nostr version of obsidian too
Logseq looks very cool! Think we could get a login with nostr version going?
Ill check out mindstr.
Logseq is foss so I dont see why not. Could be fun to play with. You could also use a private relay to keep notes synced. I havent looked to deep at logseq yet (late shift at the FIAT mines reeee) but I wonder how hard that would be.
Thanks for this, I'm already getting into it. I'll integrate it with minstr, nostr, nosdav and other stuff
I use Obsidian with SyncThing to sync all my files between computers and my own server.
Not sure if that's what you're looking for.
Runs into issues syncing to iOS devices unless you pay for Obsidian's backup service.
Ive been avoiding obsidian because its not FOSS but it looks sick.
Another thing i'm trying to look at his portability of my information. like if an app stops being developed for whatever reason than I need to be able to take all of that info from the app and move somewhere else. Hence my janky nextcloud set up. 😅
Me too, but on android
A Knowledge Base is ment to organize your random notes into a structured form - wiki-alike, but not the same more ridgit structure.
I see the use in a KM mainly when you have to document things for which you don't want to run separate apps or are building yourself a strong basis of documentation. You could document your insurance numbers much the same way that you do your home server configurations. Now, in a KM, you organize them to a degree and maybe your insurance eventually goes digital and offers you a FIDO setup. Now you might reference your infrastructure from within your insurance. You can do that in a wiki too, but a KM usually makes inter-connection a little easier.
