First off, thank you for the incredible work on mdbase-rs, the specification, and the new mdbase-connect layer. I was looking for pretty much this exact idea, and I am trying to figure out the most pragmatic way to adopt this across my desktop and mobile (iOS) devices.
The Ideal Workflow Ideally, I want to use an editor (like Obsidian) strictly as a "smart client" and local cache. The centralized mdbase-connect daemon would act as the source of truth.
I would navigate and edit my collection as usual in the editor. Changes would be detected and, if validated, synced with mdbase-connect. If a record is invalid, I would get some kind of feedback inside the editor until it is fixed. (A bunch of nice-to-haves could also be added, like full support for mdbase-lsp or custom modals to help with editing frontmatter).
Is this already in the works? I wanted to know if you are already working on a solution for this something like a generalized MDBase Connect sync/validation client for Obsidian, a dedicated PWA or something similar to the TaskNotes web app?
Building it Myself vs. Alternatives I am considering implementing parts of this myself to bridge Obsidian and the @mdbase/connect SDK. However, I have doubts about my ability to execute it elegantly and maintain it in a reasonable timeframe, given the limited time I can dedicate to this right now.
I would value your advice on how manageable of a task this is, using the great tooling you have already provided. I would also love your input on a potential architecture, or if I might be approaching the problem completely wrong (e.g., leaving syncing to Syncthing and/or obsidian-livesync, the tools I currently use and handling validation elsewhere).
Your Setup & Recommendations I was also wondering how you use your tools yourself. If you have the time, I would love to know how you structure your notes, which devices and tools you use to interface with them, and more about the philosophy and practical implementation of your collection(s). Maybe you would also be willing to share your long-term goals with MDBase and an unofficial roadmap.
Please know that I don't take anything more from you for granted, you've already provided so much. Answering these questions is entirely optional, and please feel free to just drop a link to any docs or posts I might have missed.
Thanks again for your time and the massive effort you've put into this ecosystem!
First off, thank you for the incredible work on mdbase-rs, the specification, and the new mdbase-connect layer. I was looking for pretty much this exact idea, and I am trying to figure out the most pragmatic way to adopt this across my desktop and mobile (iOS) devices.
The Ideal Workflow Ideally, I want to use an editor (like Obsidian) strictly as a "smart client" and local cache. The centralized mdbase-connect daemon would act as the source of truth.
I would navigate and edit my collection as usual in the editor. Changes would be detected and, if validated, synced with mdbase-connect. If a record is invalid, I would get some kind of feedback inside the editor until it is fixed. (A bunch of nice-to-haves could also be added, like full support for mdbase-lsp or custom modals to help with editing frontmatter).
Is this already in the works? I wanted to know if you are already working on a solution for this something like a generalized MDBase Connect sync/validation client for Obsidian, a dedicated PWA or something similar to the TaskNotes web app?
Building it Myself vs. Alternatives I am considering implementing parts of this myself to bridge Obsidian and the @mdbase/connect SDK. However, I have doubts about my ability to execute it elegantly and maintain it in a reasonable timeframe, given the limited time I can dedicate to this right now.
I would value your advice on how manageable of a task this is, using the great tooling you have already provided. I would also love your input on a potential architecture, or if I might be approaching the problem completely wrong (e.g., leaving syncing to Syncthing and/or obsidian-livesync, the tools I currently use and handling validation elsewhere).
Your Setup & Recommendations I was also wondering how you use your tools yourself. If you have the time, I would love to know how you structure your notes, which devices and tools you use to interface with them, and more about the philosophy and practical implementation of your collection(s). Maybe you would also be willing to share your long-term goals with MDBase and an unofficial roadmap.
Please know that I don't take anything more from you for granted, you've already provided so much. Answering these questions is entirely optional, and please feel free to just drop a link to any docs or posts I might have missed.
Thanks again for your time and the massive effort you've put into this ecosystem!