←back to thread

Less is safer: How Obsidian reduces the risk of supply chain attacks

(obsidian.md)
469 points saeedesmaili | 1 comments | 19 Sep 25 22:02 UTC | HN request time: 0.202s | source
Show context
brentm ◴[20 Sep 25 03:06 UTC] No.45309907[source]▶
I've been using Roam Research since about 2020. Is Obsidian better?
replies(1): >>45310032 #
photon_garden ◴[20 Sep 25 03:25 UTC] No.45310032[source]▶
Haven’t used Roam, but what I like about Obsidian:

- All your data is just plain files on your file system. Automation and interop are great, including with tools like Claude Code.

- It’s local-first, so performance is good.

- It’s extensible. Write extensions in HTML, CSS, and JS.

- It’s free.

- Syncing files is straightforward. Use git, Syncthing, Google Drive, or pay for their cheap sync service which is quite good.

- Product development is thoughtful and well done.

- They’re explicitly not trying to lock you in or own your data. They define open specs and build on them when Markdown doesn’t cut it.

Things you might not like:

- Their collaboration story isn’t great yet. No collaborative editing.

- It’s an Electron app.

replies(2): >>45311594 #>>45312358 #
1. deafpolygon ◴[20 Sep 25 11:26 UTC] No.45312358[source]▶
The plain text thing is more of a feel-good argument than a practical one. If there’s a solid export path, the format isn’t really the issue... what matters is whether the app actually works the way you need it to. At the end of the day, your workflow lives or dies on how the software behaves... not on the file extension.