I have slowly dusted off my #logseq graph and began using it is a daily journal for my project work. I had forgotten how much I like the concept of Logseq's daily journal.
Still using it more sporadically than I should be. For comparison, my activity from around 2 years ago.
@AAMfP Furthermore, I'd not say that Markdown definitions are bloated in contrast to Orgdown. Quite the contrary since in the basic Markdown definitions, there are no tables, blocks, properties and many many more syntax elements orgdown knows.
@publicvoit
Nice point.
Indeed I'm actually using Org Mode Markup Syntax also through #Orgzly app (from F-Droid) instead of phone calendar, agenda and notes, but also when writing text emails, text messages and even on Slack, WhatsApp and other similar tools, even if they are not (so) compatible with it.
Maybe your idea is not popular but I'm sure that people using Org Mode Markup Syntax are using it everywhere. 😉
@spinningthoughts 100% - what the key takeaways / summary are to me wil lbe different to a bot. Will it also capture the nuances / read between the lines comments of a meeting or simply factual.
Feels like there are other aspects of Tana that could have been worked on with AI, rather than forming the core of the app, being something additional
@spinningthoughts I also feel that they now might find themselves in a type scenario where other aspects of the app will fall to the wayside as they will need to put all efforts into ensure that AI runs as it should (given this is basically what users are paying for) while other basic things are not fixed.
@ednico Not doing local-first early is biting Tana in the arse quite a bit. Notion managed it (eventually) but they‘re kicking a good bit of technology debt down the road there.
@spinningthoughts I could not agree more. That and export - I feel like if Tana really wanted to appeal / get the attention of the masses it was to implement Offline or proper encryption and be different from the rest
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.
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?
#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
@Neblib I "kind of" do. I am using heavily modified org-roam-logseq.el though. There still are some issues, e.g. Logseq fails to recognize ID references as backlinks (linking itself works).
I was planning a blog post about my setup, but with recent news about Logseq DB development I am considering ditching it.
@wigol yeah the logseq db announcement was a bit disappointing for sure. Emacs 30 being on Android takes away some of the reasons for a logseq as the mobile end of a org workflow, especially if developer interest refines that mobile experience further.
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. 🙇
@publicvoit I don't think, that Markdown per se is a lock-in factor. Ideally, every tool would save everything as flat text files. That would truly be open, imho.
Ages ago, I was using a simple, text file based local wiki. Things got complicated ever since.
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.