farcaller

I’m sure there are some #pkm people in here that use a digital #zettelkasten. How do you solve "where to file a note" problem? Let me elaborate.

I don’t use any IDs because it seemed that it's a paper process problem. At the same time, when I wrap up a note, I don’t immediately know which ones to link it to to add it to the graph. The paper approach solves this by filing it under the closest relevant ID.

If I don’t link the note immediately it's effectively lost forever, because it's outside of the graph, it most probably has some random title (titles are hard!) and it is in a folder with 400 other notes.

Maybe I should keep such notes as Fleeting until I can link them into the permanent graph? For me it created a problem of notes being fleeting for too long because there's no place to anchor then either.

I **suppose** that IDs solve this problem because you can always apply at least the "soft" structure of ID topics. But is there a better way?

@pkb @pkms

@kenoh tfw I notice the username and realize this got federated over to lemmy. This tech is pretty nice!

But yeah, absolutely. When it comes to important data (and my logseq graphs are important), you do backups and you verify the backups. Logseq sync is unreliable between platforms with filesystems that ignore case and don't, for example I've stumbled on https://github.com/logseq/logseq/issues/10993 recently, and hey, it was reported back in February. Checking it now I see the github bot already labelled it as stale and I suppose it will be closed without action soon.

I use git as a backup for logseq sync, but given how it tries to overwrite the config, it's not a fully reliable option either. Sometimes it syncs pages from graph A into graph B.

PKM is a hot space with new tool coming every week. I don't think Obsidian is a perfect tool by any means, after all I used it for more than a year before jumping ship to logseq. But it seems that if I use it less an advanced markdown editor and more like an outliner (for which it has a few plugins) that will fit my mental model and help to find things.

/cc @logseq

I think I'm (sadly) done with @logseq. It corrupted some data again and when I went to pull the stuff from git I figured it corrupted the .git/config even earlier than that. So now I have to pull the correct content from an old windows backup, ffs. What if I didn't have a full disk backup?

I like the idea of block references, I love the query engine and the simple UI. But data safety comes first, really. Logseq is a forever beta at this point.

I really like the concepts behind the logseq db version but @obsidian doesn't fuck with my data and you can see good iterative progress of its development. Yeah, it's not opensource. It's open data format, though, something logseq db will have to figure out eventually anyway.