nluhmann.bsky.social
I write about tech, especially PKMs (personal knowledge managers), research, productivity, and AI. I especially focus on tools I use regularly such as Logseq and Obsidian.
48 posts
47 followers
106 following
Regular Contributor
Active Commenter
comment in response to
post
For instance, you can show all pages with a given tag, or all pages in a particular folder path. Then you can check off which properties to display in the table by checking them off in the property menu.
comment in response to
post
I'm loving it, but I agree. Hopefully after they iron out all the bugs and launch sync, etc. they can focus on usability - especially on mobile. Sync will be part of Logseq Pro (along with collaboration and publishing) which will hopefully give them the money they need to hire someone for this.
comment in response to
post
There are a couple available for Obsidian already. Eventually, should be possible for someone to make one to work with Logseq DB...
comment in response to
post
Still, Siracusa's version adds a lot of safeguards, explanations, and options, so I feel a bit safer using it...
comment in response to
post
But this app is a one - time purchase and seems to do the same thing?
www.diskdedupe.com
comment in response to
post
Eventually, Apple's Siri should be able to do this as well, but currently, it looks like it might be a year or two before they get there...
comment in response to
post
The only downside is that it seems to send your audio to the cloud for processing, which raises security concerns, though they make all kinds of promises about that. It also makes it a bit slower than the built-in dictation - which appears as you speak.
You can check it out here:
comment in response to
post
Now that I understand how they work, I really find it frustrating to use LogSec without them. They allow you to create custom properties for individual tags, which can be really powerful. (A bit like Tana's "supertags" which seem to have been a source of inspiration.)
comment in response to
post
When the desktop app is released, I think it will be good enough. The main difference is that it will allow me to backup attachments, which I couldn't do in the browser-only test version of logseq.
In particular, I'm very eager to start using the "new tags" features in my workflows.
comment in response to
post
The DB app will still be in "alpha" and they explicitly warn against using it for your daily work, but I will probably throw caution to the wind and switch over to the DB entirely. I tested it out a few months ago and found that it was almost good enough for my needs.
comment in response to
post
It isn't dead. See this post from last April. Development on the new DB version has been moving at a brisk pace and it should be released later this year:
discuss.logseq.com/t/why-the-da...
comment in response to
post
I feel embarrassed for people when they cite work which says the exact opposite of the point they are trying to make.
comment in response to
post
I found that Claude Sonnet 3.7 is much better about this. ChatGPT would just keep creating new problems, bit Claude is more careful and methodical.
comment in response to
post
(This really amazes me, because while I know my way around a command line, I am not a programmer and could never have done anything like this without these AI tools.)
comment in response to
post
I had tried with ChatGPT but the more I used it the more errors it created. A complete disaster. Claude, using Sonnet 3.7, got the job done in about 30-40 minutes.
comment in response to
post
It still needs some work, but I hope to publish it next week.
comment in response to
post
Used those for years! Invaluable.
comment in response to
post
I was able to double the speed without increasing the error rate:
--progress --transfers=4 --checkers=4 --tpslimit=5 --tpslimit-burst 10 --drive-chunk-size=256M --disable-http2 --bind 0.0.0.0
comment in response to
post
Was still getting errors about 17% of the time. In the forum someone suggested additional commands that seem to have helped get rid of most of those failures:
--progress --transfers 1 --checkers 1 --tpslimit 1 --tpslimit-burst 0 --disable-http2 --bind 0.0.0.0
Docs explain each one here:
comment in response to
post
I'm using App Tamer to stop the app in the background.
comment in response to
post
Rclone is batched cloud-local-cloud.
comment in response to
post
This ensures that it only copies one file at a time. It is slower, but still fast enough and I can just let it run in the background.
comment in response to
post
By the way, you can still get a reasonable deal on a 1TB lifetime account at Koofr via Stacksocial. A discussion on Reddit implied this might expire soon, which is what motivated me to get it now.
(Note: You can only use one offer per account, so you can't buy two and get 2TB on the same account.)
comment in response to
post
The solution seems to be a command line utility called rclone, specifically designed for working with cloud storage services. It supports Koofr. Here is a link to the instructions:
comment in response to
post
I converted it into a Starter Pack:
go.bsky.app/BWyfZng
comment in response to
post
There are two reasons for doing this:
First, I want to get off Dropbox.
And second, the Git plugin for @obsidian.md makes it easy to manage my blog entirely within Obsidian.