It takes a lot of habit to casually slip your daily note in your #ZettelKasten... or fill the #diary at all. You've got to memorize things during the day and flush them before sleep. Don't make a mistake, #NoteTaking is skill in itself.
I called these folders uniformly: 📆 Days, 📝 Perms, 🔗 Refs, and 🎯 Hubs. The point worth stressing is that, if you see anything connect, don't hesitate and type a link right where you're standing.
Well, I’m rotating back to #logseq from #obsidian. The dropoff in my note-taking was extreme. I pretty much stopped taking notes, because the obsidian format wasn’t conducive to my writing style.
Also worth noting I have the same issue with Obsidian I do with #KDE: option paralysis. There’s simply too much to configure, too many things to tweak.
My notes are #PlainText first, #Markdown second. They're highly portable between platforms, apps, and devices. #macos and #ios are my weapons of choice, but they'd look and work the same on #android and #Windows.
@Jakra@AvrilMAalund Be sure to look at #Obsidian, too. Biggest difference between Obsidian and #Logseq is that Obsidian is prose- and file-focused and Logseq is outline- and block-focused. They’re both free, so try them both; chances are one will feel more natural to you pretty quickly.
Switching back from #obsidian and #logseq to #emacs and #orgmode (+#orgroam) feels like a step from someone else's home into a thriving forest: such a rich eco-system! Found #systemcrafters an invaluable resource to get quickly from vanilla emacs to something which exceeds or is on par with the alternatives in all aspects that matter: configurability, extendability, control, speed, resources, android support via #orgzly, themes, #foss, local first, future proof,....
TIL about the #Logseq Diagrams plugin: You can create a ton of diagram types like C4, Flow etc. using different libraries like mermaid.js, plantuml etc.
I then stumbled across a minor holy war between logseq people who proclaim it is a note taking app, and so MUST use bullets for everything, and others who are confused about why a Markdown editor adds bullets to anything.
Short version - it's not a Markdown editor. It uses its own flavor of Markdown, and its purpose built for note taking ... and forces everything to use bullets.
🟢 #FOSS with AGPL license (in theory)
🔴 In reality it depends on a closed source module responsible for sync, dubious legality and misleading
🟡 Developed almost privately by a Venture Capitals funded company but accepting small contributions on GitHub and donations on OpenCollective
🟢 Store notes in #Markdown (or in less supported #OrgMode) locally
🟡 Forces indented lists in .md files and it doesn’t support normal paragraphs at all
🟡 Introduces syntax that breaks Markdown in a very bad way instead of using code blocks where possible (in Advanced Queries?)
🟡 Based on Electron, NodeJS and NPM
🟡 UI and business logic mixed together, it forces you to always run the whole UI, including for sync
🟢 Available for Linux on FlatHub (unofficially)
🔴 AppImage is the only officially supported way to install on Linux
🟡 No official reproducible builds but unofficial Flatpak ones are reproducible
🟡 Not in F-droid (and the closed source sync feature wouldn’t be allowed there anyway), you have to grab their APK manually or automatically
🟢 Supports Wayland but not by default
🟢 Custom CSS
🟡 Fixed UI, no tabs, no split view
🟡 Multi-window means multiple conflicting whole instances
🟢 Plugins platform
🔴 Plugins marketplace based on GitHub
🟡 Poor integration of plugins especially from UI/UX PoV
🟢 Very interesting concept of PDF annotations
🟡 PDF annotations not stored in the .pdf as standard annotations
🟡 PDF annotations stored in their own .md files with odd names
🟢 LaTeX formulas support
🟡 No native PDF export and in general problematic
🟡 Too many menus, command palettes and other redundant UI elements
🟢 Queries with simple syntax and UI
🟡 Advanced Queries are too often needed
🟢 Datalog query language in Advanced Queries
🟡 Very broken aliases feature
🟡 Inconsistent requirements of capitalize, lowercase etc in query syntax and elsewhere that even break some functionalities
🟢 Macros
🟡 Macros don’t work with most syntax, including Advanced Queries
🟢 Supports HTML and Hiccup syntax
🟢 Supports embedding Web pages using iframes
🟢 Sync is e2e encrypted
🔴 The code for e2e encryption can’t be audited because it is closed source
🟡 Tons of functionalities must be configured by editing a EDN file that it is very easy to break
🟢 Forum based on Discourse
🔴 Use (and abuse) of Discord, even release announcements are made there
🟡 Some Matrix bridges
Given the points above and the fact I backed #Logseq for a long time but addressing these issues may require years and maybe the project won’t survive anyway that long, what should I do? Move to a simpler but better supported system like #Emacs or wait and hope Logseq team figure out priorities?
Recent “AI” (sigh) native integration in Logseq (using OpenAI according to a GitHub branch of theirs, again zero communication by the team) lower my hopes a lot.
If they take money from people they should make clear what it will be used for.
I use it for over half a year now to write almost daily all the relevant stuff from my brain into it and it's super awesome to see interconnected data that I can use to get information and really knowledge out of.