Obsidian Versus Syncthing: Markdown Purists Demand Full Control Over Note Sovereignty
Many users converge on file-based synchronization, specifically pushing plain Markdown files synced via tools like Syncthing or cloud backups like Nextcloud/Dropbox, often leveraging editors such as VS Codium or Kate.
The ideological split pits Obsidian's usability against the demand for open standards. Pro-Obsidian users, like AxiomShell, praise its localized data structure, while others champion pure, self-managed stacks. Joplin receives multiple endorsements, noted for its cross-platform nature and self-hosting options via WebDAV, which baronvonj advocates heavily.
Ultimately, the core conflict settles on control versus convenience. The consensus tilts toward robustness via raw file sync, exemplified by the 'ultimate endgame' suggestion of pairing Vim keybindings with Syncthing to Markor, but the lure of Obsidian's linking system keeps the proprietary camp loud.
Key Points
File-based synchronization using Syncthing for plain Markdown files is a highly viable, respected method.
Users like zarlin confirm Syncthing works reliably across Windows, Android, and Linux for this setup.
Obsidian's local-first architecture is praised for data portability, even if official sync fails.
AxiomShell argues this makes it superior to ecosystems that might restrict data access.
Joplin is repeatedly recommended for its cross-platform flexibility and WebDAV self-hosting capabilities.
baronvonj and harsh3466 cite it for robust, manageable syncing methods.
The absolute standard for control involves complex, custom setups like pairing Vim keybindings with Syncthing.
rutrum details this 'endgame solution,' favoring raw file management.
Silverbullet.md is highlighted for advanced, scriptable functionality beyond basic note-taking.
clif points to Lua scripting and dynamic 'Lists of Lists' generation as key features.
Proprietary tools are criticized for locking users into ecosystems that violate open standards.
comradeMiao and Ephermeral drive the argument toward open standards like Anytype or pure Markdown.
Source Discussions (3)
This report was synthesized from the following Lemmy discussions, ranked by community score.