I’m currently trying out Joplin:
– Free sync via Dropbox—which is a bit slow. I may eventually switch to Joplin Cloud ($2.40/month).
– Relatively simple UI—which is exactly what I want. Obsidian has many features I don’t need.
Designing #ToolsForThought - one of the long-term things I have been musing about is how to combine the power of the bullet-point outliner with the power of the long-form writing tool. The issue is, both are pretty powerful in a modern setting. Throw something like Capacities together with something like Tana. The interface gets nastily cluttered.
So why don't separate them a bit? Here's what I call a 90/10 solution - it's not perfect, but I think it manages most of the things needed. 1/n
The idea of transcluding entire pages into another page has been more well-established in designs of, for example, #Logseq. So that works. You want to write a long-form page deeper into an outliner thread? You can use a backslash-dialogue to create that new page and transclude/link it in place. Works just as well.
A few complex scenarios where you mix long-form text and outliner thought annotations don't really work with this scenario, but that's okay.
After listening to @amolith on the @linuxlads I am giving #Logseq a decent go again: I'll try it for 2 weeks and see where I end up. I wrote in my Bullet Journal once this month, so I can't be worse than that. I am using my #Obsidian folder already set up with #Syncthing between devices, and it seems fine with that.
Obsidian lasted... not long, but I think I was trying to be too rigid with it. So I'll try not to be so much this time.
My favourite feature is automatically periodically save a snapshot of current tabs as Markdown indented lists. And since I specified my #Logseq folder as the saving path, I can navigate my browser history from Logseq journal.
I have been experimenting with using #LogSeq as a #bookmark database, but it's not working out. Maybe I need to write a new bookmark service. (lol, aw me, you crack me up.)
Dear #logseq and #obsodian users, #git is not a backup system. Store your notes in a reposotory, if you must, but please configure a backup for your notes.
i really like #flatnotes, but it's a little bit too minimalistic ... thinking about switching to another #note taking solution ... but there are so many options. #obsidian , #logseq , #joplin ?
main requirements are that its needs to be quick and easy to use; syncing the notes between desktop and android phone (not through external cloud, needs to be #selfhosted) ... preferrably 100% #foss - so i guess obsidian is already out?
Was möchte man denn für Notizen verwenden, wenn man diese auf #Linux, #Android oder #Windows erstellen und bearbeiten möchte. Verteilt auf verschiedene Geräte sollen diese über #Syncthing werden.
@qbi
Nutze #Logseq auf meinem Android und synchronisiere den Graph mittels Syncthing. Auf dem Desktop ist Logseq echt ganz toll. Aber die Android App finde ich sehr fiddelig zu bedienen - am Rande der Unbenutzbarkeit. Meistens kippe ich da nur Links rein, über die ich stolpere. Schade ...
#emacs#logseq anyone have a working setup with logseq (in orgdown) and #orgroam playing nice in logseq's folder (orgroam dailies in 'journals', etc)? Currently my vault is a mix of org and md but I'm hoping to at least get the org files recognized while I work on converting the md (or figure out #mdroam). I tried playing with org-logseq but even though I'm matching correctly on its grep for the folder and I have title properties I couldn't get it working after a good attempt. #askfedi
@flameeyes I already have one wordpress instance I need to manage, screw that. I actually enjoy authoring posts in #logseq nowadays, I just need a sensible pipeline to publish them that doesn't involve running scripts in clojure, calling into hugo, and then scp -r.
I even started working on that. Clojure's nbb is amazing, being clojure but with all the node-modules you can eat (and your ssd can fit). I don't need much, clearly nothing of the hugo's customization abilities, just a live preview and a final render. Writing the hiccup-themed html that just renders into static tags is fun. Being able to access the logseq's DB directly is also really handy and you can do some processing if needed (like resolving logseq's cross-block references, pulling the images from the store, etc.)
I'm writing a longer (as it seems) article on the lock-in effect of solutions like #Obsidian that are using open formats like #Markdown for storage. The file format is not the only thing that might lock you in.
I did already start with a list of arguments but also want to collect your ideas so that I don't forget a good argument.
Please, no emotions, just facts and objective arguments.
Reply here in this thread and I'll collect ideas from it. 🙇
This year I wanna get into doing diligent note-taking: #Obsidian vs #Logseq, which is the better option? Or something else entirely? My only real requirements are having a Linux app and an Android one being a nice-to-have.
I try now #Logseq and this is #OpenSource and I would like to like it but somewhere I can't manage to understand and use it. I don't just want to write down my thoughts and #ideas, I also want to be able to check off a #todo list… 😐
Wow. I guess I was wrong when I said that we have well and truly enough #Obsidian how-to tutorials out there. Either that or this person doesn’t have the faintest idea how to google properly.
might like to look into either of those wrt to "building a second brain". On the actual software side, the darlings of note-taking seem to be split into 2 1/2 camps. Either #obsidian (page-based knowledge - my personal preference), #logseq (block-based knowledge) or #orgmode, which I'm assigning the 1/2 to as I don't know much about it, not as many people seem into it and (to me) it's complicated and non-intuitive to start off with. Obsidian has a tree structure on the left, works ...2/4
They're working on a DB version in parallel that will provide better scalability, performance and realtime #collaboration (#RTC). They'll charge for RTC.
Unfortunately, this seems to be the end for #orgdown markup as they are implementing #Markdown only now and a conversion feature later on. 😞
Therefore, logseq is not an option for me any more and I'll need to think about a migration strategy for my wife.