Sadly my website isn’t mobile friendly right now but I’m reworking it. I hope to have the redesign within a week.

As to the price I just left what SS put by default. All my posts are available to free subscribers anyway. Of course I’m happy if you want to contribute but I have no expectations or concerns if you don’t.

You can read this article. https://lemmy.ml/post/4161707. Syncthing is free, open source, simple to set up, and much faster than a repository based solution. The article explains why and how to set it up.

Try running the same distro on a live USB drive. If it runs faster on USB then it’s likely your HD that’s the problem. As many have said, XFCE is very light weight, if you can’t get KDE running smoothly. As an experiment you could try installing Fedora. The way the installer works is that it boots a live version, which you can use. In the live version you have an icon to install to your system. Use the live version a while, then install and run the installed version. Normally the installed version should be noticably faster.

Have you tried ctrl-shft-v to paste?

You could use Syncthing. If your NAT router supports UPnP, which most do, you don’t need to worry about the firewall. If for some reason it doesn’t just work you can forward 22000 tcp/udp. It’s device to device and doesn’t depend on IP addresses.

deleted by creator

Reiserfs was the first journalling FS included in the Linux kernel. Ext3 didn’t make it in until 2001. So reiser was the only game in town for us and why we moved that way. By the time of the murder ext3 was mature so the switch away wasn’t a big deal.

At the time the competition was against a nascent ext3, as I recall, against which reiserfs had significant advantages. Journaling wasn’t standard back then and wasn’t handled by ext2, so there was a lot of competition, and it wasn’t clear that ext3 would be the best solution.

Now that I think about it ext3 wasn’t even a thing. And when it did come on line reiserfs already had a mature journaling system.

This is not for everyone, I agree. I don’t see how it ties my notes to any specific tool, however. It doesn’t impact the contents of notes. It’s just a different way of interacting with them.

Your welcome!

To me the only reason for a second vault is for sharing or collaborating with others. Obsidian really doesn’t care how many notes you have in your vault so maintaining separate vaults just adds additional steps in getting to your info. (Obsidian doesn’t care about directories either for that matter.)

For single-value properties, since I mainly use in-line syntax, I can search for “key:: value” (with quotes) which achieves the same thing. That approach should work for yaml as well unless you’re unlucky. With double colon syntax "key:: " is safely like [key] since I never use double colons in my writing. It’s less safe if using yaml. Searches on multi value keys is harder to do, but OR can get you there if there aren’t too many.

I was one of the reiserfs users before it happened and I dumped it quickly. I think an awful lot of people did the same, and since it was one of a number of alternatives to ext I think it is more abandonment than obsolescence.

Now I think my decision was wrong headed, so long as he was no longer involved. The NASA example was given. Alfred Hitchcock movies? Abuser of women but damn good films.

But that’s the point. In device to device sync there’s no repository.

I haven’t used that one. There’s a gtk gui on flathub, too. I just used the browser interface here because it’s universally available (tmk).

There are many ways. Git based solutions, or any repo based solutions,don’t give instantaneous synchronization though.

In NixOS you can just mount your directories and run nixos-generate-config.

Here’s the documentation https://blacksmithgu.github.io/obsidian-dataview/.

I also want to suggest that you consider not basing queries on folders but using tags instead. Simply putting #author in the notes would mark it as an author note allowing you to simplify your query and make it work no matter where the file is located. Obsidian doesn’t really care about folders although we do always use them. So I don’t think it’s good practice to base queries on them. Just my 2 cents.

You don’t need to pre-scale images. Just add eg. “|75” immediately after the image file name to scale to 75 pixels. If you don’t care about preserving aspect ratio something like “|100x75” works to.