Ditching Obsidian and building my own (amberwilliams.io)

Article summary

The author discusses their experience with various personal knowledge management systems (PKMS), including Obsidian, and their decision to build their own custom solution. They cite concerns about privacy, security, and the longevity of commercial PKMS, as well as the desire for a simple and flexible system. The author describes their custom PKMS, which is built using a platform called Directus and allows for easy note-taking, organization, and synchronization across devices. The system is designed to be secure, private, and future-proof.

Main themes

• Personal Knowledge Management
• Custom Solutions
• Privacy and Security
• Longevity and Maintenance
• Open Formats and Data Hygiene
• Commercial vs. Custom PKMS
• Git and Version Control
• Technical Debt and Maintenance

What commenters say

• Some commenters argue that building a custom PKMS is unnecessary and that existing solutions like Obsidian are sufficient.
• Others disagree, citing concerns about the longevity and security of commercial PKMS and the benefits of having complete control over one's data.
• The use of Git for synchronization and version control is proposed as a viable alternative to commercial solutions.
• Some commenters express skepticism about the feasibility of maintaining a custom PKMS over time, citing the potential for technical debt and the need for ongoing maintenance.
• The importance of data hygiene and longevity is emphasized, with some arguing that even proprietary formats with export functions can be sufficient.
• Others argue that proprietary formats pose a risk of lock-in and that open formats like Markdown are preferable.
• The value of building a custom PKMS as a learning experience and a way to tailor a system to one's specific needs is also highlighted.
• Some commenters suggest that the effort required to build and maintain a custom PKMS may be better spent on other pursuits.