[–] 3 points 2 years ago*

There's no reason to pay for sync. As your vault is plain-text files you can use dozens of existing sync solutions.

There's an open-source community sync plugin which aims to provide an equivalent replacement to the paid sync: https://github.com/vrtmrz/obsidian-livesync

I'm happily syncing my vault with Drive, and also paying for the sync as a way to support the Obsidian app development.

  • source
  • [–] 4 points 2 years ago

    While I agree that this post seems like a giant spammy ad, you don't have to provide anything personal to Kagi. You can pay with crypto rather than card - I paid using Monero via a swap service.

  • source
  • parent
  • context
  • [–] 0 points 2 years ago* (last edited 2 years ago)

    Wise does not have the same. Here's my EU card page: https://i.imgur.com/yvrUSvq.png

    They offer virtual cards, but not one-time-use cards. It's a big difference in safety.

    In fact, apart from just finding out about privacy.com (only available in the US), I'm not aware of anybody except Revolut who offers one-time-use cards.

    e: If you know how to do it with Wise, please let me know. (Virtual cards which can be deleted after use are not the same as one-time cards.)

  • source
  • parent
  • context
  • [–] 5 points 2 years ago

    In Logseq, everything is a nested list. This feels like a limitation, but I’ve been preferring it. The decision is made for you: you’re going to jot this information down as a list. So then you just start writing it.

    I really appreciate you posting this. I'm a long-time Obsidian user, and an Evernote user before that, and I never "got" Logseq. I just couldn't understand what people saw in an app that didn't let you "write" anything. I've tried to start using Logseq so many times and just given up because the interface made no sense.

    Thanks to your comment I finally get it! I prefer to be using something open-source, so I'm going to give Logseq another go, now that I finally understand it, and see how that approach feels.

  • source
  • parent
  • context
  • [–] 1 point 2 years ago* (last edited 2 years ago)

    Obsidian, Zettlr, and Logseq live in the category of local plain-text file-based PKMs.

    Trilium lives in the category of local database-based PKMs.

    The reason the first category exists is that people wanted to get out of vendor and file lock-in.

    Apples and oranges.

    Having been through the enshitification of Obsidian, it was important to me and many others to be not beholden to any vendor's file system. Your database requires Trilium to be instantly usable. My notes are useful and usable (and frequently accessed) from Logseq and VSCode.

    The two options are simply not comparable, hence apples and oranges.

  • source
  • parent
  • context
  • [–] 1 point 2 years ago* (4 children)

    You’re describing now a larger scope of requirement

    I am not. I am saying data storage format is a basic, critical factor. And it is. And I already know you agree on this, which is why you choose FOSS options with known, open formats.

  • source
  • parent
  • context
  • [–] 1 point 2 years ago* (last edited 2 years ago) (6 children)

    Lmao. No, I don’t agree that file format is the most critical choice

    Local vs web-hosted, or open formats vs closed formats are part of the exact same choice. So I think you probably do agree that it's a critical, basic component of your software decision. 😉

    Yes obsidian supports various linking formats, but mainly uses its own.

    But it doesn't. The only two options are Wikilinks or original Markdown.

    The only software that I'm aware of that is in the same camp as Obsidian - plaintext Markdown files and non-outliner - is Zettlr.

  • source
  • parent
  • context
  • view more: next ›